# Cairn exposed panels / AIA0001–AIA0003

- ID: cairn-norforge-2026-10
- Reported: 2026-10-19
- Researcher: Snorre Fagerland
- Organization: NorForge
- AI role: attacker_uses_ai_as_operator (AI as operator)
- Offensive frameworks: cairn
- Confidence in AI involvement: not assessed
- Research / borderline: false
- Last reviewed: 2026-11-05
- Entry page: https://openattacks.ai/attacks/cairn-norforge-2026-10/
- Entry JSON: https://openattacks.ai/api/attacks/cairn-norforge-2026-10.json
- Browse title: Cairn: coding agents automate web exploitation
- Editorial summary: Exposed operator panels revealed coding agents repeatedly attempting known web exploits against commerce and payment sites. Success was reported for roughly 10% of tasks.
- Evidence class (catalog annotation): Reported campaign
- Source-stated target environments: Web applications
- Stage hunts and conditional defenses: https://openattacks.ai/api/defenses/cairn-norforge-2026-10.json

## Technique
Operators run open-source Cairn harnesses that loop AI coding agents toward intrusion goals (unauthenticated RCE, uploader shells). Panels ship with no login and Compose binds 0.0.0.0:8000, so NorForge and scanners could read task text, tooling, and secrets. AI did not invent new exploits; it made patient web exploitation cheap (~10% success, ~23h to goal). Oct 26 update: NorForge discovered threat actors AIA0009/AIA0010 hijacking exposed Cairn panels themselves, harvesting SSH keys and operator secrets from compromised panels, deploying Poseidon RAT to take over panel infrastructure and pivot to operators' own systems.

## Stack relevance (editorial)
Assessment: attacker\_tool\_only. Editorial applicability reviewed against the catalog source account; not a scan or independent incident verification.
The named AI product is used by the attacker. No reviewed mapping from owning that product to the reported victim conditions is available.
A product mention alone is not a victim-side applicability mapping. Selection does not verify affected versions, permissions or compromise.

## Initial access
Unauthenticated web RCE / upload / deserialization / SQLi-to-RCE chains against e-commerce and payment sites (task-driven); CVE-2026-75650 Magento lab tooling observed on workers

## AI tooling and models
- [Cairn](https://github.com/oritera/Cairn) (open source AI harness)
- [Claude Code CLI](https://github.com/anthropics/claude-code) via ANTHROPIC\_BASE\_URL to [DeepSeek](https://github.com/deepseek-ai)
- Worker label claudecode\_deepseek-v4.1-flash (AIA0001)
- pi\_openrouter\_deepseek (AIA0002)
- --dangerously-skip-permissions
- Agent skill .agents/skills/tsec-actions/SKILL.md (CTF leftover)

## Other tooling
- [Playwright](https://github.com/microsoft/playwright)
- [PHPGGC](https://github.com/ambionics/phpggc)
- [Nmap](https://github.com/nmap/nmap)
- [ffuf](https://github.com/ffuf/ffuf)
- [Amass](https://github.com/owasp-amass/amass)
- [dnsrecon](https://github.com/darkoperator/dnsrecon)
- StyleSmuggler PoC
- [Magento Open Source](https://github.com/magento/magento2) 2.4.9 lab — Links to Magento upstream; the reported lab repository is not identified.
- [Docker](https://github.com/moby/moby)
- [PHP](https://github.com/php/php-src)
- [Python](https://github.com/python/cpython)
- [OpenSSL](https://github.com/openssl/openssl)

## Victims and sectors
E-commerce / payment / merchant sites; AIA0001 mostly US, Japan, Australia; AIA0002 merchant/gray-market/pharma and some African commerce; Reuters-reported one operator into 100+ sites

## Target geography
- United States
- Japan
- Australia
Reported target geography includes the United States, Japan and Australia. Canada appeared in task text and African commerce was suggested by hints; those unconfirmed locations are excluded from country counts.

## Attribution
NorForge AIA0001 (Chinese language, CGI Global Limited / AS56594, high confidence), AIA0002 (English, Vultr/AS20473, high), AIA0003 (AlexHost, low). Financially motivated.

## Scale and metrics
20+ malicious exposed panels; AIA0001 1,100+ projects across 14 panels; ~10% success; ~\<$5/task estimate; \<23h start-to-goal; TruffleHog hundreds of secrets (11% verified); Censys: 24 stock Cairn panel hosts

## Attack flow
Catalog reconstruction of the supplied source account. Unknowns and research caveats are preserved.
### step-1: Operator assigns an intrusion goal [access]
Cairn workers receive tasks against web, commerce and payment sites.
Evidence: https://norforge.com/blog/inside_cairn

### step-2: Coding agents plan and retry [ai]
The harness loops Claude Code or other agent backends toward the goal.
Evidence: https://norforge.com/blog/inside_cairn

### step-3: Existing exploitation tools run [execution]
Workers attempt web RCE, upload and related exploitation chains.
Evidence: https://norforge.com/blog/inside_cairn

### step-4: Some tasks obtain access [impact]
The research reports roughly 10% success; exposed harness panels also revealed operator tasks and secrets.
Evidence: https://norforge.com/blog/inside_cairn

Connections:
- step-1 -> step-2
- step-2 -> step-3
- step-3 -> step-4

## 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: 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-2: Provider-side abuse investigation
- Visibility: Provider / operator records
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/provider.sigma.yml
- KQL query download: /api/detections/provider.kql
- SPL query download: /api/detections/provider.spl
- Hunt hypothesis: A model-provider investigation correlates related accounts, repeated offensive requests and shared infrastructure or exposed operator sessions.
- Required telemetry: Provider-owned account / request audit; Abuse-review findings and linked-account context; Lawfully available exposed operator-session evidence
- Investigate: Correlate accounts, request rates, infrastructure and source-described behavior in provider-owned records.
- Investigate: For victim-side defense, pivot to the reported execution or access stage rather than trying to detect attacker-side prompts.
- Limitation: Attacker-side planning is generally absent from victim SIEM logs. These templates require provider-owned audit data and do not identify AI use from a victim process alone.
- No direct MagicSword prevention claim is recorded for this stage.
- Community intelligence: LOLSkills — https://lolskills.io

### step-3: Web exploitation → host activity
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/web.sigma.yml
- KQL query download: /api/detections/web.kql
- SPL query download: /api/detections/web.spl
- Hunt hypothesis: Repeated exploit or upload requests are followed by an unexpected server process, file, or outbound connection.
- Required telemetry: Reverse-proxy / WAF request logs; Server process and file events; Outbound DNS / proxy records
- Investigate: Join requests to the affected host and process tree by time and request ID.
- Investigate: Inspect uploaded files and server-spawned shells; distinguish authorized testing from exploitation.
- Limitation: A scan or high request rate alone does not prove compromise or AI use. Host telemetry is needed to confirm execution.
- No direct MagicSword prevention claim is recorded for this stage.
- Community intelligence: GTFOBins — https://gtfobins.github.io

### step-4: Web exploitation → host activity
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/web.sigma.yml
- KQL query download: /api/detections/web.kql
- SPL query download: /api/detections/web.spl
- Hunt hypothesis: Repeated exploit or upload requests are followed by an unexpected server process, file, or outbound connection.
- Required telemetry: Reverse-proxy / WAF request logs; Server process and file events; Outbound DNS / proxy records
- Investigate: Join requests to the affected host and process tree by time and request ID.
- Investigate: Inspect uploaded files and server-spawned shells; distinguish authorized testing from exploitation.
- Limitation: A scan or high request rate alone does not prove compromise or AI use. Host telemetry is needed to confirm execution.
- Qualification: Success is reported in aggregate. Confirm a host-side effect for an individual task before treating a probe as successful access.
- 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.
- AML.T0016.002: Generative AI — The supplied source explicitly describes generative-model tooling assisting the reported activity; this mapping does not establish additional autonomy or victim impact.
  Technique: https://atlas.mitre.org/techniques/AML.T0016.002
  Evidence: https://norforge.com/blog/inside_cairn

## Defensive notes
Default-deny / GTFOBins-style block of nmap, python, php, openssl on web servers that do not need them; scan agent skills before load (LOLSkills); do not expose harness panels

## Sources
- https://norforge.com/blog/inside_cairn — NorForge: Inside Cairn - Exposed AI Agent Panels (AIA0001-AIA0003)
- https://norforge.com/blog/automated-subversion-attempted-takeover — NorForge: Cairn Panels Hijacked - AIA0009/AIA0010 Deploy Poseidon RAT

## Source notes
Jose post credits Reuters for the 100+ sites figure; exact Reuters article URL not captured in Typefully text.
