Skip to content
Breach Index · running record

OpenRouter and the 2026 inference-provider incidents (not a breach of OpenRouter)

OpenRouter is an LLM router: one API that sends each request to one of many inference providers. This page tracks what OpenRouter has told customers about incidents at those providers in November 2026. By OpenRouter's own account, its own systems were not breached.

Short answer

Was OpenRouter hacked?

OpenRouter says it was not breached: its announcement of 22 November 2026 says the researchers' findings "did not show any breach or unauthorized access of OpenRouter". The problems it describes were at inference providers it routes requests to. That is OpenRouter's own assessment; no independent investigation has been published.

After security researchers reported that some providers had data compromised or did not uphold their data policies, OpenRouter says it off-boarded three providers, which it does not name, removed 125 endpoints from Zero Data Retention (ZDR) eligibility, notified all potentially affected customers and is adapting the researchers' tests to run continuously. It credits the Dragos report and links notices from Novita, Phala and Together AI.

Earlier, on 21 November, OpenRouter emailed customers that "Requests you sent to MiniMax models may have been read": a researcher's test URLs in prompts sent to MiniMax models from July to October 2026 were accessed by a third party 40 to 130 hours later. OpenRouter said that issue sits with MiniMax and the providers that forwarded to it, not with OpenRouter.

Timeline at a glance

  1. Jul–Oct 2026A researcher's test URLs in prompts sent to MiniMax models are accessed by a third party 40 to 130 hours later, per OpenRouter's email. (OpenRouter (customer email))Not a breach
  2. 19 Nov 2026Dragos publishes canary research: at least three AI providers breached (unnamed); one traced route had an undisclosed OpenRouter hop. (Dragos)Reported
  3. 21 Nov 2026OpenRouter emails customers that requests to MiniMax models may have been read; removes the ZDR label from those endpoints. (OpenRouter (customer email))Not a breach
  4. 22 Nov 2026OpenRouter off-boards three unnamed providers, removes 125 endpoints from ZDR eligibility and notifies potentially affected customers. (OpenRouter)Not a breach

Last updated 22 November 2026. Every entry is dated and linked to its source; claims by attackers are labelled as claims, never stated as fact.

OpenRouter incident timeline, in detail

Confirmed = acknowledged by OpenRouter, a regulator filing or a court. Reported = credible reporting OpenRouter has not fully confirmed. Unverified claim = an attacker or leak-site claim.

Nov 2026Not a breachThird-party (inference provider) incidents

Three providers off-boarded and 125 endpoints removed from ZDR eligibility

What happened. OpenRouter says security researchers reported that certain inference providers had data compromised or did not uphold their data policies. Based on its investigations it off-boarded three providers and removed 125 endpoints from ZDR eligibility, including providers the researchers flagged and others removed as a precaution. It notified all potentially affected customers, including where a provider has not posted publicly.

Impact. OpenRouter says the findings did not show any breach of OpenRouter. It is adapting the researchers' testing to run continuously, verifying network paths for requests or responses forwarded to third parties, and will require "appropriate assurances and validation" before restoring ZDR eligibility to any removed endpoint. It does not name the three providers.

Sources: OpenRouter announcement · Dragos research · PlayCISO write-up

Jul–Nov 2026Not a breachThird-party (model provider) data handling

Requests sent to MiniMax models "may have been read"

What happened. In an email to customers, OpenRouter said a security researcher placed unique test URLs in prompts sent to MiniMax models from July to October 2026, and a third party accessed them 40 to 130 hours later, whether MiniMax served a request directly or another provider forwarded it to MiniMax.

Impact. OpenRouter said the issue sits with MiniMax and the forwarding providers, not with OpenRouter, that none of the researcher's AWS test keys were used, and that it removed the ZDR label from these endpoints. As of 21 November there was no public OpenRouter page for this notice.

Sources: PlayCISO write-up

Where the reports disagree

  • Which providers: OpenRouter names none of the three providers it off-boarded, and Dragos names none of the three it found breached. No source says whether they are the same three, or whether Phala, Together AI or Novita are among either group.
  • Not a breach vs exposure: OpenRouter says its own systems were not breached, but requests sent through it reached providers where prompts were exposed. Customers can be affected without OpenRouter being breached.
  • Hidden hops: Dragos says one traced route included an OpenRouter hop that was "not disclosed in the marketplace" it was bought through.

The pattern across the record

A router is a subprocessor chain

Each request goes to a provider OpenRouter picks unless you pin one, and that provider may forward it again. Each hop can read the prompt.

ZDR is a policy, not a control

Removing 125 endpoints from ZDR eligibility shows the label could not be relied on for them. Verify where requests actually go.

What it means for OpenRouter customers — and what to do

If your apps, agents or staff send prompts through OpenRouter, read any notice OpenRouter sent your account and check the provider windows against your logs.

  1. 1.Read your notice and rotate

    Rotate any secret that was in a routed prompt during the windows the providers give (Phala, Together AI, Novita), then review those accounts.

    Leaked credential response
  2. 2.Pin providers for sensitive work

    Use an allow-list of providers with fallbacks off, rather than letting the router choose.

    What to do this week
  3. 3.Verify ZDR routing

    Set ZDR and data-collection deny, then check that they change which endpoints serve your requests.

Take this with you
Incident timeline · What OpenRouter customers should do · Sources

CISO takeaways

Sources

Company statements and regulator filings first, then reputable reporting. Reviewed 22 November 2026.

  1. 1.Data Processing Incidents on Inference Providers — OpenRouter, 22 Nov 2026
  2. 2.Three breaches, endless leaks: Your AI supply chain needs canaries — Dragos, 19 Nov 2026
  3. 3.November preliminary incident report — Phala, 10 Nov 2026
  4. 4.Security event: prompt leakage for requests in June and July of 2026 — Together AI, 21 Nov 2026

Frequently asked questions

Was OpenRouter hacked?

OpenRouter says no: the researchers' findings "did not show any breach or unauthorized access of OpenRouter". The incidents were at inference providers it routes requests to.

Which providers did OpenRouter remove?

OpenRouter says it off-boarded three providers but does not name them. It links notices from Novita, Phala and Together AI and says not all affected providers have posted publicly.

What happened with MiniMax on OpenRouter?

OpenRouter emailed customers on 21 November 2026 that requests sent to MiniMax models from July to October may have been read by a third party, and said the issue sits with MiniMax and the providers that forwarded to it.

Our coverage of OpenRouter

Same sourced, verification-tagged timeline, company by company — compare how peers have fared.

Or see the full Breach Index and how to read it.

Independent analysis for security-leadership education; not affiliated with or endorsed by OpenRouter. Facts are attributed to the dated sources above, and anything disputed or unconfirmed is labelled as such. See the full Breach Index.