# CL-UNK-1211 AI-assisted Linux government campaign

- ID: cl-unk-1211-unit42-2026-10
- Reported: 2026-10
- Researcher: Roey Porat, Tom Fakterman
- Organization: Unit 42 (Palo Alto Networks)
- AI role: llm_generated_malware (LLM-generated malware)
- Confidence in AI involvement: not assessed
- Research / borderline: true
- Last reviewed: 2026-10-20
- Entry page: https://openattacks.ai/attacks/cl-unk-1211-unit42-2026-10/
- Entry JSON: https://openattacks.ai/api/attacks/cl-unk-1211-unit42-2026-10.json
- Browse title: CL-UNK-1211 AI-assisted campaign on government Linux servers
- Editorial summary: Espionage-style intrusions on government Linux servers used web shells, privilege escalation, SysGoRAT and tunnels. The code looks LLM-generated, but a live AI operator is not confirmed.
- Evidence class (catalog annotation): Reported campaign
- Source-stated target environments: Linux
- Stage hunts and conditional defenses: https://openattacks.ai/api/defenses/cl-unk-1211-unit42-2026-10.json

## Evidence qualification
AI role is payload generation / LLM-style comments in scripts, not confirmed live agent operator. Unit 42 says code consistent with LLM generation or automated AI agent.

## Technique
Espionage-style ops on government Linux (Oct 2025–Apr 2026): web shells with PHP auto\_prepend\_file persistence, sudo password alias in .bashrc, PwnKit/LinPEAS privesc, SysGoRAT, GSocket/revsocks/pysoxy tunnels, mailbox/social-media targeting, fake red-team markers.

## Stack relevance (editorial)
Assessment: mapped. Editorial applicability reviewed against the catalog source account; not a scan or independent incident verification.
First action: Review exposed web applications, web-worker child processes, persistence and tunnels.
- Relationship: environment; tools: no specific product; OS scope: linux; requires existing MCP connections: false.
  Relevance: The reported victim environment is Linux servers, including government targets.
  Condition to check: Source-specific initial access and host activity must be present.
  Condition to check: The source supports AI-assisted code generation, not a confirmed live AI operator.
  Evidence: https://unit42.paloaltonetworks.com/ai-campaign-targets-linux-infrastructure/
A product mention alone is not a victim-side applicability mapping. Selection does not verify affected versions, permissions or compromise.

## Initial access
Web shell deployment on Linux servers (custom and GitHub open-source shells)

## AI tooling and models
- LLM-assisted script generation (inferred from code artifacts)

## Other tooling
- SysGoRAT
- PwnKit CVE-2021-4034
- [LinPEAS](https://github.com/peass-ng/PEASS-ng/tree/master/linPEAS)
- [GSocket/gs-netcat](https://github.com/hackerschoice/gsocket)
- [revsocks](https://github.com/kost/revsocks)
- [pysoxy](https://github.com/MisterDaneel/pysoxy)
- React2Shell scanner CVE-2025-55182
- transfer.sh / bashupload / filebin / catbox

## Victims and sectors
Government entities and state-affiliated infrastructure

## Target geography
- unknown

## Attribution
CL-UNK-1211

## Scale and metrics
Activity window Oct 2025–Apr 2026; multiple C2 IPs listed in report

## Attack flow
Catalog reconstruction of the supplied source account. Unknowns and research caveats are preserved.
### step-1: Web shells land on Linux servers [access]
The campaign targets government and state-affiliated infrastructure.
Evidence: https://unit42.paloaltonetworks.com/ai-campaign-targets-linux-infrastructure/

### step-2: Persistence and privilege tooling [execution]
Reported steps include PHP persistence, sudo credential capture and privilege-escalation tools.
Evidence: https://unit42.paloaltonetworks.com/ai-campaign-targets-linux-infrastructure/

### step-3: Scripts show signs of AI assistance [ai]
Conversational code comments support an inference of AI-assisted generation, not confirmed live agent control.
Evidence: https://unit42.paloaltonetworks.com/ai-campaign-targets-linux-infrastructure/

### step-4: Remote access and collection [impact]
SysGoRAT and tunneling tools support espionage-style operations.
Evidence: https://unit42.paloaltonetworks.com/ai-campaign-targets-linux-infrastructure/

Connections:
- step-1 -> step-2
- step-2 -> step-4
- step-3 -> step-2 (Code-artifact inference)

## Stage defense and hunting recommendations
Editorial recommendations, not validated coverage. Source-controlled query starters are drafts. Custom-schema examples require telemetry collection and field mapping; absence of a mapping means not assessed. MagicSword policy opportunities require managed Windows scope and enforcement.
### step-1: Linux web worker → shell / interpreter
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: native
- SIGMA query download: /api/detections/linux-webshell.sigma.yml
- KQL query download: /api/detections/linux-webshell.kql
- SPL query download: /api/detections/linux-webshell.spl
- Hunt hypothesis: A PHP or web-server worker launches a shell, interpreter, or reconnaissance utility outside its normal baseline.
- Required telemetry: Linux process creation (EDR / auditd normalized to process fields); PHP / web access logs; File changes to web roots and PHP configuration
- Investigate: Trace the worker's children and correlate them with inbound requests.
- Investigate: Review auto\_prepend\_file, .bashrc changes, /dev/shm execution, and outbound tunnels where the report describes them.
- Limitation: Legitimate CGI, maintenance, and deployment scripts can match. The query is a process-tree starter, not a complete web-shell detector.
- No direct MagicSword prevention claim is recorded for this stage.
- Community intelligence: GTFOBins — https://gtfobins.github.io

### step-2: New persistence → recurring execution
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/persistence.sigma.yml
- KQL query download: /api/detections/persistence.kql
- SPL query download: /api/detections/persistence.spl
- Hunt hypothesis: A task, Run key, cron entry, shell profile, or startup file is changed and later launches the same unexpected program.
- Required telemetry: Platform-specific registry, scheduled-task, cron and startup-file changes; Process creation and file provenance; User / administrative change records
- Investigate: Diff the persistence artifact and identify the creating process / principal.
- Investigate: Correlate the subsequent launch and network behavior; baseline deployment and management agents.
- Limitation: Windows and Unix persistence require different collectors. A configuration change without a subsequent launch is not proof that persistence ran.
- No direct MagicSword prevention claim is recorded for this stage.

### step-3: Stage hunt not mapped yet
- Visibility: Not assessed
- Query origin: catalog_authored; status: not_assessed; log scope: gap
- Hunt hypothesis: A stage-specific hunt has not been reviewed for this part of the source account.
- Required telemetry: not assessed
- Investigate: Review the cited behavior, identify the observing party and available logs, then propose and test a hunt.
- Limitation: An unmapped stage does not mean it is undetectable or that no behavior occurred. It means this catalog has not supplied a reviewed hunt for it.
- Qualification: This stage is included for completeness; a query needs a reviewed link between the described behavior and logs available to the observing party.
- No direct MagicSword prevention claim is recorded for this stage.

### step-4: Sensitive data → unusual destination
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/exfil.sigma.yml
- KQL query download: /api/detections/exfil.kql
- SPL query download: /api/detections/exfil.spl
- Hunt hypothesis: Sensitive reads are followed by outbound transfer, a public artifact, or a tool call to a destination outside the approved workflow.
- Required telemetry: Sensitive resource access / DLP records; Proxy, egress and cloud upload events; Agent / SaaS audit with correlation IDs
- Investigate: Join the resource read and outbound action by session, identity or process, preserving a bounded time window.
- Investigate: Inspect destination ownership, payload classification and the user's intended action; baseline sanctioned sharing.
- Limitation: An outbound connection or high byte count alone is not exfiltration. Encrypted traffic may hide content, and bulk legitimate exports are common.
- No direct MagicSword prevention claim is recorded for this stage.


## MITRE ATLAS
Mappings are catalog annotations based on described behavior, not assignments or endorsements by MITRE.
No source-backed mapping is currently recorded.

## Defensive notes
Detect auto\_prepend\_file changes, \*.gsocket.io traffic, binaries from /dev/shm; Jose take: AI made old Linux tradecraft cheaper

## Sources
- https://unit42.paloaltonetworks.com/ai-campaign-targets-linux-infrastructure/
