Observed incident

Cloudflare traces ARTEX activity in a customer account to a compromised deployment token

Reported

Published here

What happened

Cloudflare responders observed ARTEX using a compromised customer API token that had been used for software deployments. The token had broad permissions and no IP restrictions or rate limit. Cloudflare assessed that the compromise most likely started at another cloud provider.

Parties and reporting

Where this happened

Victim location not disclosed. Real organizations or systems were affected or targeted, but the sources do not say where. Explore the world map.

AI tools and systems: ARTEX, Cloudflare Workers, Customer CI/CD API token

Outcome

Responders observed newly created Workers, 400 database export requests in one hour, and attempts to retain access and validate tokens for other services. Cloudflare did not say how many exports succeeded or how much data was taken.

Operating lesson

Replace long-lived deployment credentials with short-lived, narrowly scoped ones. Alert on unexpected Worker creation and unusual volumes of database exports.

Evidence and limits

The incident affected a customer account. Cloudflare did not identify the customer, its location, the other provider or a confirmed loss amount. Its investigators assessed that a person likely provided light guidance; the report does not establish a breach of Cloudflare infrastructure.

Sources