Skip to content
Prompt Theft at Three AI Inference Providers Exposes OpenRouter Customer Requests

Prompt Theft at Three AI Inference Providers Exposes OpenRouter Customer Requests

First seen 22 Nov 2026, 12:13 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 22, 2026 at 12:14 UTC
  • •Three AI inference providers behind OpenRouter were compromised or failed to uphold data policies, with some prompts flagged Zero Data Retention still stolen.
  • •OpenRouter removed the three providers and 125 endpoints from ZDR eligibility and states its own systems were not breached.
  • •Planted AWS keys sent in late October were reportedly all captured and used for tens of thousands of AWS API calls.
  • •Affected customers were notified; defenders should treat any AWS keys or secrets sent through affected providers as exposed.
  • •Researchers flagged artex-agent and artex-judge-r121 user agents as absent from public indicator lists.

Dragos reported that attackers stole data from inside three AI inference providers routing through OpenRouter, and the providers did not know until researchers told them, according to Thehackernews. The findings came from canary-token research that seeded two million prompts with unique links and credentials between July and November; the earliest breach reportedly began in mid-July. The largest breach involved a couple hundred planted AWS keys sent to one provider during late-October windows, and every request in those windows was reportedly stolen, some of them rejected before any model ran. The attacker reportedly tested keys, listed S3 buckets, searched Secrets Manager and Parameter Store, and tried to create Bedrock API keys and IAM users, driving tens of thousands of AWS API calls. On November 1 the same attacker reportedly used the ARTEX AI-driven penetration testing framework to confirm keys were still live, and two user agents (artex-agent, artex-judge-r121) were reported as absent from public indicator lists. A separate finding described sellers on an AI inference marketplace enabling request logging at low prices and collecting customer traffic, with one key reportedly passing through a router that forwarded some traffic to the marketplace. OpenRouter stated it found no breach of its own systems, removed three providers, removed 125 endpoints from Zero Data Retention eligibility, and notified potentially affected customers. OpenRouter said it is adapting the researchers' testing, verifying network paths for forwarding to third parties, and requiring assurances before restoring ZDR eligibility. No CVEs are involved.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-07-01
Earliest breach at a provider reportedly begins
Researchers say the earliest of the three provider breaches began in mid-July; the exact date is not given.
Thehackernews
2026-11-01
Attacker reportedly uses ARTEX to verify stolen keys
The same attacker reportedly brought in the ARTEX AI pentesting framework to confirm that held keys were still live.
Thehackernews
2026-11-22
OpenRouter removes three providers and 125 endpoints from ZDR
OpenRouter said it off-boarded three providers, removed 125 endpoints from ZDR eligibility, and notified affected customers.
Thehackernews

More articles in this cluster (5)

Following this threat?

Track Dragos in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

Am I affected if I routed requests through OpenRouter?
OpenRouter says it notified all potentially affected customers, and affected endpoints were removed from ZDR eligibility. Check your notifications and treat any secrets sent through the three removed providers as exposed.
Does this mean OpenRouter itself was breached?
No. OpenRouter says the findings showed no breach of OpenRouter itself; the compromises were at the third-party inference providers.
What should defenders do first?
Rotate any AWS keys or secrets that were sent in prompts to affected providers, and review CloudTrail for S3, Secrets Manager, Parameter Store, Bedrock, and IAM activity. Add the reported artex-agent and artex-judge-r121 user agents to detections.