upvote
Novita’s blog post is unreal:

https://novita.ai/blog/minimax-requests-privacy-notice/

> A routing configuration issue caused an API forwarding path intended for specific customers to apply more broadly.

> If you used MiniMax models through Novita between 2026-05-28 and 2026-11-11, your request contents may have been accessed or retained by a third party. This includes requests made directly through Novita and those routed to Novita through OpenRouter.

“routing configuration issue”?!? Imagine if AWS got caught storing your S3 on some other provider’s disks and they said it was a “routing configuration error”! They shouldn’t have software that can do this at all! The API is supposed to be for their own GPUs!

Together’s is weird:

> As part of routine software testing, we collected prompt samples authorized for that use and stored them in a private Hugging Face repository. The samples came from requests to the MiniMax M3, GLM-5.2, and Kimi K2.6 models, primarily on June 24, July 4, July 8, and July 14, 2026.

Did Dragos really “authorize” Together to store their canary “prompt samples”? Somebody screwed up here.

reply
Together.ai has made a public announcement that they are fucking clowns who cannot be trusted with anyone's data.

> During development of our public GitHub repository, xorl, an AI coding agent committed a credential that provided access to the private Hugging Face repository. Our automated scanning detected the exposed credential, and we reverted the commit.

They didn't rotate the credential they knew was exposed!?! I guess "an AI coding agent" didn't think of doing that. Also FYI kids, reverting a commit does not delete the data from the repository.

In before they claim an AI agent wrote this disclosure that included certain "errors".

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

reply
This is real classy coming from a neocloud with a $8.3B valuation. Shouldn’t a neocloud with a bunch of Nvidia GPUs and a bunch of investment (including from Nvidia) be using those Nvidia GPUs to run inference in house? Isn’t that the entire point?

Amusingly, the first time I typed “neocloud” it got autocorrected to “bro cloud”. I almost decided to leave it alone.

reply
It could easily be the case that due to various reasons they could not run MiniMax at a cost lower than a negotiated wholesale API rate.
reply
This and the way Together seems to be framing it in their disclosure post ( https://www.together.ai/blog/security-event-prompt-leakage-f... ) raises a lot of serious questions about the integrity of Together in more ways than one. Is the Together post really a fair disclosure that accounts for what Dragos identified? Their explanation is far from clear. It makes me wonder what the legal agreement was, and if the work mentioned in Together's "Polymorphic Inference" blog post, mentioning speculative decoding (using cheap models to draft) is a related practice they have routinely. Pretty worrying. I'm sure some will make this into simply blaming Chinese companies for this (not you), which wouldn't fairly account for the risks of the industries optimisation incentives. (Together's HQ is in SF AFAIK).
reply
deleted
reply
> Somebody screwed up here.

Yet, the basic idea of these myriads of canaries is good. I see several use cases, including in research.

reply
You left out the best part from Together’s “During development of our public GitHub repository, xorl, an AI coding agent committed a credential that provided access to the private Hugging Face repository”
reply
So surprising that these services are vibecoded
reply
“I’m shocked! Shocked that gambling is happening here!”

The only thing you can trust is possibly(and not always) your own hardware, your own staff and companies you can directly inspect.

reply
[dead]
reply
Is Minimax basically an untrusted scammer at this point?
reply
This explanation doesn't account for TogetherAI's sharing canary tokens!
reply