OpenRouter removes three providers after prompt-theft research
OpenRouter off-boarded three providers and removed 125 endpoints from Zero Data Retention eligibility after researchers traced exposed prompt data at AI inference providers.
OpenRouter off-boarded three providers after research found data from at least three artificial intelligence (AI) inference providers exposed. Dragos seeded about two million prompts with unique links and credentials between July and November 2026. None knew about the breach until Dragos notified them.
The earliest breach began in mid-July. Some stolen requests were flagged as Zero Data Retention (ZDR). The largest breach involved a couple hundred planted Amazon Web Services (AWS) keys, each sent in exactly one request during short windows in late October. Some stolen keys came from requests the provider rejected before a model ran.
The bait keys drove tens of thousands of AWS application programming interface (API) calls. One attacker appears to have compromised two providers at once from a single rented server. OpenRouter removed 125 endpoints from ZDR eligibility. It notified all potentially affected customers. The findings showed no breach of OpenRouter itself. OpenRouter requires assurances and validation before restoring ZDR eligibility to any removed endpoint.
According to The Hacker News, an attacker took control of an inference server at Phala and could view request data while it was processed. The report said Phala contained the incident on November 8. Requests to DeepSeek V4 Flash 0731 routed through the gateway between October 21 at 00:00 UTC (Coordinated Universal Time) and November 8 at 05:35 UTC should be treated as exposed.
The report said Together AI’s stored customer prompt samples were downloaded after a credential was committed to a public GitHub repository. Together AI made zero data retention the default for new accounts.
Why it matters: prompts can carry live credentials. The report also said a Chinese AI lab fetched secret links from more than half of the seeded prompts sent to its models between July and October. About two-thirds of the requests marked no data collection or ZDR were fetched by the lab’s scraper.
What to do: check for an OpenRouter notification and review whether your endpoints still qualify for ZDR. The cited sources do not list fixed versions for the affected providers.
Sources
Related reading
3 postsDiscussion
Spotted an error? Send corrections to [email protected] .