Skip to content
PERMISSION/PROTOCOL
Back to incident tracker

2026-11-13

HighPrimary

Cloudflare Reports ARTEX Creating Workers and Issuing Database Dump Requests With a Compromised Token

Cloudflare reports ARTEX creating Workers and issuing database dump requests using a compromised API token; successful data retrieval remains unconfirmed.

ARTEXCredential exposureResponder-reported attacker-operated agent activity using compromised credentialsAn unnamed customer's Cloudflare environment and account-level CI/CD API token

What happened

Cloudflare reports new Worker creation, 400 database dump requests in an hour, attempted persistence and attempts to validate session tokens for third-party applications.

Why it matters

Worker scripts were created in the affected environment. Requests and attempts are observed; successful database extraction and persistence are not confirmed in the public report.

Missing authorization check

Victim-controlled scope and authorization for token use, Worker creation and database-export operations, beyond possession of an account-level credential.

Would PP block it?

Integrated legitimate workflows could bind token use and exact export or Worker operations to delegated scope. No PP integration or prevention result was established for this incident.

Incident analysis

Timeline and technical read

Timeline

  1. 2026-11-13

    Cloudflare publishes an incident-response account of ARTEX using a compromised account-level token.

Technical breakdown

  • The account-level token had previously been used for CI/CD and lacked IP restrictions or rate limiting.
  • Worker names included artex-*, artex-pgrecon-*, artex-pgw-* and artex-do-* and correlated with distinct behaviors.
  • Responders observed more than 69 requests per minute and 400 database dump requests within an hour.
  • The source describes attempted persistence and third-party session validation, not verified success of either operation.

Authorization boundary

Where the authorization boundary should have been

This incident is categorized as Credential exposure. The relevant Permission Protocol gate is Credential Gate. The read is conditional: the block only applies where the real action boundary is routed through a gate.

If enforced at
Only independently integrated victim-controlled credential or resource execution boundaries
Still needs
PP is not perimeter defense, does not prevent initial token theft, and cannot mediate API paths that bypass its boundary. Credential restrictions, revocation and containment remain separate controls.
Receipt required for
Scoped token use, Worker creation and database export where an independently enforced authority boundary is integrated

An internal authority gate cannot constrain an external attacker-controlled ARTEX harness that does not route its operations through that gate.

Start small

Put the relevant gate at this action boundary.

This incident maps to Credential Gate. Start with the boundary that controls the actual action, then require a signed receipt before execution.

Replay this incident with a signer in the loop