The honest view from inside technical leadership
Analysis

Engineering leadership

Independent reporting on the decisions, costs and contracts that shape how engineering organizations build with AI.

Security · News

Tigerfish S3 Bucket Exposed Police Interview Transcripts for Weeks After a Warning Went to Spam

A San Francisco transcription firm that works for police departments and prosecutors stored customer recordings and transcripts where anyone could list and download them. Fixing the bucket took one setting. Reaching someone who would read the warning took a reporter.

Line-art illustration of an open storage bucket with transcript pages and a film strip lifting out of it, beside an envelope dropped into a spam tray, representing the Tigerfish S3 bucket exposure

A Tigerfish S3 bucket left transcriptions of police interviews, body-cam footage, raw customer recordings and customer invoices open to anyone on the internet, TechCrunch reported on 20 November 2026. The researcher who found it emailed the San Francisco transcription company in October, and Tigerfish says that email landed in its spam filter.

The Tigerfish S3 Bucket Held Police Interviews, Body-Cam Footage and Invoices

Anurag Sen, an independent security researcher, found the data on an Amazon S3 storage bucket that listed its own contents and sat at a web address simple enough to guess. No password was required to read any file. TechCrunch’s Zack Whittaker reported that the files included transcripts of police interviews, body-cam footage, the raw audio and video that customers had sent in for transcription, and invoices. The invoices identified some of the customers, among them police departments and prosecutors’ offices. TechCrunch also describes Tigerfish as working for government departments and large technology companies. Before contacting the company, TechCrunch verified the data and where it came from. Tigerfish’s own website promises clients the “highest standards of confidentiality” and a strict non-disclosure policy.

Tigerfish Locked the Bucket Soon After TechCrunch Called, Weeks After the First Warning

Sen discovered the open bucket in October and wrote to Tigerfish. Nobody answered. He then gave the details to TechCrunch so the exposure would reach someone at the company, and Tigerfish secured the bucket soon after TechCrunch got in touch. Tigerfish president Adam Goldberg told TechCrunch by email, “We’ve blocked all public access to the bucket you identified.” He said the block covered directory listings and individual files, that the company had confirmed all its other S3 buckets were blocked from public access, and that it was reviewing its storage security more broadly. The company said Sen’s original disclosure had been caught by its spam filter. TechCrunch could not establish whether Tigerfish has told its customers, and the company did not reply to a follow-up email.

AWS Has Blocked Public Access on New S3 Buckets by Default Since April 2023

Amazon Web Services says S3 buckets and objects have always been private by default. It added a feature called Block Public Access in 2018, and from April 2023 it switched that feature on automatically for every newly created bucket, in every region, whether the bucket is made through the console, the API, the command line or CloudFormation. A newly created bucket that grants public access therefore requires someone to turn that protection off first. TechCrunch’s report does not say when the Tigerfish bucket was created or how its permissions were set. Sen told TechCrunch that most of the exposures he finds trace back to ordinary human mistakes, such as an engineer disabling authentication to test something before a weekend and never switching it back on.

Why This Matters for Engineering Leadership

The technical fix at Tigerfish was a single access setting, and it was applied within a short time of the right person hearing about the problem. The weeks of exposure came from the intake side: a warning from a researcher arrived in October and went unread. That is a gap an engineering leader can close in an afternoon. RFC 9116, published in April 2022, defines a security.txt file served at /.well-known/security.txt that tells researchers where to report a vulnerability. When this site checked on 21 November 2026, tigerfish.com returned a 404 at that path. Publish the file, point it at an address that a named person reads, and exempt that address from spam filtering. Then remove the dependency on individual buckets being configured correctly. S3 supports Block Public Access at the account level, which overrides any single bucket’s settings, and a change to that setting can trigger an alert. A company that stores police interviews on behalf of prosecutors also needs a decision, made in advance and with a deadline, about how and when customers are told that their files were exposed.

FAQ

What data did the Tigerfish S3 bucket expose?

TechCrunch reported that the bucket held transcriptions of police interviews, body-cam footage, customers’ raw audio and video, and customer invoices. The invoices showed customers including police departments and prosecutors’ offices.

Who found the Tigerfish data exposure?

Anurag Sen, an independent security researcher, found the bucket in October 2026. He emailed Tigerfish, received no reply, and then passed the details to TechCrunch.

Has Tigerfish fixed the exposure?

Yes. Tigerfish president Adam Goldberg told TechCrunch the company blocked all public access to the bucket and checked that its other S3 buckets were also blocked.

Why did Tigerfish miss the researcher’s warning?

The company told TechCrunch that Sen’s disclosure email was caught in its spam filter.

Did Tigerfish notify affected customers?

It is not known. TechCrunch reported that it was unclear whether customers had been told, and Tigerfish did not answer a follow-up email.

How can a company make sure security researchers can reach it?

Publish a security.txt file under RFC 9116 at /.well-known/security.txt, pointing to an address that is monitored and exempt from spam filtering.

Source: A transcription firm used by police, prosecutors, and tech giants exposed customer data online by Zack Whittaker, TechCrunch, November 20, 2026. Primary sources: Amazon Web Services, “Heads-Up: Amazon S3 Security Changes Are Coming in April of 2023”, and RFC 9116, “A File Format to Aid in Security Vulnerability Disclosure”, April 2022.

Read more news & analysis