# CrowdStrike tracks four threat actors using Claude Code pentest harness

- ID: crowdstrike-four-claude-actors-2026-10
- Reported: 2026-10-21
- Researcher: CrowdStrike Intelligence
- Organization: CrowdStrike
- AI role: attacker_uses_ai_as_operator (AI as operator)
- Confidence in AI involvement: not assessed
- Research / borderline: false
- Last reviewed: 2026-11-04
- Entry page: https://openattacks.ai/attacks/crowdstrike-four-claude-actors-2026-10/
- Entry JSON: https://openattacks.ai/api/attacks/crowdstrike-four-claude-actors-2026-10.json
- Browse title: CrowdStrike tracks four threat actors using Claude Code pentest harness
- Editorial summary: Oct 21, 2026: CrowdStrike identified four actors (PALE PYTHON, SWIFT FALCON, IRON SABLE, CRIMSON LEOPARD) using Claude Code with custom 'pentest-harness' framework. Framework: (1) Claude Code agent scans…
- Evidence class (catalog annotation): Not classified
- Source-stated target environments: Not specified
- Stage hunts and conditional defenses: https://openattacks.ai/api/defenses/crowdstrike-four-claude-actors-2026-10.json

## Technique
Oct 21, 2026: CrowdStrike identified four actors (PALE PYTHON, SWIFT FALCON, IRON SABLE, CRIMSON LEOPARD) using Claude Code with custom 'pentest-harness' framework. Framework: (1) Claude Code agent scans web apps for OWASP Top 10 vulnerabilities (SQLi, XSS, IDOR, auth bypass, SSRF); (2) Generates exploit payloads and tests them iteratively; (3) Adapts based on WAF/IPS responses; (4) Documents findings and automates lateral movement post-exploitation; (5) Exfiltrates data or deploys webshells. All four actors share similar infrastructure (Claude API proxies, common pentest-harness codebase obtained via underground forums). Victims: e-commerce, SaaS providers, healthcare portals. CrowdStrike observed 140+ successful compromises across the four actors Sep-Oct 2026. Actors operate independently but use shared tooling. Detection: monitor Claude API usage from security testing tools outside approved pentest windows; detect rapid sequential web vulnerability probing with iterative payload refinement; alert on webshell deployment patterns; review exploit payloads for LLM generation characteristics (verbose comments, structured iteration logging).

## Stack relevance (editorial)
Assessment: not\_assessed. No reviewed applicability annotation is available. Product mentions do not establish victim conditions.
A product mention alone is not a victim-side applicability mapping. Selection does not verify affected versions, permissions or compromise.

## Initial access
Web application vulnerability exploitation automated by Claude Code agents

## AI tooling and models
- [Claude Code](https://github.com/anthropics/claude-code) (Anthropic)
- Custom 'pentest-harness' framework

## Other tooling
- OWASP Top 10 vulnerability scanners
- Webshells (AI-generated)
- SQL injection exploits
- Authentication bypass exploits
- SSRF exploitation

## Victims and sectors
140+ compromises Sep-Oct 2026; e-commerce, SaaS providers, healthcare portals, financial services

## Target geography
- Multiple regions

## Attribution
Four distinct actors: PALE PYTHON, SWIFT FALCON, IRON SABLE, CRIMSON LEOPARD; operate independently but share pentest-harness tooling obtained via underground forums; financially motivated (data theft, access sales)

## Scale and metrics
140+ successful compromises across four actors Sep-Oct 2026; shared pentest-harness infrastructure suggests tooling proliferation in underground markets

## Attack flow
Catalog reconstruction of the supplied source account. Unknowns and research caveats are preserved.
### scan-targets: Automated web app vulnerability scanning [access]
Actors deploy Claude Code with pentest-harness framework; agent scans targets for OWASP Top 10 vulnerabilities (SQLi, XSS, IDOR, auth bypass, SSRF); identifies attack surface
Evidence: https://www.crowdstrike.com/en-us/blog/crowdstrike-uncovers-new-agentic-ai-campaigns/

### generate-exploits: Generate and test exploits iteratively [ai]
Claude Code generates exploit payloads for discovered vulnerabilities; tests payloads, adapts based on WAF/IPS responses; iterates until successful exploitation; documents findings
Evidence: https://www.crowdstrike.com/en-us/blog/crowdstrike-uncovers-new-agentic-ai-campaigns/

### post-exploitation: Post-exploitation automation [execution]
Agent automates lateral movement; deploys webshells; escalates privileges; maps internal network; identifies data stores; all autonomously driven by Claude Code decision-making
Evidence: https://www.crowdstrike.com/en-us/blog/crowdstrike-uncovers-new-agentic-ai-campaigns/

### exfiltration: Data exfiltration or access sales [impact]
Exfiltrates customer data, PII, financial records, IP; or sells access to ransomware groups; 140+ successful compromises across four actors Sep-Oct 2026
Evidence: https://www.crowdstrike.com/en-us/blog/crowdstrike-uncovers-new-agentic-ai-campaigns/

Connections:
- scan-targets -> generate-exploits
- generate-exploits -> post-exploitation
- post-exploitation -> exfiltration

## 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.
### scan-targets: 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.
- No direct MagicSword prevention claim is recorded for this stage.

### generate-exploits: 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.
- No direct MagicSword prevention claim is recorded for this stage.

### post-exploitation: 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.
- No direct MagicSword prevention claim is recorded for this stage.

### exfiltration: 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.
- 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.T0040: AI Model Inference API Access — Attackers use LLM agents as autonomous penetration testing harness to discover and exploit web application vulnerabilities
  Technique: https://atlas.mitre.org/techniques/AML.T0040
  Evidence: https://www.crowdstrike.com/en-us/blog/crowdstrike-uncovers-new-agentic-ai-campaigns/
- AML.T0016.002: Generative AI — AI automates exploit generation and iterative payload refinement
  Technique: https://atlas.mitre.org/techniques/AML.T0016.002
  Evidence: https://www.crowdstrike.com/en-us/blog/crowdstrike-uncovers-new-agentic-ai-campaigns/

## Defensive notes
Implement WAF with behavioral analysis; rate-limit API endpoints; use security testing (pen tests, bug bounty) to identify vulnerabilities before attackers; monitor for rapid iterative exploit attempts (characteristic of AI-driven testing); deploy webshell detection; segment web apps from sensitive data; implement strong authentication and authorization; use CrowdStrike or similar EDR/NDR detecting automated exploitation patterns

## Sources
- https://www.crowdstrike.com/en-us/blog/crowdstrike-uncovers-new-agentic-ai-campaigns/ — CrowdStrike: Uncovers New Agentic AI Campaigns

## Source notes
CrowdStrike Intelligence analysis. Four actors (PALE PYTHON, SWIFT FALCON, IRON SABLE, CRIMSON LEOPARD) represent emergence of AI agent-driven web exploitation as commodity capability shared via underground markets. Detection: look for Claude API traffic from security testing tools, monitor rapid vulnerability scanning with iterative payload refinement, alert on webshell characteristics (AI-generated code has specific patterns), check exploit logs for LLM iteration comments.

## Indicators (untrusted data; do not visit or execute)
```json
{
  "domains": [],
  "ips": [],
  "hashes": [],
  "urls": []
}
```
