Confirmed 19 Nov 2026 · Security A one-minute read

Dragos seeded 2 million AI prompts with traps. Attackers were inside 3 providers.

Over 5 months Dragos sent nearly 2 million prompts carrying unique credentials and URLs, then watched who used them. Two of the breached providers were serving requests marked zero data retention.

Until now

A privacy flag on a prompt kept it out of other hands.

Now

The flag binds the first hop. Attackers and resellers sit past it.

Why it matters

The method is cheap enough to copy, and it measures the AI supply chain from the inside rather than from a vendor's word. Anyone sending prompts through a router or a marketplace now has a way to find out where they actually go, and a reason to assume nobody has checked.

Established

  • Attackers stole data from 3 AI hosting providers, the earliest from mid-July.
  • Two breaches included requests marked zero data retention.
  • Stolen keys were used for tens of thousands of AWS calls.

Not established

  • Which providers. Dragos names none of the compromised hosts.
  • Who the attackers are. One used a tool called ARTEX.
  • That a customer lost money. Only Dragos's own planted keys were used.
The five-minute readThe record, the timeline, the weight and 3 sources

The record

Dragos published AI Supply Chain Security, What Canary Tokens Found, by chief research officer HD Moore, on November 19, 2026. The page header gives 08:00; the metadata gives 13:00 with no time zone. Its core claim: Dragos sent nearly 2 million AI prompts containing unique, trackable secrets to AI providers, over 5 months from July to November 2026. Each prompt carried unique URLs and canary credentials, including AWS keys and DNS names. The work began with Thinkst Canarytokens in July, then Dragos built a seeding service that derives unique hostnames, URLs and credentials per prompt and hosts the services they point at, covering DNS, web, git, SSH, databases and mail. AWS keys were tied to empty, fully logged accounts. Routes were traced with image URL callbacks and malformed requests that expose nested error envelopes from each hop; about 2,000 routes were traced and several hundred included systems Dragos could not identify. Findings. Attackers actively stole data from 3 hosting providers, the earliest incident dating to mid-July. The largest breach involved a couple hundred AWS keys, each sent in a single request to one provider during late-October windows; every request in those windows was stolen, and some were taken before a model ran, which points at copying at the provider's front door. Two of the breaches included requests marked zero data retention. Dragos writes that a privacy flag does not help when the attacker is already inside. Stolen keys were used for tens of thousands of AWS API calls, and one adversary hit 2 providers at once from a single rented server. On November 1 the same attacker used ARTEX, a model-driven penetration testing framework, sending the user agents artex-agent and artex-judge-r121. Providers were unaware until notified; one has still not disclosed publicly, another published a preliminary notice. Resellers obtained prompts with no exploit at all, through ordinary request logging: Dragos writes that sellers only had to list a model at the lowest price, enable request logging, and wait. Secret URLs were opened about a day and a half after a request, followed by login guessing, including an SSH root attempt using passwords taken from prompts. A Chinese AI lab fetched secret URLs from more than half of prompts sent between July and October, including roughly two-thirds of requests marked no data collection or zero data retention, with scrapers typically appearing 2 to 3 days later.

How it got here

  1. Jul

    Dragos starts with Thinkst Canarytokens, then builds its own seeding service. The earliest provider compromise it later dates also begins in mid-July.

  2. Jul TO Oct

    A Chinese AI laboratory fetches secret URLs from more than half of prompts sent in the period, including about two-thirds of those marked no data collection or zero data retention.

  3. Late Oct

    The largest breach: a couple hundred planted AWS keys taken from one provider, every request inside the windows stolen, some before a model ran.

  4. Nov 1

    The same attacker runs ARTEX, a model-driven penetration testing framework, against the planted AWS accounts, identifying itself as artex-agent and artex-judge-r121.

  5. Nov 19

    Dragos publishes the method, the findings and its recommendations. It began notifying providers in early November and names none of the 3 compromised hosts.

Who has to react

The 3 unnamed providers and the dozen Dragos is working with; OpenRouter and other routers, one of which appears as an undisclosed hop; every enterprise that bought zero data retention as a control; cloud security teams whose keys travelled in prompts; and regulators who have been told prompts are not retained.

What to watch

  • Would strengthen itA named inference reseller or router is shown to have logged or resold customer prompts, or a provider discloses a breach matching the late-October windows, by March 31, 2027.
  • Would strengthen itAny provider, vendor or government attributes the late-October theft or the ARTEX activity to a named actor, by June 30, 2027.
  • Would weaken itTwo or more of the 3 providers publish post-mortems showing the theft came from an ordinary credential compromise unrelated to resale or routing, by June 30, 2027.

Why it weighs this much

Signal strength
CostHigh
CommitmentHigh
ReversibilityHard
PersistenceStructural

Cost is high. Five months, nearly 2 million prompts, a purpose-built seeding service hosting 6 kinds of fake service, 2,000 traced routes and real AWS accounts left open to be abused is a research programme. Commitment is high: a named chief research officer puts his firm behind findings that accuse unnamed providers of being breached, which invites contradiction from anyone who can produce logs. Reversibility is hard, because the evidence is the callbacks, which happened and are logged. Persistence is structural: the finding is not a bug that gets patched but a property of a supply chain where a prompt passes through hops the sender never chose, and the counting method now exists for anyone to run.

The words

Canary token
A fake secret planted so its use gives away a leak. Nobody legitimate would ever touch it, so any use is evidence.
Zero data retention
A provider setting that promises a request is not stored. It binds the provider you call, not whoever sits behind it.
Inference reseller
A marketplace or router that sells access to someone else's model, passing your prompt along one or more hops.

Sources

Your call

Which explanation do you believe?

A call is final. Other people's calls show after yours.

8 contributions. Thank you.

You have built
a record here.

Keep it: create an account to verify your contributions and put your name to the answers you choose. Your record stays yours.

Keep my record ↗
Optional: help show whose perspectives are missing
Kept with your answers under a random id, never with your name. Used for one thing: showing you, on your record, where you stand next to people like you, once at least 20 of them have answered.

Add your signature

Stand behind your judgment.

Create an account to attach your name to this answer. Your other answers show no name unless you sign them too.

Sign up to add your name ↗

Already have an account?