Cases › security breach › LR-2026-0612
Claude Code and DeepSeek used in Chinese cyber espionage campaign
Preliminary Why: 1 report: Security Affairs · subject to change · 1 independent report
Developing: a major or severe case captured in the last 72 hours. Later changes are logged on the corrections page.
Status: action reported, no fix
No source states: loss or records, could do, deployer, industry.
Severity major: Test: many third parties, meaning a stated count of two or more affected parties. Fact: the report states two of eight organizations in Taiwan were successfully exploited, and government systems in Thailand and Afghanistan were compromised.
Security researchers at Hunt.io found an active intrusion campaign in which Claude Code and DeepSeek-v4-pro were working parts of the intrusion. The recovered logs show the attackers split the work between two AI models: Claude Code 2.1.165 handled execution, and DeepSeek-v4-pro handled planning, script generation and attack technique choice. Targets included government administrative systems in Thailand and Afghanistan, eight organizations in Taiwan with two successfully exploited, and financial services firms in several regions. The researchers found the campaign while pivoting on known command-and-control infrastructure, and an open directory on one server exposed the operators' source code, exploit scripts and logs. Hunt.io notified the affected organizations and national CERTs on July 6, 2026, and held publication for a seven-day disclosure window.
What happened
What was done
Risks
Primary96 incidents
Rising: 24 vs 4.0 a week
Read from the sources; not yet reviewed by a person.
Controls
Not yet read for controls. Controls that mitigate the primary risk:
ModelSafety training and refusal · Cyber and weapons safeguards · Abuse monitoring and account enforcement · Staged or restricted release · Dangerous-capability testing before release · Outside red-teaming · Content safety classifiers · Safeguards kept on in testing · Reasoning monitoring
Infrastructure / targetKnown flaws patched · Multi-factor sign-in and password policy · Network segmentation · Intrusion and endpoint detection · Backups and recovery · Phishing and fraud filters
Evidence
No source states: what the AI was doing, what it reached or did, when it was found, how many records were exposed, the direct loss, any court case, the cause, what set it off.
Model versions this case names
Each link opens what the provider's documents state for that version, who tested it, and the safeguards it describes.
Show the full account: 4 items from the primary sources
What happened, in order
- June 2026 Hunt.io researchers found an active intrusion campaign while pivoting on known TencShell command-and-control infrastructure.
- June 8 through 12, 2026 Timestamps on the recovered files span June 8 through 12, 2026.
- June 18-19 Three servers sharing SSH keys were actively maintained as recently as June 18-19, when all three reissued their ARL certificates together.
- July 6, 2026 Hunt.io notified the affected organizations and national CERTs.
Show every field, with its source and grade
The AI system
What happened
Impact
LR-2026-0612 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON