The short version
- The exposure. Tigerfish left a large amount of internal data, including customer transcriptions and the raw audio and video behind them, on an openly listed Amazon S3 storage bucket. The material included transcriptions of police interviews and body-camera footage, plus invoices naming police departments and prosecutors' offices.
- How it was found. Security researcher Anurag Sen found the bucket in October at an easy-to-guess web address that required no password. He alerted Tigerfish but received no reply; the company later said his email had been caught in its spam filter, and Sen took the details to TechCrunch.
- The fix. After TechCrunch verified the data and contacted the company, Tigerfish blocked public access to the bucket, including directory listings and individual files, and said it had checked its other buckets.
- Customer notice unclear. It is not known whether Tigerfish has told affected customers. The company did not respond to a follow-up email from TechCrunch.
Timeline
| Date | Event |
|---|---|
| October | Anurag Sen finds the exposed Tigerfish bucket and emails the company; the company later said the message was caught in its spam filter and went unanswered. |
| 20 Nov | TechCrunch reports the exposure after verifying the data; Tigerfish says it has blocked all public access to the bucket and that its other S3 buckets are also blocked. |
What happened
Tigerfish, based in San Francisco, transcribes audio and video for law enforcement, government departments and large technology companies. A storage bucket belonging to the company was listed publicly on Amazon's S3 service and reachable through a web address that was easy to guess, with no password required. The contents included customer transcriptions and the original recordings they were made from.
Sen, a researcher who has spent years locating exposed datasets, discovered the bucket in October and emailed the company. He heard nothing back and later passed the details to TechCrunch, which verified the source of the leak and the data before contacting Tigerfish. The bucket was secured shortly afterwards.
Tigerfish president Adam Goldberg said the company had blocked public access to the bucket, including directory listings and individual files, and had confirmed that its other S3 buckets were also closed to public access. He said the company was reviewing its storage security more broadly. Tigerfish said Sen's original email had been caught by its spam filter.
Who is affected
The exposed material covered police interviews, body-camera footage and customers' raw audio and video, according to TechCrunch. Invoices in the bucket identified customers including police departments and prosecutors' offices.
The source does not say how many customers or recordings were involved, how long the bucket had been open, or whether anyone other than the researcher accessed the files. Tigerfish has not said whether it has begun notifying the organisations whose recordings were exposed.
Wider context
Sen told TechCrunch that many of the exposures he finds come down to basic human error rather than sophisticated attack, giving the example of an engineer creating a test database, switching off authentication and forgetting to close it again. He argued the bigger risk is sensitive systems left open to the public internet without a password.
The report notes that Amazon has made it harder to make S3 buckets public without clear warnings, and that some newer development platforms have added similar safeguards against user mistakes. It also points to unchecked, AI-generated code as a growing source of security problems.
What is not known yet
- Whether anyone other than the researcher downloaded or viewed the exposed transcripts, footage or invoices.
- How many customers and how many recordings were exposed, and how long the bucket had been publicly reachable.
- Whether Tigerfish has notified the police departments, prosecutors' offices and companies whose material was in the bucket.
- Whether the exposed material included recordings tied to active cases or other material under confidentiality restrictions.
What to do
If you are a Tigerfish customer
- Ask the company in writing whether your transcripts, recordings or invoices were in the exposed bucket.
- Ask whether access logs show anyone other than the reporting researcher retrieved files, and whether notification is planned.
- Treat any recordings or transcripts held by the firm as potentially public until it confirms otherwise.
If you run cloud storage
- Inventory buckets and block public access at the account level rather than per bucket.
- Check for directory listings and individual objects that are readable without authentication.
- Delete or lock down test and proof-of-concept buckets created outside normal provisioning.
For everyone else
- Treat misconfiguration, not only intrusion, as a primary route to data loss, and make closed-by-default storage the standard.
- Monitor the mailbox that receives security reports so a researcher's warning is not lost to a spam filter.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.
We email you about this topic only; unsubscribe any time. See our Privacy Policy.