ARTEX planner agent API reconnaissance and exploitation
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…
What happened
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.
How it happened
Read the flow as text & sources
A catalog reconstruction of the supplied source account. Unknown steps remain explicit; an edge describes the reported relationship between steps.
- 01 · Agent harvests API metadata
ARTEX planner agent autonomously collected source maps, OpenAPI specifications, and runtime-config.json files from exposed endpoints
Source for step 1 - 02 · OAuth and credential attacks attempted
Agent tried OAuth redirect URI abuse and password spraying
Source for step 2 - 03 · Self-registration on exposed APIs
Successfully registered accounts on APIs without authentication controls
Source for step 3 - 04 · Approximately 50 MB data read
Agent read substantial data from compromised APIs
Source for step 4 - 05 · Data written to unauthenticated store
Wrote collected data to unauthenticated development document store
Source for step 5
Why it matters
Reported entry point: Exposed API endpoints without authentication. Reported impact: Agent read substantial data from compromised APIs; Wrote collected data to unauthenticated development document store; reported targets include Organizations with exposed APIs and unauthenticated development endpoints; applicability to your setup has not been assessed, so verify affected versions, permissions, and configuration in the original report.
What you can do
Protection & prevention
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
Catalog defensive guidance based on the reported behavior. Confirm scope and current mitigations in the original source.
Technical detailsTooling, impact & MITRE ATLAS
Attack context
- AI's role
- AI as operator
- Offensive frameworks
- ARTEX
- Initial access
- Exposed API endpoints without authentication
Tooling as reported
AI products, models and artifacts
- ARTEX planner agentCommunity-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
Targets and reported impact
- Targets / sectors
- Organizations with exposed APIs and unauthenticated development endpoints
- Reported scale / exposure
- Activity Sep 24-Oct 27 2026; approximately 50 MB data read; wrote to unauthenticated document store
- Target geography
- Multiple regions
Multiple regions reflects API reconnaissance patterns observed by Unit 42
Reported attribution
Microsoft Storm-0940 (related activity Oct 21)
Structured attribution
- Actor
- Unnamed ARTEX operators; Microsoft tracks related activity as Storm-0940
- Country
- Unknown
- Motivation
- unknown
- Attributed by
- Unit 42, Microsoft
- Attribution confidence
- medium
Detection rules
- ARTEX API hallmarksGUIDANCE
security-detections-mcp searches for password spray returned Azure Identity Protection and dsacls rules. Those do not match ARTEX spraying an exposed application API. No cited rule encodes the canary values evil.com, test@example.com, or deadbeefdeadbeefdeadbeef12, the 25 to 31 second pause, or the 48 second recheck. Hunt OpenAPI and source-map downloads followed by a write and an immediate read of the same path.
Activity timeline
- First seen
- 2026-09-24
- Last updated
- 2026-11-11
Updates
- 2026-10-30 — Unit 42
Unit 42 publishes the Sep 24-Oct 27 ARTEX planner activity: source maps, OpenAPI files, unauthenticated self-registration, and about 50 MB read.
- 2026-11-11 — Unit 42
Unit 42 publishes the defender hallmarks, including canary values, 1-14 request bursts with 25-31 second pauses, and the October host counts of 609 ARTEX and 1,323 CyberStrikeAI.
Source 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
MITRE ATLAS
AI-specific catalog annotations based on the reported behavior; these are not MITRE case-study assignments.
ARTEX planner agent autonomously conducted API reconnaissance and exploitation Source
Sources & research credit
2 sourcesResearch by Ben Magee, Will Cates · Unit 42 (Palo Alto Networks)
- Activity using ARTEX agentic AI github.com
- ARTEX and AI-Powered Red Teaming Tools: What Defenders Need to Know unit42.paloaltonetworks.com
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.
Record & downloads
- Source record name
- ARTEX planner agent API reconnaissance and exploitation
- Entry ID
- unit42-artex-api-recon-2026-10
- Catalog review
- November 4, 2026
- AI-role confidence
- high
- Category
- adversary-use-of-ai
- AI involvement confidence
- confirmed