Key facts
- Tigerfish president Adam Goldberg said the company blocked all public access to the identified S3 bucket, including directory listings and individual files.
- Goldberg said Tigerfish verified that all of its other S3 buckets are blocked to public access.
- The exposed data included transcriptions of police interviews, body-cam footage, customers' raw audio and video, and customer invoices, per the report.
- Tigerfish said Sen's email disclosing the leak was caught in its spam filter.
- Tigerfish did not respond to a follow-up email asking whether it had notified customers, according to the report.
Tigerfish, a San Francisco transcription company whose customers include law enforcement, government departments and Silicon Valley technology companies, blocked public access to an Amazon-hosted S3 cloud bucket after a security researcher found customer data exposed online, according to a TechCrunch report published November 20, 2026.
The exposed material included transcriptions of police interviews, body-cam footage, customers' raw audio and video footage, and invoices of the company's customers, which include police departments and prosecutors' offices, the report said. Security researcher Anurag Sen, who found the files, said they sat on an openly listed S3 server reachable through an easy-to-guess web address with no password required.
Sen said he discovered the data in October and alerted the company but did not hear back, and later gave details to TechCrunch to flag the incident. After TechCrunch contacted Tigerfish, the company secured the bucket. "We've blocked all public access to the bucket you identified, including directory listings and individual files," Tigerfish president Adam Goldberg said in an email, adding that the company had verified its other S3 buckets were also blocked and was reviewing its storage security more broadly.
Tigerfish said Sen's email disclosing the leak was caught in its spam filter. It is unclear whether the company has notified its customers; Tigerfish did not respond to a follow-up email, the report said. Sen told TechCrunch that many exposures he finds come down to basic human error, such as an engineer disabling authentication on a test database and forgetting to restore it.
