Skip to content
Source: together.ai

🔐Together AI Breach Exposes Prompts From Three Models Via Leaked Repo Credential

Check your Together AI data retention settings today

TL;DR

Together AI disclosed that an exposed private-repo credential let an unauthorized party download stored prompt samples from MiniMax M3, GLM-5.2, and Kimi K2.6 in June and July 2026. The attacker tested other services' credentials, and the company says the data was deleted. Customers handling sensitive prompts should enable zero data retention now.

Together AI says a credential for a private repository ended up in a public code repo, and someone used it to pull stored prompt samples. The affected traffic came from MiniMax M3, GLM-5.2, and Kimi K2.6, mostly on June 24, July 4, July 8, and July 14, 2026. If you send prompts through those models on Together's serverless inference, your inputs may have been sitting in that store. The part that should make you sit up: the attacker didn't just grab prompts. They searched the samples for credentials to other services and tested whether they worked. Five of the tested credentials were canaries from a Dragos security experiment, which is how the company learned the data was being mined. Automated scanning caught the exposed commit and it was reverted, but the window was already open. Together says an outside forensic firm and law enforcement are involved, and the company has found no evidence of prompt leakage beyond this incident. The attacker has reportedly deleted the data with no sign of further spread. The review of which prompts contained personal information or other customer data is still running, and affected customers will hear directly. Controls are tightening: scoped or short-lived credentials, keyless access where supported, credential scanning on every pull request, and zero data retention as the default for new accounts.

Together AI Breach Exposes Prompts From Three Models Via Leaked Repo Credential — together.ai

Key Points

1

The incident window covers June and July 2026, with most affected traffic concentrated on June 24, July 4, July 8, and July 14.

Keep reading — it's free

Enter your email to keep reading — plus the best of AI & tech, daily. Free, forever.

Also get
or

Already a member? Sign in

Together AICredential LeakPrompt SecurityZero Data RetentionAI Infrastructure

Comments

Subscribe to join the conversation...

Be the first to comment