November 23, 2026InfrastructureMonitoring

OpenRouter Pulls 125 Endpoints From Zero Data Retention. The Label Was Never Tested

Two days ago the story was a researcher's canary study: fake secrets planted in prompts sent through AI routers and resellers, then watched to see who touched them. Now the vendors have answered, and the numbers are bigger than the email that leaked on Saturday. OpenRouter posted an official statement on Nov 22 (Hacker News 275 points by 02:14 UTC). It has off-boarded three providers, removed 125 endpoints from Zero Data Retention eligibility, and notified every potentially affected customer. The 125 includes endpoints the researchers flagged plus more pulled "as a precautionary measure." The three off-boarded providers are not named. Statement: https://openrouter.ai/blog/announcements/data-processing-incidents-on-inference-providers

The providers' own posts explain what went wrong, and it is two different failures. Novita says a routing config meant for specific customers applied broadly, so MiniMax requests between May 28 and Nov 11 2026 were forwarded to MiniMax's official API instead of running on Novita hardware, including requests that came in through OpenRouter. The researcher saw accesses to URLs embedded in test prompts, no use of the AWS key markers, and Novita says the pattern "suggests automated content review"; it is still checking with MiniMax. Notice: https://novita.ai/blog/minimax-requests-privacy-notice/ Together AI's failure is older and dumber: a credential for a private repo leaked in a public repo, and someone downloaded stored prompt samples from MiniMax M3, GLM-5.2 and Kimi K2.6 traffic, mostly from June 24, July 4, July 8 and July 14. The attacker then searched those samples for credentials and tested them. Five were Dragos canaries. Write-up: https://www.together.ai/blog/security-event-prompt-leakage-for-requests-in-june-and-july-of-2026

So one leak was a routing mistake and the other was a stolen key, and in both cases the customer's ZDR checkbox said nothing. That is the real news. ZDR was a promise copied from a provider's terms into a router's filter. Nobody was checking whether the promise held. OpenRouter now says it is adapting the researchers' method to run continuously and verifying network paths for third-party forwarding before it restores ZDR to anyone. Good. That should have been the product from day one.

If you run agents, this hits harder than it would for a chatbot. Agents paste API keys, env files and customer records into context all day, and Together's attacker went hunting for exactly that. Rotate anything that went through MiniMax on Novita in that window. And stop treating "zero retention" as a property of a vendor. It is a claim, and claims need a canary.
← Previous
OpenAI Just Published Its Speedometer and Asked Everyone to Agree on a Speed Limit
Next β†’
fast-anything Lets the Agent Write Rust, Then Makes Production Decide
← Back to all articles

Comments

Loading...
>_