deniz.in

Markets

Weather

Loading weather

· via Hacker News – Front Page (native)

OpenRouter drops three providers and pulls 125 endpoints from Zero Data Retention after data incidents

OpenRouter says security researchers found data compromises at several AI inference providers, prompting it to remove three providers and strip 125 endpoints of Zero Data Retention eligibility.

OpenRouter drops three providers and pulls 125 endpoints from Zero Data Retention after data incidents

What happened

Security researchers reported this week that certain AI inference providers had data compromised, or otherwise showed evidence that their data handling policies were not being upheld. The account comes from OpenRouter, the routing service that sits between customers and a fast-moving catalog of hosted models, which published a summary of the findings alongside its own response.

According to OpenRouter, the testing did not reveal any breach of, or unauthorized access to, OpenRouter itself. The results instead exposed problems at specific inference providers within its ecosystem. OpenRouter worked with the researchers and the providers involved to understand the findings and to push the providers to address them, and it credited a report by Dragos for surfacing the issues.

What OpenRouter did

OpenRouter describes itself as the operating layer between customers and a fast-moving market of models and providers, and said it takes data policy enforcement seriously. The actions it has already completed:

  • Off-boarded three providers from the platform based on the results of its investigations.
  • Removed 125 endpoints from Zero Data Retention (ZDR) eligibility. The removals covered providers flagged by the researchers, plus additional endpoints pulled as a precautionary measure.
  • Notified all potentially affected customers.

Further work is underway:

  • Adapting the researchers' testing approach so the same checks can run on an ongoing basis.
  • Conducting technical verification of network paths to identify cases where requests and responses may be forwarded to third parties.
  • Requiring appropriate assurances and validation before any removed endpoint regains ZDR eligibility.

OpenRouter thanked the authors of the Dragos report and said it intends to integrate similar testing techniques into its own operations, raising the bar that providers will need to meet in order to remain listed.

The providers involved

Three providers have posted public security announcements, which OpenRouter listed in its statement:

  • Novita published a privacy notice regarding MiniMax requests on its platform.
  • Phala published a preliminary incident report for November.
  • Together disclosed a security event involving prompt leakage for requests made in June and July of 2026.

Not every affected provider has posted publicly. OpenRouter said it has notified affected users regardless of whether a public write-up exists, and that it is encouraging all providers to produce incident reports and will keep the list updated over time.

Why it matters

Anyone sending prompts, documents or customer data to a hosted model is trusting the inference provider on the other end, not just the model vendor or the aggregator that routed the request. Zero Data Retention is a promise that many enterprise and compliance workflows depend on: if a provider quietly retains or leaks request data, customers have little way of knowing unless someone actively tests for it. That is what makes this episode notable — the problems came to light through external testing rather than provider transparency, and Together's disclosure shows the exposure can reach back months, to requests sent in mid-2026.

The episode also signals a shift in who enforces these policies. An intermediary like OpenRouter is now running its own verification, delisting providers and gating ZDR status behind technical checks rather than relying on stated policies alone. For teams building on hosted models, the practical takeaway is to track which specific endpoints carry retention guarantees, since eligibility can change quickly — 125 endpoints lost it in a single review — and to treat the routing layer, not just the model provider, as part of the security boundary worth auditing.

  • #ai-security
  • #privacy
  • #openrouter
  • #llm-inference
  • #data-retention

Related posts