AI Governance Institute
← News
Research2026-08-14

Open-Source AI Agents Used in Near-Autonomous Attacks on Taiwan Infrastructure

What happened

Presenting at Black Hat in August 2026, FBI Cyber Division leadership and former U.S. National Cyber Director Chris Inglis confirmed that suspected Chinese-linked operators had deployed two open-source AI agents, Hermes and OpenClaw, in near-autonomous attacks against Taiwanese government networks and energy sector targets. The full account in The Register describes the agents as capable of self-propagating through enterprise environments by detecting and exploiting common network misconfigurations without sustained human direction. Officials characterized free, open-weight models as having materially lowered the expertise barrier for attacks on industrial control systems and operational technology, making previously obscure attack paths accessible to a wider range of threat actors. The incident follows a pattern already visible in the autonomous AI agents breach of Taiwan's nuclear agency earlier this year, and reinforces concerns about commodity AI being weaponized in geopolitically motivated campaigns. Critically, both Hermes and OpenClaw are open-source models that any organization could theoretically host internally, meaning the same capabilities that enabled these attacks are available to adversaries globally without licensing or access controls.

Why it matters

  • ·Critical infrastructure operators and their enterprise supply chains now face a documented, active threat from AI agents that can propagate autonomously through networks: existing obscurity and perimeter controls are insufficient against agents that systematically probe for misconfigurations rather than relying on known exploits.
  • ·The use of open-source, open-weight models removes the procurement and access barriers that previously constrained sophisticated cyberattacks, meaning any organization's open-weight model intake policy and supply chain controls are now directly relevant to its threat surface, not just its AI ethics program.
  • ·Attribution by senior FBI and former White House cyber officials at a major public forum raises the likelihood of follow-on regulatory and sector guidance for critical infrastructure operators, particularly under frameworks governing operational technology risk, and compliance teams should expect new disclosure or assessment requirements to follow.

Governance controls affected

What to do now

  • Conduct an immediate review of your critical infrastructure AI risk assessment under SCT-003 to determine whether autonomous agent propagation scenarios are included in your threat model.
  • Audit your open-source model intake policy (PRC-005) to confirm that Hermes, OpenClaw, and similar open-weight models with known offensive capabilities are subject to a documented approval and containment process before any internal deployment.
  • Require your OT and ICS security teams to run a network misconfiguration review focused on the self-propagation vectors described in the Black Hat findings, including lateral movement through misconfigured credentials and trust relationships.
  • Escalate the Black Hat findings to your board-level AI risk committee and update your AI risk tolerance documentation to reflect that near-autonomous offensive AI use against critical infrastructure is now a confirmed rather than theoretical risk.
  • Review vendor and third-party contracts to confirm that suppliers with OT or ICS access have adequate controls against AI agent-based intrusion, and invoke incident notification requirements where exposure is unclear.

What to watch next

Compliance teams should monitor for sector-specific guidance from CISA, NERC, and equivalent bodies responding to the Black Hat disclosures, particularly any updates to critical infrastructure cybersecurity requirements that reference AI-enabled threat actors. The pattern of incidents targeting Taiwanese government and energy networks may also prompt updated export control guidance on dual-use AI models, given that Hermes and OpenClaw are open-weight models with no distribution restrictions. Broader regulatory signals around open-weight model governance are already emerging, and teams tracking the 89% surge in AI-enabled attacks and related incidents should anticipate that near-autonomous offensive AI will feature prominently in the next cycle of critical infrastructure protection rulemaking.

Stay ahead of stories like this

Get every Global AI governance development like this one, plus the rest of the week's developments. Every Thursday.

Powered by Buttondown.

Related Coverage

Corporate Policy2026-09-03

Commercial Guardrail-Removal Service Breaks Open-Weight Model Supply Chain Controls

Startup Abliteration.ai has built a commercial service that strips safety guardrails from open-weight AI models and resells API access to the modified versions, including Z.ai's GLM-5.3. TechCrunch testing confirmed the service readily produced credential-theft code and dangerous pathogen instructions on demand. The company operates without meaningful know-your-customer controls and has not defined its own responsibility boundaries.

Research2026-08-26

Exploited MLflow SSRF and AI-Generated PLC Attacks Converge on AI Infrastructure

The Cloud Security Alliance's August 23 CISO Daily Briefing flags two AI-infrastructure security findings with direct compliance implications. An actively exploited server-side request forgery flaw in MLflow is being used to steal cloud credentials from model-serving environments. A separate joint government advisory warns that AI-generated Python scripts are enabling attacks on Siemens S7 programmable logic controllers used in industrial settings.

Research2026-08-24

CVE-2025-9141 Makes Inference Engines a Governed Security Dependency

Independent security research published in August 2026 documents a concrete attack class in which a malicious LLM could exploit vulnerabilities in its own inference engine to execute arbitrary code on the host machine. The analysis cites CVE-2025-9141, an arbitrary-code-execution bug in vLLM's tool parser that was merged despite automated critical-severity warnings. Organizations self-hosting open-weight models are advised to separate GPU and token-parsing hosts and treat all inference engine output as untrusted.