# ARTEX planner agent API reconnaissance and exploitation

- ID: unit42-artex-api-recon-2026-10
- Reported: 2026-10-30
- Researcher: Ben Magee, Will Cates
- Organization: Unit 42 (Palo Alto Networks)
- AI role: attacker_uses_ai_as_operator (AI as operator)
- Offensive frameworks: artex
- Confidence in AI involvement: high
- Research / borderline: false
- Last reviewed: 2026-11-04
- Entry page: https://openattacks.ai/attacks/unit42-artex-api-recon-2026-10/
- Entry JSON: https://openattacks.ai/api/attacks/unit42-artex-api-recon-2026-10.json
- Browse title: ARTEX planner agent API reconnaissance and exploitation
- Editorial summary: ARTEX planner agent activity observed Sep 24-Oct 27 2026 by Unit 42. Agent autonomously harvested source maps, OpenAPI specifications, and runtime-config.json files. Attempted OAuth redirect URI abuse and…
- Evidence class (catalog annotation): Not classified
- Source-stated target environments: Not specified
- Stage hunts and conditional defenses: https://openattacks.ai/api/defenses/unit42-artex-api-recon-2026-10.json

## Technique
ARTEX planner agent activity observed Sep 24-Oct 27 2026 by Unit 42. Agent autonomously harvested source maps, OpenAPI specifications, and runtime-config.json files. Attempted OAuth redirect URI abuse and password spraying. Successfully self-registered on exposed APIs without authentication. Read approximately 50 MB of data. Wrote data to an unauthenticated development document store. Microsoft tracks related activity as Storm-0940 with Oct 21 observations. Unit 42's Nov 11, 2026 post (Cuong Dinh, Richard Emerson, Samantha Stallings), ARTEX and AI-Powered Red Teaming Tools, adds incident-response and Managed Threat Hunting cases where ARTEX turned password-reset pages and exposed APIs into cloud access in under a day. Behavioral hallmarks in that post: bursts of one to 14 requests about a second apart, then a pause of 25 to 31 seconds; a pivot within a minute of a credential download; more than 200 client secrets validated in about three minutes; a GET to the same path after almost every successful write; canary values evil.com, test@example.com, and deadbeefdeadbeefdeadbeef12; and polling every 48 seconds. As of October 2026 Unit 42 counted 609 internet-facing ARTEX hosts and 1,323 CyberStrikeAI hosts, with 21 running both. The framework is https://github.com/RuoJi6/ARTEX.

## 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
Exposed API endpoints without authentication

## AI tooling and models
- [ARTEX](https://github.com/RuoJi6/ARTEX) planner agent — Community-maintained fork; the original repository is unavailable.
- Autonomous API reconnaissance

## Other tooling
- Source map harvesting
- OpenAPI specification parsing
- OAuth redirect abuse attempts
- Password spraying
- API self-registration

## Victims and sectors
Organizations with exposed APIs and unauthenticated development endpoints

## Target geography
- Multiple regions
Multiple regions reflects API reconnaissance patterns observed by Unit 42

## Attribution
Microsoft Storm-0940 (related activity Oct 21)

## Scale and metrics
Activity Sep 24-Oct 27 2026; approximately 50 MB data read; wrote to unauthenticated document store

## Attack flow
Catalog reconstruction of the supplied source account. Unknowns and research caveats are preserved.
### recon: Agent harvests API metadata [access]
ARTEX planner agent autonomously collected source maps, OpenAPI specifications, and runtime-config.json files from exposed endpoints
Evidence: https://github.com/PaloAltoNetworks/Unit42-timely-threat-intel/blob/main/2026-10-30-activity-using-ARTEX-agentic-AI.txt

### exploit-attempts: OAuth and credential attacks attempted [ai]
Agent tried OAuth redirect URI abuse and password spraying
Evidence: https://github.com/PaloAltoNetworks/Unit42-timely-threat-intel/blob/main/2026-10-30-activity-using-ARTEX-agentic-AI.txt

### registration: Self-registration on exposed APIs [execution]
Successfully registered accounts on APIs without authentication controls
Evidence: https://github.com/PaloAltoNetworks/Unit42-timely-threat-intel/blob/main/2026-10-30-activity-using-ARTEX-agentic-AI.txt

### data-access: Approximately 50 MB data read [impact]
Agent read substantial data from compromised APIs
Evidence: https://github.com/PaloAltoNetworks/Unit42-timely-threat-intel/blob/main/2026-10-30-activity-using-ARTEX-agentic-AI.txt

### data-write: Data written to unauthenticated store [impact]
Wrote collected data to unauthenticated development document store
Evidence: https://github.com/PaloAltoNetworks/Unit42-timely-threat-intel/blob/main/2026-10-30-activity-using-ARTEX-agentic-AI.txt

Connections:
- recon -> exploit-attempts
- exploit-attempts -> registration
- registration -> data-access
- data-access -> data-write

## 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.
### recon: 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.

### exploit-attempts: 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.

### registration: 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.

### data-access: 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.

### data-write: 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.T0016.002: Generative AI — ARTEX planner agent autonomously conducted API reconnaissance and exploitation
  Technique: https://atlas.mitre.org/techniques/AML.T0016.002
  Evidence: https://github.com/PaloAltoNetworks/Unit42-timely-threat-intel/blob/main/2026-10-30-activity-using-ARTEX-agentic-AI.txt

## Defensive notes
Authenticate all API endpoints including development; remove source maps from production; restrict OpenAPI spec access; validate OAuth redirect URIs; implement API registration controls; monitor for automated reconnaissance patterns; detect bulk configuration file access; alert on unauthenticated document store writes; review Storm-0940 indicators

## Sources
- https://github.com/PaloAltoNetworks/Unit42-timely-threat-intel/blob/main/2026-10-30-activity-using-ARTEX-agentic-AI.txt — Activity using ARTEX agentic AI
- https://unit42.paloaltonetworks.com/artex-and-ai-powered-red-teaming-tools/ — ARTEX and AI-Powered Red Teaming Tools: What Defenders Need to Know

## Source notes
Microsoft tracks related activity as Storm-0940 with Oct 21 observations Relevant detection rules: - Monitor for bulk access to source map files (.map.js, .js.map) - Alert on OpenAPI specification downloads (openapi.json, swagger.json, api-docs) - Detect runtime-config.json and similar configuration file access patterns - Monitor for OAuth redirect URI manipulation attempts - Alert on password spraying patterns (multiple authentication attempts across accounts) - Detect unauthenticated API registration/account creation - Monitor writes to development document stores from unexpected sources - Track volume of API data reads (spike detection for ~50 MB threshold) - Note: API reconnaissance detection typically requires application-level logging, WAF rules, and API gateway monitoring. No direct Sigma rules exist for OpenAPI/source map harvesting; requires custom rules based on web server access logs and application audit trails. 
