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.
2026-11-13
HighPrimaryCloudflare reports ARTEX creating Workers and issuing database dump requests using a compromised API token; successful data retrieval remains unconfirmed.
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
2026-11-13
Cloudflare publishes an incident-response account of ARTEX using a compromised account-level token.
Authorization boundary
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.
An internal authority gate cannot constrain an external attacker-controlled ARTEX harness that does not route its operations through that gate.
Start small
This incident maps to Credential Gate. Start with the boundary that controls the actual action, then require a signed receipt before execution.