Tigerfish leak: an open S3 bucket and a warning sent to spam
Transcription firm Tigerfish left police interviews and raw audio in an open S3 bucket, and the researcher's warning hit spam. Check your vendors and buckets.
Tigerfish, a San Francisco transcription firm that works for police, prosecutors and tech companies, left customer data in an Amazon S3 bucket anyone could list. TechCrunch reported on November 20 that the bucket held police interview transcripts, body-cam transcriptions and customers' raw audio and video. The researcher who found it emailed Tigerfish in October. The email went to spam. Two failures, both cheap to prevent.
What actually happened
Per TechCrunch:
- What was exposed: transcripts of police interviews and body-cam footage, customers' raw audio and video, and invoices for customers including police departments and prosecutors' offices. No record counts were given.
- How: an S3 bucket that was openly listed, at an easy-to-guess web address, with no password.
- Who found it: security researcher Anurag Sen, in October 2026. He got no reply, so he went to TechCrunch.
- The fix: Tigerfish locked the bucket after TechCrunch reached out. President Adam Goldberg said the company blocked all public access and "verified that all of our other S3 buckets are blocked to public access."
- The spam filter: Tigerfish said Sen's disclosure email was caught in its spam filter.
- Customers: it is unclear whether Tigerfish has told them. It didn't answer TechCrunch's follow-up.
Sen's view: most leaks are human error, like a test bucket opened on a Friday and forgotten. TechCrunch notes Amazon recently added multistep warnings before a bucket goes public.
Why it matters for your business
You probably don't hold body-cam footage. You probably do send call recordings, meeting audio or voice notes to some transcription or AI vendor. That vendor has a bucket too.
And if you run your own cloud storage, the Tigerfish story has a second lesson: someone tried to warn them. Nobody saw it.
What we'd check:
- Ask your transcription and AI vendors where your audio is stored, how long they keep it, and whether public access is blocked at the account level.
- Turn on S3 Block Public Access for your whole AWS account, not bucket by bucket. AWS documents it here.
- Delete what you don't need. Raw recordings you already transcribed are pure risk.
- Publish a security contact. Add a
security.txtfile and a monitored security@ address. Make sure the spam filter can't eat it. - Review AI-generated infrastructure code. Vibe-coded storage setups are where "temporary" public access becomes permanent.
Key takeaways
- Tigerfish exposed police interview transcripts, body-cam transcriptions and raw customer audio and video
- The cause was an openly listed S3 bucket with no password
- The researcher's October warning was caught in Tigerfish's spam filter
- It's unclear whether customers have been notified
- Block public access account-wide, ask vendors where your recordings live, and monitor a security inbox
Not sure what's public in your cloud account? We audit storage permissions, retention and vendor data flows for small teams, then fix what we find. Book a review or see our services.
Sources: TechCrunch, AWS documentation.
- #data-breach
- #aws-s3
- #vendor-risk
- #transcription
- #security-disclosure
Tommy Rush — Founder, Rush Commerce
Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More
Get The Rush Report weekly — one email, zero fluff.
Keep reading
OpenRouter drops 3 providers, pulls ZDR from 125 endpoints
OpenRouter off-boarded three inference providers and removed 125 endpoints from zero data retention after Dragos canary research. What to check in your stack.
Read itOpenAI Performance Factory: Codex agents debug, engineers merge
OpenAI's Performance Factory ran 1,700+ Codex investigations into ChatGPT slowdowns. 70% of audited root causes held up; about 15 agent PRs shipped as written.
Read it