Skip to content
Cloud Security Breaches

Twilio (2020): what the sources say about the cloud incident

Twilio disclosed the incident on 22 Jul 2020. The ledger reads the access path as public storage, databases and services. The cloud or provider involved: AWS. Every field rests on the primary sources listed below. Fields no primary source states read not public.

Open the ledger · Report a correction

Disclosed
22 Jul 2020
Incident window
July 19, 2020 1:12 PM PDT to July 20, 2020 10:30 PM PDT (window for downloads of the modified library, per the company)
Cloud or provider
AWS
What was exposed
A modified version (v1.20) of the TaskRouter JS SDK hosted on the company's content domain. The company stated it had no evidence that any customer data was accessed and that no malicious party had access to its internal systems, code or data; customers who downloaded v1.20 in the window were asked to replace it.
How access was gained
The company's incident report says a misconfiguration in the S3 bucket hosting the library let a bad actor inject code, and that the access policy for the path storing the SDK allowed anybody on the Internet to read and write to that path.
Access path
Public storage, databases and services
Kind of control that addresses it
deny public write access on storage that serves code to customers, audit bucket policies on a schedule, and publish integrity checks for served scripts

In the words of the source

“We had not properly configured the access policy for one of our AWS S3 buckets.” (company statement, Incident Report: TaskRouter JS SDK Security Incident - July 19, 2020)

Primary sources

If a field is wrong or a newer primary source exists, write to the editor with the entry name in the subject.

Sources

  1. Incident Report: TaskRouter JS SDK Security Incident - July 19, 2020, read 16 Nov 2026

Last reviewed 16 Nov 2026.