Build1 publisher3 min readPublished
Anthropic traces nearly 300,000 Kimi requests to an Opus model through 5,380 fraudulent accounts
The allegation reaches Kimi's consumer output, and it arrives with two sets of numbers that do not fit inside each other. Anthropic has not dated the traffic, so nobody outside can tie it to a Kimi release.
The Engineer · Build desk

What happened
- Anthropic alleged in a Bloomberg report published September 10th that Moonshot AI routed Kimi user requests through Claude models without telling the users who sent them.
- The specific cluster Anthropic described covers nearly 300,000 requests sent primarily to an Opus model through 5,380 fraudulent accounts that mostly appeared to operate from Singapore and Japan.
- Anthropic's own public report the same day describes a wider campaign of more than 3.4 million exchanges with Claude conducted through hundreds of fraudulent accounts.
- Anthropic attributed the activity using request metadata it said matched public profiles of senior Moonshot personnel, and said a later phase tried to reconstruct Claude's reasoning traces.
Compiled by The EngineerSomething wrong?How this is made
Why it matters
- decision A cloud negotiating a revenue share on K3 is now buying a model family whose serving path is in dispute, and the term that settles it has to be written into the contract because no downstream party can measure it.
- exposure If the routing happened as alleged, the users whose prompts moved are the ones with no record of where their data went or which provider's terms applied to it.
- contradiction Bloomberg and Anthropic's report name different third parties, so the secondhand figures deserve less weight than the primary report on everything the two do not agree about.
- constraint With no dates attached to the traffic, a buyer cannot scope the exposure to a version or a period, which leaves any diligence answer open-ended.
Anthropic says it does not allow its technology to be accessed from inside China [9]. That restriction is what makes this an account story. The traffic Anthropic described to Bloomberg came through accounts that mostly appeared to operate from Singapore and Japan [2], and Anthropic's report described proxy operators maintaining pools of accounts and replacing them when individual accounts were blocked [10].
Divide the two Bloomberg figures and the pool shows up in the arithmetic. Nearly 300,000 requests across 5,380 accounts is about 56 requests per account [12]. That is thin per-account volume for a data collection run at this scale. From the provider's side of the API, that pattern looks like accounts being cycled and replaced.
The two published figure sets do not nest. Anthropic's own report describes more than 3.4 million exchanges through hundreds of fraudulent accounts [3]; the narrower cluster Bloomberg describes carries 5,380 accounts [2], which is under nine percent of the exchanges and more of the accounts [13]. The source material does not say whether that is a different counting rule or a different population.
Attribution rests on request metadata that Anthropic said matched public profiles of senior Moonshot personnel [5]. That signal exists only inside the model provider. A cloud reselling weights, or a developer building on Kimi, has access only to the response and the bill, not to the metadata behind it.
Moonshot has been seeking up to 30% of revenue generated from K3 services on Azure, AWS and Google Cloud [7], after launching the 2.8-trillion-parameter mixture-of-experts model on July 16th and releasing its weights on July 27th [6]. A revenue-share arrangement on open weights is a contract about a model family. The routing allegation asks a different question: which model handled the user's prompt and produced the output the product displayed [8].
Distillation on its own is a standard training method, including when a provider distills its own systems [11]. The allegation concerns false accounts, proxy infrastructure and restricted access used to collect training data from a competitor at scale [4]. Routing requests among models is also ordinary practice, and it depends on disclosure, valid access and agreements governing how user data is processed [14].
What the public record does not carry is independent confirmation that Kimi's consumer product forwarded user prompts to Claude [15]. The timing of the alleged traffic is also unestablished, so nothing ties it to K3 or to any other Kimi release [16]. And the secondhand account differs from the primary one on who else is accused: Bloomberg reported that Anthropic accused DeepSeek and Xiaomi of similar conduct, while Anthropic's report named DeepSeek and MiniMax alongside Moonshot [17].
So the provenance question a buyer can act on is contractual. That means specifying which model serves the request, under whose access, and with what data terms in writing [14]. These numbers come from Anthropic's own request logs [5].
What to watch
- Whether Anthropic publishes dated traffic that would place the alleged routing against a specific Kimi release.
- Whether Moonshot responds to the routing allegation directly, separately from the distillation claim.
- Whether Azure, AWS or Google Cloud add model-provenance or serving-path terms to K3 distribution arrangements.