· via TechCrunch
Transcription firm Tigerfish left police interview transcripts exposed in open S3 bucket
Tigerfish, a transcription vendor serving police, prosecutors and major tech companies, left customer transcripts, raw audio and video, and invoices on a publicly reachable cloud server.

What happened
Tigerfish, a San Francisco-based transcription company whose customers include police departments, prosecutors' offices and large Silicon Valley firms, has fixed a security lapse that left a substantial set of internal data open to anyone on the internet, according to TechCrunch. The exposed material reportedly included transcriptions of police interviews and body-camera footage, customers' raw audio and video files, and invoices from the company's clients.
According to the report, the files sat on an Amazon-hosted S3 cloud server that was publicly listed and reachable through an easily guessable web address, with no password required. Security researcher Anurag Sen discovered the exposure in October and emailed Tigerfish, but heard nothing back; the company later said his message had landed in its spam filter. Sen then passed the details to TechCrunch, which verified the leak and contacted the company. Tigerfish secured the bucket shortly afterwards.
The company's response
Adam Goldberg, Tigerfish's president, told TechCrunch in an email that the company had blocked all public access to the affected bucket, including directory listings and individual files, and had confirmed that its other S3 buckets were also closed off. He added that Tigerfish is continuing to review and strengthen its storage security more broadly. TechCrunch reports that it remains unclear whether the company has notified affected customers, and Tigerfish did not respond to a follow-up inquiry.
A researcher who hunts open databases
Sen, 30, has spent roughly a decade scanning the internet for sensitive datasets left unprotected, describing his work to TechCrunch as that of an "unpaid air-traffic controller." His past finds, as reported by TechCrunch, include US military emails leaking from a compartmentalised Department of Defense cloud server, databases full of customer records, the inner workings of a national licence-plate surveillance system, and public systems inadvertently streaming SMS login codes used around the world.
Working from his home in Indonesia, he uses automated scanners and specialised search engines to locate cloud storage and databases that probably should not be public. In his view, the findings expose how "fragile" the internet really is behind the scenes, despite running on an assumption of absolute trust.
Misconfiguration, not mastermind hacking
Sen attributes most of the exposures he finds to ordinary human error rather than sophisticated attackers, according to TechCrunch. His illustration: an engineer spins up a test cloud database on a Friday, disables authentication to test an API, and forgets to close the door before the weekend.
The report also places the incident in a broader trend. AI tools are making it easier to uncover weaknesses, and the spread of AI-assisted "vibe coding" is pushing insecure, unchecked code into production. In response, Amazon has added multi-step warnings before an S3 bucket can be made public, and newer platforms such as Lovable and Supabase have built in guardrails against common user mistakes. Sen's argument, as relayed by TechCrunch, is that people fear "shadowy hackers" when the real crisis is sensitive systems and databases left wide open on the public internet without a password.
Why it matters
The data at stake was not ordinary business material. Transcripts of police interviews and body-camera audio can identify suspects, victims and witnesses, and can reveal details of active investigations, so exposure could compromise prosecutions and endanger individuals. The exposed invoices add client rosters and payment details to the picture.
The incident is also a supply-chain lesson: public agencies and major technology companies handed highly sensitive recordings to a third-party vendor, and a single storage misconfiguration put all of it a guessed URL away from anyone. The spam-filter episode shows how easily responsible disclosure can fail through mundane channels; without TechCrunch stepping in, the data might still be online. For any organisation storing sensitive material in the cloud, routinely verifying bucket permissions and maintaining a monitored channel for security reports remain basic hygiene.
- #security
- #data-leak
- #aws-s3
- #transcription
- #cloud-storage