Data Processing Incidents on Inference Providers

270 points88 comments19 hours ago
usernomdeguerre

Wow I missed this story entirely. I'd seriously considered moving to OpenRouter at my next external AI renewal due to the breadth of options and pricing but this has absolutely ended that consideration.

It's clear from the breadth and variety of exposures that there's no due diligence or guardrails inside OpenRouter on who they market and how they classify their providers. Their response to this indicates a few first steps but none seem to have the force of law and i'd have expected more from a Stripe aquisition.

Very glad that my daily driver is a local model and I only use these external services sparingly.

redrix

Nice to see this move by OR.

That being said, the best ZDR agreement is the one that your company has directly with the inference provider(s). Unfortunately:

- Not everyone is large enough (or has enough $$) for that. - Ultimately you’re in the same position of having to “trust” that they’re doing ZDR; even after auditing their security docs.

show comments
a012

I was affected with just one prompt by this incident, which is non issue to me because I was trying different models at that time so there was nothing serious. The troubling problem I see in this incident is the “providers” in OR just casually forwarding prompts to upstream (MiniMax) instead of providing inference service them selves.

Coincidentally later on I set my OR settings to only allow some providers that I can rely on, not blindly let OR route to wherever they like.

show comments
smuhakg

I got the email. The tl;dr is MiniMax (the Chinese AI lab) is actively reading your prompts, and a security researcher discovered this by putting decoy URLs into their requests which were accessed by MiniMax.

More importantly, many providers (AtlasCloud, Novita and StreamLake were named but there seems to be more implied in the blog post) have been rerouting requests to MiniMax servers on the backend and not processing their own prompts.

The obvious question is whether OpenRouter has done any auditing on their inference providers. Based on the researcher's blog post, I guess not.

https://www.dragos.com/blog/ai-supply-chain-security-canary-...

show comments
leobg

As an aside, I always wondered about decision models. They are so cheap. I can’t help but think that providers must be using them as honeypots for data acquisition:

You do dont find real world company documents on the web that you could train on. And companies certainly won’t upload them to you so you can improve your models, not even with incentives. But provide a model with dirt cheap input pricing and free outputs - and you gut yourself a firehose.

To think that the “labs” wouldn’t train on this is like thinking they’d never have trained on shadow library books because, “well, it’s illegal”. They did it back then and it gave them an advantage over the competition. So why wouldn’t they now?

show comments
mbgerring

You should assume that no inference provider is honoring any public commitment they have made about data retention. You should assume that 100% of what you share with an LLM over the wire is being recorded, saved, and used as training data. Any other stance is indefensible naïveté for anyone who has been around the tech industry for more than, let’s say, 5 years.

show comments
codedokode

This reminds again that all "promises" of companies are a lie and you better not trust their "privacy policies".

show comments
hasyimibhar

ZDR through AWS Bedrock is still safe right? AFAIK Bedrock self hosts all models they provide. Even proprietary weight models like Claude are run within AWS network.

show comments
coderz89

Also saw Prompt leakage for requests incident from Together AI

https://www.together.ai/blog/security-event-prompt-leakage-f...

though this is not similar as ZDR, it's crazy to see so many incidents in last few months.

the_lucifer

Is there any information on the three companies that violated ZDR? I could only find mention of one of those affected providers in the original article (that OR links in their post): Lark. Trying to figure out if I ended up routing to one of the affected "ZDR" endpoints.

I don't understand why these names are being coyly tiptoed around as if they're trying to protect the privacy of these companies blatantly lying about ZDR. Why isn't OR calling out the actual providers they off-boarded by name? Why is OR basically protecting them under a cover of anonymity?

Lost a lot of trust in OR that's for sure, in-spite of some other positive reception I see here for this move.

Edit: Wording update.

show comments
angry_octet

Model routing was always insane. Until there is attestation from the providers and encryption of the session the temptation to peek will be too great.

g-b-r

I hope this time this stays on the frontpage, every LLM user should be aware of it.

There's also a good article at https://arstechnica.com/security/2026/11/a-leaky-ai-supply-c... , and a few earlier comments at https://news.ycombinator.com/item?id=50582794 , https://news.ycombinator.com/item?id=50585962 and https://news.ycombinator.com/item?id=50562582 .

Ungh

As usual, if you really give a shit about your data, don’t give it to someone else.

solarkraft

With this change, everything is good in the world and we can just take everyone’s word that they’re actually ZDR without any audits or technical enforcement again. Right?

cobychapple

Zero data retention, give or take 125 endpoints.

neuroelectron

Of course, the entire point of running an inference provider is stealing sensitive proprietary data. What are they gonna do? sue for copyright infringement?

g-b-r

This revealed something as delightful as a purported TEE provider having their "software TEE" root keys hacked, through "a legacy internet-facing service with management interfaces that relied on loopback access for trust and did not independently authenticate callers" (https://phala.com/posts/phala-november-preliminary-incident-...)

show comments
Havoc

Solid move.

Though frankly I would think anyone even slightly bothered about ZDR does not start their train of thought with "OK so we're going to put a middle man in"

show comments