Transcription firm Tigerfish exposes police interviews and bodycam footage on unsecured cloud server
A security lapse at San Francisco-based Tigerfish left sensitive law enforcement transcriptions and video footage accessible online without a password. The company secured the data after a researcher reported the exposure.

Key takeaways
- Tigerfish exposed police interviews, bodycam footage and invoices on an unsecured Amazon S3 bucket.
- Security researcher Anurag Sen discovered the leak in October and reported it via TechCrunch after no direct response.
- Tigerfish secured the bucket and says it has checked other storage for similar misconfigurations.
- It is not known if affected customers have been notified or if the data was accessed before remediation.
In this article
What was exposed
A transcription company used by police departments, prosecutors' offices and major technology firms left a large volume of internal data exposed on an Amazon S3 cloud storage bucket. According to TechCrunch, the bucket contained transcriptions of police interviews, body-camera footage, raw audio and video files, and customer invoices. The data was accessible via an easy-to-guess web address with no password protection required. An S3 bucket is a basic storage container in Amazon Web Services; when misconfigured, it can be listed and downloaded by anyone on the internet.
How the data was discovered
Security researcher Anurag Sen found the exposed bucket in October 2026 during routine scans for unprotected datasets. Sen, who has spent a decade reporting similar exposures, alerted Tigerfish directly but received no reply. He then shared details with TechCrunch to prompt action. TechCrunch verified the source of the leak and contacted the company. The publication reports that Sen's initial email was caught in Tigerfish's spam filter, delaying the response.
Company response and remediation
After being contacted by TechCrunch, Tigerfish secured the bucket within a short period. President Adam Goldberg confirmed in an email that all public access to the identified bucket had been blocked, including directory listings and individual files. He added that the company had verified its other S3 buckets were also blocked from public access. Goldberg said Tigerfish is continuing to review and strengthen its storage security more broadly. The company did not respond to a follow-up question about whether affected customers have been notified.
Wider implications for cloud storage security

The incident highlights how simple misconfigurations continue to expose sensitive information despite growing awareness. Sen told TechCrunch that many leaks stem from basic human errors, such as engineers disabling authentication for testing and forgetting to re-enable it. He noted that recent attention on artificial intelligence accelerating vulnerability discovery overlooks the fact that most exposures result from unprotected systems left open to the public internet. Cloud providers including Amazon have added multi-step warnings to make it harder to create public buckets accidentally, but legacy configurations and oversight remain risks.
Unanswered questions
It remains unclear whether Tigerfish has informed the law enforcement agencies and corporate clients whose data was exposed. The company did not answer TechCrunch's follow-up email on customer notification. The duration of the exposure and whether any unauthorised parties accessed the data before it was secured are also unknown. Researchers like Sen continue to scan for similar exposures, arguing that the real crisis is not sophisticated hacking but the sheer volume of sensitive systems left without basic password protection.
Sources
Spotted a mistake? See our corrections policy. Read how News by OnDevice works in our editorial policy.



