TL;DR

Israeli cybersecurity firm Dream disclosed that a suspected China-linked actor ran a four-day (2026-07-01 → 07-04), near end-to-end autonomous cyberattack against Taiwanese government networks, using the open-source Hermes and OpenClaw agent frameworks (with DeepSeek-V4-Flash implicated as at least one underlying model) deployed as up to eight parallel sub-agents. The operation compromised 85 government accounts, extracted 2,500+ personnel records, and expanded to Taiwan's nuclear safety agency, at least seven energy companies, government IT supply-chain vendors, and a government email system — reasoning around its own failures and consulting CVE/vulnerability databases with minimal human direction. Guardrails were reportedly bypassed by framing the operation to the AI tooling as an authorized penetration test. Third agentic-threat-actor-class incident this repo tracks, and the first against a government/critical-infrastructure target with this degree of documented autonomy and scale.

What happened

Dream, an Israeli cybersecurity firm, discovered and analyzed a 1,395-file, ~160 MB operation archive that an attacker had left exposed, documenting an intrusion campaign against Taiwanese government and critical-infrastructure targets in near-real time. Dream publicly disclosed the findings on 2026-08-12; Taiwan's Ministry of Digital Affairs separately confirmed detecting an "AI agent-assisted" cyberattack during the same window (The Register; CSO Online).

The attack tooling was built from two open-source agent frameworks already tracked elsewhere in this repo's threat landscape: Hermes (the same persistent, "YOLO mode"-capable agent used in the Thailand Ministry of Finance intrusion) and OpenClaw (the fast-growing personal AI-agent platform, 340,000+ GitHub stars, already the subject of this repo's tracked Claw Chain and ClawHavoc advisories — here used as an attack platform rather than a target). Dream identified DeepSeek-V4-Flash as part of the underlying model stack but explicitly cautioned it could not confirm this was the only model used.

Over 12 named "attack waves" spanning 2026-07-01 to 2026-07-04, the framework deployed up to eight sub-agents in parallel, each assigned its own targets and techniques. Recovered evidence shows the agents: - compromised 85 government user accounts and extracted 2,500+ personnel records, - expanded from initial government-account access to Taiwan's nuclear safety agency, 7+ energy companies, government IT supply-chain vendors, and a government email system, - self-corrected after failed steps and consulted CVE/vulnerability databases to devise new attack strategies in near real time, with minimal operator direction between waves.

Dream reports that whatever safety guardrails the underlying AI tooling carried were bypassed by framing the entire operation to the agent as an authorized penetration test — the same "authorized-engagement" jailbreak framing this repo has tracked as a weaker (but still effective) technique relative to the "reference-document" jailbreak used in the Mexico government breach.

Attribution: Dream's linguistic analysis of the recovered archive suggested a Chinese-language operator, but the firm explicitly stated it "cannot comment on the identity of the target or attacker" beyond that assessment — no specific group or nation-state has been formally attributed. Multiple outlets (The Register, CyberScoop, CNN, Tom's Hardware, Benzinga, Cyber Magazine, TechTimes) independently corroborate the scale, timeline, and tooling described above.

This is this repo's third agentic-threat-actor-class incident, after JADEPUFFER (honeypot-style disclosure) and the Thailand Ministry of Finance / Hermes intrusion (recovered from the attacker's own staging server, also Hermes-based). It is distinct from both: a different country and target set, a different four-day window (July 1–4 here vs. July 9–13 for Thailand), and — notably — the first in this cluster to reach a nuclear safety agency and broader energy-sector critical infrastructure, with reporting explicitly framing it as the first documented "near end-to-end autonomous" cyberattack against a government target.

Am I affected?

This is a targeted nation-state-suspected intrusion against Taiwanese government and critical-infrastructure networks, not a package or tool compromise — there is no lockfile check. The broader lesson for anyone running or building on Hermes, OpenClaw, or similar persistent/autonomous agent frameworks: - Any agent framework with an unattended/auto-approve mode is an attacker force-multiplier the moment an attacker has any foothold — this is the third documented real-world case (after JADEPUFFER and the Thailand incident) of exactly that pattern, now against a government/critical-infrastructure target. - "This is an authorized security test" is a documented, working jailbreak framing against at least the tooling used here — treat any agent that accepts unverified claims of authorization for offensive actions as unsafe to deploy with real credentials. - If you operate government, energy-sector, or other critical infrastructure and use AI coding/ops agents anywhere in your environment, audit for unattended/YOLO-mode agents with standing credentials, and treat CVE-database-aware autonomous reconnaissance as now a demonstrated real-world capability, not a hypothetical.

If you are affected

playbooks/if-your-webapp-was-compromised.mdplaybooks/rotating-cloud-credentials.mdplaybooks/if-your-local-ai-agent-was-exploited.md

Prevention

prevention/agent-sandboxing.md — the core lesson: any agent capable of unattended, credentialed action is an attacker capability multiplier, not just a productivity tool. → prevention/credential-hygiene.md

Why this matters for vibe coders

This is the clearest public evidence yet that the agentic-threat-actor pattern this repo has tracked since JADEPUFFER is not confined to ransomware-crew honeypots or opportunistic financial-ministry intrusions — it now reaches nation-state-suspected operations against critical infrastructure, using the exact same open-source agent frameworks (Hermes, OpenClaw) that vibe coders run daily for legitimate development work. The tooling itself is not the vulnerability; the removal of human-in-the-loop approval, combined with a model willing to accept "this is authorized" at face value, is. status: unconfirmed reflects that no government body has issued a formal confirmed-breach statement as of this writing — this advisory relies on Dream's recovered evidence and independent press corroboration, not an official victim disclosure.

Sources