Transcription firm Tigerfish left customer data openly accessible online
San Francisco-based Tigerfish, which transcribes audio and video for police, prosecutors and tech giants, left customer materials openly accessible online. The company locked down access after a security researcher's warning and TechCrunch's involvement.

Tigerfish, a San Francisco transcription company serving law enforcement, government departments and Silicon Valley tech firms, has fixed a security lapse that left a large amount of internal data exposed on the web. The data included customer transcriptions and the source materials behind them. The incident shows how simple misconfigurations can leave sensitive information open to anyone.
What was exposed
The exposed files included transcriptions of police interviews, body-camera footage, and customers' raw audio and video recordings. Invoices were also visible, and the company's customers include police departments and prosecutors' offices.
According to security researcher Anurag Sen, the files sat on an Amazon-hosted (S3) cloud storage server whose contents were openly listed. Anyone could reach it through an easy-to-guess web address, with no password required.
How it came to light
Sen found the data in October and alerted the company, but received no reply. He then passed the details to TechCrunch. The outlet verified the source of the leak and the data and contacted Tigerfish, which secured the storage soon afterward.
Tigerfish president Adam Goldberg said in an email that all public access to the bucket, including directory listings and individual files, had been blocked, and that the company's other S3 buckets had been checked. He added that Tigerfish is continuing to review and strengthen its storage security. The company said Sen's email had been caught in its spam filter. It is unclear whether Tigerfish has notified its customers, and it did not answer a follow-up email.
The researcher's view
Sen, 30, has spent the past decade searching for sensitive datasets exposed online from his home in Indonesia, aiming to notify their owners. He says most leaks he finds come down to basic human error, such as an engineer disabling authentication for a test on a Friday and forgetting to restore it. In his view, the real problem is sensitive systems left open to the public internet without a password.


