Signal Downstream of Twilio (2022)

Signal used Twilio to deliver SMS verification codes for account registration, making Twilio a fourth-party dependency for Signal users.

Discovery. The incident surfaced in 2022 after unusual activity was identified in the vendor's environment.

Investigation. External forensics confirmed unauthorised access affecting phone re-registration.

Notification. Downstream customers were notified and required to review their own exposure.

• Attackers gained access to the vendor environment holding phone re-registration.
• Credential, token or software supply chain compromise was central to the intrusion path.
• Downstream customers had limited visibility into vendor internal controls.
• Detection was delayed relative to the exposure window.

• Vendor was under-classified. Data classification did not reflect the volume or sensitivity of phone re-registration.
• Concentration risk was invisible. One vendor served many customers in the same sector.
• Contractual controls were weak. Notification, forensic access and evidence rights were vendor-favourable.
• Downstream visibility was absent. Customers could not see the vendor environment where their data lived.

• Downstream customers issued notifications to their end users.
• Regulators reviewed the incident under relevant data protection and sector rules.
• Contract renegotiations followed for affected vendor relationships.

The Signal via Twilio incident became a reference point in TPRM programmes for communications SaaS, driving stronger classification, contractual and monitoring controls across the sector.

The customers who used Signal via Twilio did not have a technical failure. They had a trust failure. They trusted the vendor to hold phone re-registration without ever verifying how.

1. Classify communications SaaS as tier-1 by default when they hold phone re-registration.
2. Demand contractual notification within hours, not days.
3. Require independent forensic reports for material incidents.
4. Rotate credentials, tokens and keys after any vendor breach.
5. Segment vendor tenants and least-privilege every integration.
6. Map concentration risk across the sector.
7. Rehearse downstream customer notification with legal and comms.
8. Report vendor incident lessons to the board with clear owners.

"Your vendor holds phone re-registration. Verify how, or inherit the incident."