Skip to main content
Twilio10-Q: Cybersecurity incident

Twilio acknowledges past security incidents including hacking and phishing have occurred on its platform.

What happened

The company discloses that its platform has previously been affected by hacking, fraudulent use attempts, and phishing attacks. This admission of past security failures indicates a significant and ongoing pain point, likely driving investment in new security tools, services, and personnel to prevent future occurrences and protect customer data.

Source

SEC EDGARMay 1, 2026

Quarterly report (Form 10-Q)

Twilio 10-Q

Filing excerpt

In addition, computer malware, viruses and computer hacking, fraudulent use attempts and phishing attacks have become more prevalent in our industry, have occurred on our platform in the past and may occur on our platform in the future.

sec.gov/Archives/edgar/data/1447669/000144766926000049/twlo-20260331.htmRead the full source

Other signals in this filing (6)

Extracted by Autobound

From the Signal API record
Signal
10-Q: Cybersecurity incident

What this signalsFilings often name leadership changes, deals and spending plans.

Fiscal year end
03/31
Filed
May 1, 2026

More 10-Q signals at other companies

The full record

From the Signal API record

Details

CIK
1447669
Accession number
0001447669-26-000049
Filing year
2026
Fiscal year
0
Why it matters
Urgent security needs
Signal category
Technology

Topics and mentions

Technologies

  • malware
  • phishing

Extraction

Confidence
High
Relevance
90%
Sentiment
Negative
Detected
May 5, 2026
signal_type
sec-10q
signal_subtype
cybersecurityIncident

Use this data

Get every 10-Q signal for Twilio and the companies you sell to, in the tools you already use.

  1. Ask Claude about it

    Connect Autobound to Claude, Claude Code or Cursor with MCP. Then ask: “What changed at Twilio this week?”

  2. Send it to your own tools

    The Signal API returns 10-Q signals for any list of companies as JSON, for your CRM, warehouse or app.

  3. Try it free

    Sign up and spend your free credits on the companies you sell to.

    Start Free1,000 free credits

The API returns more than this page shows

This page shows a preview. The full sec-10q record in the Signal API and MCP can also have these 8 fields. Some fields are empty for some signals.

Company

  • linkedin_urlValue in the API
  • industriesValue in the API
  • employee_count_lowValue in the API
  • employee_count_highValue in the API
  • revenueValue in the API
  • descriptionValue in the API

Signal

  • signal_nameValue in the API
  • associationValue in the API
Show the full JSONThe record on this page and the API request

GET /v1/signals/b61d83a8-7c2f-4f9a-9d43-bbe93e77b58a returns this record as JSON. POST /v1/companies/enrich returns every signal for twilio.com.

{
  "signal_id": "b61d83a8-7c2f-4f9a-9d43-bbe93e77b58a",
  "signal_type": "sec-10q",
  "signal_subtype": "cybersecurityIncident",
  "detected_at": "2026-05-05T08:48:22.355+00:00",
  "company": {
    "name": "Twilio",
    "domain": "twilio.com"
  },
  "data": {
    "detail": "The company discloses that its platform has previously been affected by hacking, fraudulent use attempts, and phishing attacks. This admission of past security failures indicates a significant and ongoing pain point, likely driving investment in new security tools, services, and personnel to prevent future occurrences and protect customer data.",
    "summary": "Twilio acknowledges past security incidents including hacking and phishing have occurred on its platform.",
    "excerpts": "In addition, computer malware, viruses and computer hacking, fraudulent use attempts and phishing attacks have become more prevalent in our industry, have occurred on our platform in the past and may occur on our platform in the future.",
    "relevance": 0.9,
    "sentiment": "negative",
    "confidence": "high",
    "source_url": "https://www.sec.gov/Archives/edgar/data/1447669/000144766926000049/twlo-20260331.htm",
    "filing_date": "2026-05-01",
    "filing_year": 2026,
    "fiscal_year": 0,
    "fiscal_year_end": "03/31",
    "sales_relevance": "Urgent security needs",
    "signal_category": "technology",
    "technologies_mentioned": [
      "malware",
      "phishing"
    ]
  }
}

Long text fields are shortened on this page.

Looking up one signal by its id is free. Enrich costs 2 credits per signal returned; a call with no results is free.