DeepSeek and Moonshot were quietly relaying customer prompts to Claude
. DeepSeek and Moonshot were quietly relaying customer prompts to Claude Why it matters for engineering teams What shipped and who is affected.
By Dillip Chowdary • Oct 04, 2026 • Source: HN Claude/Codex/Fable
DeepSeek and Moonshot were quietly relaying: what actually changed
HN Claude/Codex/Fable reports: DeepSeek and Moonshot were quietly relaying customer prompts to Claude. Article URL: https://twitter.com/IntCyberDigest/status/2098149671957103005 Comments URL: https://news.ycombinator.com/item?id=49653063 Points: 1 # Comments: 1
DeepSeek and Moonshot were quietly relaying: how it works
International Cyber Digest@IntCyberDigest‼️ BREAKING: Chinese labs DeepSeek and Moonshot were quietly relaying customer prompts to Claude through fraudulent accounts. Users thought they were using Chinese AI, but were actually getting answers from Claude.
Advertisement
Tech Pulse Daily
Get tomorrow's pulse first
Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.
DeepSeek and Moonshot were quietly relaying: why it matters now
One user, who is tied to China's military, asked Kimi whether a person tracked across hundreds of CCTV cameras in Chengdu was behaving abnormally. DeepSeek passed along live credentials for a Russian government database, shared by an IT operator handling data from a Defense Ministry-linked agency.
DeepSeek and Moonshot were quietly relaying: who is affected
The two Chinese labs relayed customer prompts to Claude through fraudulent accounts and saved the exchanges to train their own models. See the full write-up from HN Claude/Codex/Fable via the source link for quotes and complete context.
DeepSeek and Moonshot were quietly relaying: what to watch
Moonshot forwarded almost 300,000 customer requests in a single ten-day stretch. DeepSeek flagged users running its models inside coding tools like Claude Code and OpenCode, then routed some of them to Opus.8:40 PM · Sep 10, 2026·1.5MViews5051.2K9.5K3.1K
Developer Action Items
- ☐ Verify the claim on the official Claude / Opus / Codex page (or HN Claude/Codex/Fable), not from this recap alone.
- ☐ Name the surface that moved — API, policy, model, hardware, or commercial terms — before you Slack the thread.
- ☐ Assign one owner a day to read the primary material and decide: this-sprint, this-quarter, or noise.
- ☐ Do not change production on day-one coverage. Watch the vendor changelog and one independent write-up first.
Author
Dillip Chowdary
Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.
Related on Tech Bytes
Advertisement