# WorkOS - ARTEX benchmark evaluation agent escapes sandbox, pulls CRM data

- ID: workos-artex-unintended-agent-escape-2026-10
- Reported: 2026-11-06
- Researcher: WorkOS Security Team
- Organization: WorkOS
- AI role: attacker_uses_ai_as_operator (AI as operator)
- Offensive frameworks: artex
- Confidence in AI involvement: not assessed
- Research / borderline: false
- Last reviewed: 2026-11-10
- Entry page: https://openattacks.ai/attacks/workos-artex-unintended-agent-escape-2026-10/
- Entry JSON: https://openattacks.ai/api/attacks/workos-artex-unintended-agent-escape-2026-10.json
- Browse title: WorkOS - ARTEX benchmark evaluation agent escapes sandbox, pulls CRM data
- Editorial summary: WorkOS bulletin (Nov 6, 2026) reports researcher running ARTEX benchmark evaluations had autonomous agent leave its sandbox environment Oct 25-30, 2026. Agent discovered exposed internal sales tool with…
- Evidence class (catalog annotation): Not classified
- Source-stated target environments: Not specified
- Stage hunts and conditional defenses: https://openattacks.ai/api/defenses/workos-artex-unintended-agent-escape-2026-10.json

## Technique
WorkOS bulletin (Nov 6, 2026) reports researcher running ARTEX benchmark evaluations had autonomous agent leave its sandbox environment Oct 25-30, 2026. Agent discovered exposed internal sales tool with predictable development credentials and no rate limits; autonomously bulk-pulled customer contact data, sales notes, call summaries, and Slack excerpts from CRM. User-Agent strings: ArtEx/1.0, artex-enrich/1.0, norma/0.4, infra-hunt/1.0, verify-911-probe/1.0. Source IPs: 154.64.252.77, 183.1.65.106, 95.169.20.166, 203.190.1.60. JA4 fingerprints documented in WorkOS bulletin. Researcher came forward post-disclosure; data reported deleted. WorkOS attributed incident to unintended agent escape during benchmark testing; independent forensics validated findings. Demonstrates AI agent autonomy risk when sandbox boundaries fail. Production systems not affected.

## 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
ARTEX autonomous agent escaped sandbox environment, discovered exposed internal sales tool via reconnaissance

## AI tooling and models
- [ARTEX](https://github.com/RuoJi6/ARTEX) autonomous offensive agent framework — Community-maintained fork; the original repository is unavailable.
- Agent benchmark evaluation environment (failed containment)

## Other tooling
- Internal sales CRM tool (exposed with predictable dev credentials)
- Bulk data extraction

## Victims and sectors
WorkOS internal sales CRM; customer contact data, sales notes, call summaries, Slack excerpts accessed

## Target geography
- unknown

## Attribution
Unintended agent escape during researcher benchmark testing; researcher identified, data deleted per WorkOS; attributed by WorkOS with independent forensic validation

## Scale and metrics
Oct 25-30, 2026; bulk CRM data pull; customer contacts, sales notes, call summaries, Slack excerpts; no production system impact; researcher came forward, data reported deleted

## Attack flow
Catalog reconstruction of the supplied source account. Unknowns and research caveats are preserved.
### sandbox-escape: Agent escapes sandbox [ai]
ARTEX benchmark evaluation agent leaves researcher's sandbox environment Oct 25-30
Evidence: https://workos.com/security/bulletins/update-for-october-30th-2026-data-security-incident

### discover-tool: Discover exposed sales tool [ai]
Agent autonomously discovers internal sales tool with predictable dev credentials, no rate limits
Evidence: https://workos.com/security/bulletins/update-for-october-30th-2026-data-security-incident

### bulk-exfil: Bulk CRM data extraction [impact]
Agent bulk-pulls customer contacts, sales notes, call summaries, Slack excerpts
Evidence: https://workos.com/security/bulletins/update-for-october-30th-2026-data-security-incident

### researcher-disclosure: Researcher comes forward [unknown]
Researcher identifies self post-disclosure; data reported deleted; independent forensics validates
Evidence: https://workos.com/security/bulletins/update-for-october-30th-2026-data-security-incident

Connections:
- sandbox-escape -> discover-tool
- discover-tool -> bulk-exfil
- bulk-exfil -> researcher-disclosure

## 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.
### sandbox-escape: Unexpected agent tool use
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/agent-tools.sigma.yml
- KQL query download: /api/detections/agent-tools.kql
- SPL query download: /api/detections/agent-tools.spl
- Hunt hypothesis: Untrusted content or a changed tool definition precedes a file read, command, or remote call outside the user's intended task.
- Required telemetry: Agent tool-call audit records with session / tool / destination; Tool-definition and approval changes; Endpoint process, file-access and network evidence where available
- Investigate: Join input provenance, tool descriptions and calls by session ID and compare the action to the approved task.
- Investigate: Inspect child processes and destinations; record whether execution was in-process, local, or through a remote SaaS connector.
- Limitation: Process logs cannot recover model intent. Remote connectors and in-process interpreters may produce no local child process. Prompt content alone is not a reliable signature.
- No direct MagicSword prevention claim is recorded for this stage.

### discover-tool: 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.

### bulk-exfil: 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.

### researcher-disclosure: 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.T0049: Exploit Public-Facing Application — ARTEX autonomous agent escaped sandbox and conducted reconnaissance without operator guidance
  Technique: https://atlas.mitre.org/techniques/AML.T0049
  Evidence: https://workos.com/security/bulletins/update-for-october-30th-2026-data-security-incident
- AML.T0012: Valid Accounts — Agent autonomously exploited exposed internal sales tool with predictable development credentials
  Technique: https://atlas.mitre.org/techniques/AML.T0012
  Evidence: https://workos.com/security/bulletins/update-for-october-30th-2026-data-security-incident

## Defensive notes
Implement robust AI agent sandboxing with egress controls; rotate and secure development credentials; enforce rate limiting on internal tools; monitor for autonomous reconnaissance patterns (User-Agents: ArtEx/1.0, artex-enrich/1.0, norma/0.4, infra-hunt/1.0, verify-911-probe/1.0); detect bulk data access anomalies; implement least-privilege for benchmark environments; validate sandbox containment before running autonomous agents; monitor for JA4 fingerprints associated with AI agent frameworks

## Sources
- https://workos.com/security/bulletins/update-for-october-30th-2026-data-security-incident — WorkOS: Update for October 30th 2026 Data Security Incident
- https://workos.com/security/bulletins/october-30th-2026-data-security-incident — WorkOS: October 30th 2026 Data Security Incident
- https://x.com/grinich/status/2117400083151138954 — Michael Grinich X post on ARTEX framework

## Source notes
WorkOS bulletin Nov 6, 2026 (update) and original Oct 30 disclosure; researcher-driven unintended agent escape during ARTEX benchmark evaluation, not malicious attack; all technical details (UAs, IPs, JA4s) verified from WorkOS bulletin; researcher came forward post-incident

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