Hacker News
AI Supply Chain Security: What Canary Tokens Found
jofzar
|next
[-]
Openrouters response.
Honestly I'm not sure how anyone could ever trust them for ZDR ever again, they don't seem to be doing their due diligence. (See data residency below)
> This wasn’t limited to requests sent to the lab directly. Several U.S. hosting providers resell this lab’s models, and prompts sent to those providers triggered the exact same scraper – the prompts were flowing back to the lab. A customer who picked a U.S. provider specifically to keep their data in the U.S. didn’t get what they paid for.
Edit: Thinking on this more, I don't see how they could have offered ZDR unless the "provider" has more skin in the game then them. The reason you trust Amazon/google with ZDR is because if they break contract/get caught out it will be a massive lawsuit and social/industry backlash.
"Providers" via openrouter don't have that skin in the game, all the reputation is with openrouter and now that the trust chain is broken, I don't see how anyone in good faith could ever use them for their "zdr" or "hosting" location ever again.
Joeri
|root
|parent
[-]
We are adapting the researchers’ testing approach so we can run these checks on an ongoing basis.
If providers are regularly canary tested by them it is not a perfect guarantee, but it does reduce risk by a lot. There is no way to have an ironclad ZDR promise, as even root inference providers in a direct API contract could be hacked or have retention misconfiguration. But there are many different levels of data risk and OpenRouter should be able to do a lot of risk reducing work. Let’s see what they do with that.
jofzar
|root
|parent
|next
[-]
> There is no way to have an ironclad ZDR promise, as even root inference providers in a direct API contract could be hacked or have retention misconfiguration.
Then they should never offer it and it's crazy they still are, if you can't verify that zdr is actually happening and enforce it yourself then wtf are you doing. Putting "canaries" in when you offer the service doesn't work.
I'm going to be surprised if legally openrouter can survive this.
matltc
|next
|previous
[-]
ffsm8
|root
|parent
[-]
Let me contextualize this my pointing out that I wouldn't trust openrouter zdr either. From my perspective this was always as suspect as it could be.
However, anthropic explicitly states in their TOS that they will conditionally train on your input and output even if you disabled it via the checkbox in your profile - at least in the publicly readable TOS, enterprises that go through the API (not sub) will likely be able to get more into their contact which I obviously wouldn't know of...
So if you think your data is secure while using cc, you'd still have shot yourself, the difference would be basically only with a pistol vs a shotgun on openrouter
DotNetCorePowa
|next
|previous
[-]
I am glad I didn't pick OR, but now can I trust the Belgian company... Hmm...
Rebelgecko
|next
|previous
[-]
jwrallie
|root
|parent
|next
[-]
Enabling ZDR already increases latency as it limits the providers used, and I noticed worse performance due to quantization as well for some of those providers.
If the data is being leaked anyway, there is little point in using this function at all, and OpenRouter’s only remaining selling point is how easy it is for changing providers. Might as well stick to the main providers.
paweladamczuk
|root
|parent
|previous
[-]
Nevertheless, a huge disappointment by the entire ecosystem, including Openrouter.
throwaway7356
|next
|previous
[-]
Wow, there are still security companies that haven't heard of residential proxies? Which are extremely widely used in AI circles.
And companies ignoring privacy rules is industry best-practice. I would be surprised if major voyeurism companies like Meta or Microsoft would respect anything.
inkysigma
|root
|parent
[-]
TZubiri
|next
|previous
[-]
The opinion is very bland however, be opinionated.
>How to fix >1. Host it yourself >2. Or o directly to a first-tier provider. >3. Use routers with care.
I thought option 1 was a bit extreme, option 2 is the obvious response. But whatever. Now option 3? How about do not use routers?
Genuine question, did you generate this part with an LLM?
I'd rather be concise and have a single solution. Self hosted is a bit too much, using OpenAI API directly for example does not suffer from this issue. And using routers with care means nothing, and the gravity of this issue is big enough to fire a vendor, not to slap a wrist and 'be careful next time'
Here is my advisory, fire any and all API token aggregators, use 1 vendor and connect directly.