AI Risk Wire

Cases › security breach › LR-2026-0815

CL-UNK-1211 espionage campaign against government Linux infrastructure using suspected AI-generated scripts and SysGoRAT

Confirmed Why: 2 independent outlets · 2 independent reports

Developing: a major or severe case captured in the last 72 hours. Later changes are logged on the corrections page.

Status: no action reported

Severity major
Reported 2 Nov 2026
Industry Public Administration

No source states: loss or records, developer and model, agent tool, could do, deployer.

Severity major: a live production compromise of government and state-linked Linux infrastructure, with database dumping and government mailbox exfiltration attempted, though no loss figure or count is stated.

Between October 2025 and April 2026, a threat actor tracked as CL-UNK-1211 targeted Linux systems associated with government entities and state-linked infrastructure, conducting reconnaissance, maintaining persistent access and attempting to collect sensitive information. The campaign combined open-source tools, custom backdoors and persistence techniques, including the Go-written SysGoRAT remote access trojan, credential harvesting via a malicious .bashrc and injected PHP login pages, and attempts to dump databases and exfiltrate government mailboxes. Several PHP and shell scripts appeared to have been generated with the help of AI, containing conversational, step-by-step reasoning notes. A bash script named zip_mails.sh failed during execution due to syntax errors. The attackers also attempted to disable endpoint protections, remove system logs and plant misleading red-team artefacts. The finding does not establish which AI system may have been used.

What happened

No source tells the story step by step yet.

What was done

No source states an action or fix.

Risks

Data leaked or sent out
Primary45 incidents
AI used to run a cyber attack
Also88 incidents
Rising: 25 vs 3.8 a week
AI system attacked or breached
Also22 incidents

Sorted by rule from the case's fields; not yet read from the sources.

Controls

Not yet read for controls. Controls that mitigate the primary risk:

Harness

Network egress control

Application

Sensitive-data checks on outbound data · Output filtering and redaction · Human approval for high-impact actions · Data minimisation · Least-privilege access for the agent · Activity logs

Evidence

No source states: a step-by-step account, when it happened, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case, the cause, what set it off, what was done.

Show every field, with its source and grade

What happened

Earliest source we hold
2026-11-02
D inferred by us from the described behaviour, reason shown
Themes
AI assisted hacking, cyber espionage, credential harvesting, data exfiltration, government infrastructure, linux malware, remote access trojan
C one secondary source states it
Who was responsible
an outside party
C one secondary source states it
Who caused it
an outside attacker
C one secondary source states it
What went wrong
security breach
C one secondary source states it
AI agent
an AI agent acted
C one secondary source states it
What it did
The document attributes AI-generated or AI-agent-deployed scripts to reconnaissance, persistence and exfiltration activity, but does not describe the agent's own failure mechanism; classification is inferred from the described behaviour.
C one secondary source states it

Impact

Severity
major
C one secondary source states it
Kind of harm
privacy, others' security, operations
C one secondary source states it
Who was affected
Government and state-affiliated Linux infrastructure
C one secondary source states it
Kinds of data exposed
credentials, e-mail
C one secondary source states it
Why this severity
a live production compromise of government and state-linked Linux infrastructure, with database dumping and government mailbox exfiltration attempted, though no loss figure or count is stated.
C one secondary source states it

Context

Industry
Public Administration
C one secondary source states it

Notes on gaps

The campaign window (October 2025 to April 2026) is given but no specific incident date. Extractor proposed values without quotes; dropped: . No dates for individual intrusions, no loss figures, no record counts, and no affected jurisdiction are stated. The campaign window (October 2025 to April 2026) is given but no single event date. The second half of the article describes separate threat-actor use of ARTEX, PentAGI, Hexstrike and CAIRN frameworks but gives no concrete dated incident with loss, so it was not extracted as a separate record. Extractor proposed values without quotes; dropped: . Extractor quotes not found verbatim in document; dropped: .

LR-2026-0815 · version 1 · published 2026-11-03 after automatic checks; not yet checked field by field by a person · JSON