Dragos Seeded 2 Million Bait AI Prompts: Three Providers Breached Unaware, Resellers Logged Prompts, 'Zero Data Retention' Leaked — OpenRouter Pulls ZDR Label From MiniMax Endpoints

AI · 2026-11-21 · By H.A

Dragos Seeded 2 Million Bait AI Prompts: Three Providers Breached Unaware, Resellers Logged Prompts, 'Zero Data Retention' Leaked — OpenRouter Pulls ZDR Label From MiniMax Endpoints

A five-month canary experiment found three AI hosting providers breached without their knowledge, marketplace resellers keeping customer prompts, and ZDR-flagged requests read by third parties, prompting OpenRouter to strip the ZDR label from MiniMax-model endpoints.

What Happened

Dragos chief research officer HD Moore has published the results of a five-month experiment that sent about two million bait prompts to widely used AI services. The findings: at least three AI hosting providers were breached without knowing it, some marketplace resellers kept customer prompts, and requests marked "Zero Data Retention" (ZDR) still ended up in other people's hands.

Between July and November 2026, the team put unique canary secrets into the prompts. These were AWS access keys tied to empty, fully logged accounts, plus one-off URLs, DNS names, and git, SSH, database and mail credentials that existed nowhere else. Dragos ran the infrastructure behind each canary and logged every connection. If a secret was used, the prompt carrying it had been read by someone other than the model.

The report came out on 19 November. Two days later OpenRouter customers began publicly posting an email from the AI routing platform, titled "Requests you sent to MiniMax models may have been read". It appears to describe the same kind of canary testing. OpenRouter has not published a public page about it.

Three Providers Breached, Keys Used Within Hours

Dragos says data from "at least three AI providers" was exposed. The earliest incident dates to mid-July, and none of the three providers knew until Dragos told them. Dragos has not named them. It says one has not disclosed its breach publicly and another posted a preliminary notice in late October.

The largest breach covered "a couple hundred" bait AWS keys, each sent in a single request during late October. The researchers say those keys were then used for tens of thousands of AWS API calls. In one example, a key planted on 21 October was first used the next day and was still being used three weeks later. Some stolen keys came from requests the provider had rejected before any model ran. That means the attackers were reading raw request traffic, not model output.

Once inside the empty accounts, the attackers followed a familiar cloud playbook:

Their tooling also changed over time. They started with a script running from Chrome on Windows, moved to Boto3 inside OrbStack, then to the AWS CLI on Kali Linux. From 1 November they brought in ARTEX, an LLM-driven pentest framework, which showed up with the user agents artex-agent and artex-judge-r121. ARTEX is the same tool CERT-EU linked to this month's attack on European Commission staff systems.

Resellers Read Prompts Without Hacking Anything

The second finding needed no breach at all. Dragos says several resellers on an AI inference marketplace "were able to view and retain customer prompts using standard logging". To isolate them, the team sent identical prompts through different sellers. The secrets came back only from certain sellers, so the leak followed the seller, not the marketplace. In one case, secret URLs were opened about a day and a half after the prompt. The report also describes root SSH login attempts using a password that existed only inside a prompt.

"Zero Data Retention" Only Binds the First Hop

The most uncomfortable finding for enterprise buyers is about privacy flags. Dragos says prompts sent to US-based providers were passed on to Chinese AI organisations. One Chinese AI lab fetched secret URLs from more than half the prompts sent to its models between July and October, including about two-thirds of requests marked "no data collection" or ZDR.

In one case, Dragos says, a secret link from a ZDR request turned up 24 days later in a Feishu workplace chat. Within two minutes it was opened from three desktops and three phones in Beijing and Shanghai. The report's point is simple: a privacy flag only binds the first hop. If a provider forwards your request to the model's original developer, your setting may not go with it.

OpenRouter's email fills in names that Dragos left out. According to copies customers posted, a researcher placed unique URLs in prompts sent to MiniMax models from July to October 2026. A third party opened them "40 to 130 hours after the requests were sent", whether MiniMax served the request itself or another provider forwarded it. OpenRouter says AtlasCloud, Novita and StreamLake told it they forwarded OpenRouter requests for MiniMax models to MiniMax. It says the issue "sits with MiniMax and the providers that forwarded to it, not with OpenRouter".

MiniMax reportedly told StreamLake that content moderation was switched on for its endpoints before 22 October and that it has since enabled ZDR. OpenRouter says it has asked MiniMax for its own account and has not received one. In the meantime it has removed the ZDR label from these MiniMax-model endpoints. The email also says tests on other models at the same providers were not accessed, with one exception, and that none of the AWS test keys from those requests were used.

OpenRouter's own data processing agreement already warns about this. It says inclusion on its ZDR list reflects a provider's represented policy and is not a guarantee that the provider complies.

Who Is Affected

Any organisation whose staff or applications send sensitive data to AI models through aggregators, routers or reseller marketplaces should assume some of those prompts may have been stored or read. This matters most for coding agents that paste environment files, logs or config into prompts, since these often contain live keys. Dragos says it is working with about a dozen providers. It warns that stolen keys and secret URLs "continue to be accessed, even months after the initial incident."

What To Do Now

Dragos's guidance, plus standard incident steps:

For example, to search CloudTrail for the ARTEX user agents:

aws cloudtrail lookup-events --max-results 50 \
  --query "Events[?contains(CloudTrailEvent, 'artex-')].[EventTime,EventName,Username]" \
  --output table

Why It Matters

Companies have spent two years writing AI acceptable-use policies around one question: does the vendor train on our data? This research shows that is the wrong question. A prompt can pass through a router, a reseller, a hosting provider and the model's original developer, each with its own logging, moderation and security posture. Any of them can be breached. Without canaries, none of this was visible to the customers, and much of it was not visible to the providers either.

Sources

COMPUTE NODE · · --:--:--

Fresh cybersecurity news,
daily threat intelligence.

Daily cyber news, live threat intel and exploited CVEs.

Everything in one place

Self-hosted, hardened, and yours.

RUN IT

Local AI console

Chat with a model on your own hardware via Ollama or any OpenAI-compatible server. No cloud, no key.

DEFEND

Cyber threat feed

Automatic daily intel from CISA KEV, NVD & GitHub advisories, a live cyber threat map, and your own notes.

NEWS

News & videos

Articles and updates on pentesting, AI, and cyber — with embedded video, including YouTube. Post your own.

DIRECTORY

Registry

Runtimes, models, MCP servers, agents, and a full security & pentest tooling section.

PUBLISH

Posts

Write, edit, publish, and share articles backed by a real database and your account.

COMMUNITY

Forum

Threads and replies across categories from Models to Hardware to Security.

CODE

Repos

Curated AI and security GitHub repos, plus a shelf for pinning your own.

DOWNLOAD

Skill packs

Agent starters, RAG scaffolds, and defensive security & VAPT report templates.

Registry

Runtimes, models, MCP servers, agent frameworks, and a security & pentest tooling section — all links out to the real projects.

Local AI console

Talk to a model running on your own machine through Ollama or an OpenAI-compatible server — your prompts and the model's replies always go straight from your browser to your local model, never through a Reef server. Attach files for context, and pick up saved chats where you left off.

Type /image a prompt in the box below to generate
Not connected

Local AI hardware benchmark

A spec-based compatibility advisor — tells you which local models your hardware can run well, which will be slow, and which to skip. Connect to Ollama below for a real, measured speed test instead of an estimate.

1. Your hardware

2. Live check against your local model server (optional)

If a local model server is running, this cross-references the table above with what you've actually got loaded — and runs a real, measured speed test instead of an estimate.

AI Database

A browsable catalog of AI models across providers — context windows, pricing, and capabilities.

Loading…

Cyber threat feed

Latest threats pulled automatically every day from CISA's Known-Exploited-Vulnerabilities catalog and NVD — plus threat intel you post yourself.

⇩ Export STIX
Loading threat feed…

Cyber threat map

Attacks happening right now, all over the world.

Connecting…
LIVE · MAURITIUS TIME--:--:--
attack route, country to country attack route into Mauritius attacker reported worldwide
Loading live data…
attackers reported per minute · click to rewindnow

Top attack routesweb

Attackers based inlast hour

Networkslast hour

Click any dot, feed row or table row to see that IP's profile.

Mauritius

Who attacks Mauritius

Loading…

Web attacks malicious requests to Mauritian websites that were blocked
Network DDoS floods meant to knock Mauritian servers offline

    Mauritius · last 24 h

    How Mauritius is attacked

    Network-level attacks (DDoS) aimed at Mauritius, by method. They try to knock servers and networks offline by sheer volume.

    • Loading…

    The ports or services these floods aimed at aren't published.

    Mauritius · last hour

    Attackers located in Mauritius

    0attackers located in Mauritius were reported in the last hour

    This counts attacks coming from Mauritius, not attacks on it: IPs in Mauritius that servers elsewhere reported for attacking them. Usually zero or one; when it rises, it's often a hacked local server or router.

    Worldwide today

    What attackers are knocking on

    Ports most targeted across a worldwide network of sensors .

    Worldwide today

    Most active attackers

    Ranked by how many separate sensors they hit. Click a row for its profile.

    IPCountryNetworkSensors hitReports
    What you're looking at
    Blue routes

    Share of attack traffic from one country to another. Thicker, faster streams carry more. Particles show volume, not one per attack.

    Every 15 min · published 1–2 h behind
    Amber flashes

    An attacking IP that servers around the world reported in the last minute, placed where the IP is. Its targets aren't published, so there's no line.

    Every minute · shown about 1 min behind
    Locations

    IP locations are approximate (city level at best) and show where the machine is hosted, not who controls it.

    Approximate · city level at best

    News

    Articles, guides and updates on pentesting, AI, and cybersecurity — with embedded video. Add your own, including YouTube.

    Loading…

    Posts

    Loading…

    Loading posts…

    Forum

    Questions, answers, and talk about running AI locally.

    Loading forum…

    GitHub repositories

    Curated AI and security repos, plus your own pinned shelf.

    Command board

    One-liners, configs, and advice worth keeping — shared by everyone here.

    ⚠ Commands are shared with all users. Never include credentials, tokens, or internal hostnames. Review anything before you run it.
    Loading commands…

    Skill packs

    Starter files served from the API — AI agent scaffolds plus defensive security & VAPT reporting templates. Click to download.

    Loading skills…

    Your watchlist

    Follow threat actors, malware, CVEs and vendors — we tell you when a new report, CVE record or exploitation alert mentions them.

    Threat Library

    Threat actors, malware and tools — their attack techniques, Reef Sentinel coverage and indicators of compromise.

    Loading…

    Threat Intelligence

    Curated threat write-ups, advisories and analysis — with cover media.

    Loading…

    Tutorials

    Step-by-step guides for running local AI, using the console, and tracking threats. Admins can add their own.

    Loading…

    Downloads

    Direct links to the official homepage/download page for well-known cybersecurity, penetration-testing, and local-AI software. Always verify checksums/signatures from the vendor before running anything.

    Loading…

    Privacy Policy

    Loading…

    Terms & Conditions

    Loading…

    Help & FAQ

    Answers to common questions about Reef Sentinel, plus a formatting guide for posts, articles, and comments.


    Formatting guide

    Commands you can type into the body of a post, comment, or reply — no HTML needed. Comments and short replies only support bold, italic, and inline code.

    Contact us

    Questions, feedback, or a security disclosure? Reach us directly, or send a message and we'll get back to you by email.

    Loading…

    Send a message

    VAPT Report Generator

    Build an engagement, add findings with a live CVSS calculator, and generate a branded, print-ready report.

    Recon Toolkit

    Investigate any domain, IP, URL, file hash, email or CVE in one search, plus breach and password checks, hash identification and a payload cheatsheet.

    Outage Monitor

    Is Microsoft 365, Facebook, Google, AWS or ChatGPT down? Live status of the big tech services from their official status pages, every incident with its full timeline, and how long each one took to fix.

    Website Checker

    Reads a website's HTTP response headers to identify its framework and server, shows any known CVEs for the exposed versions with details, and recommends what to do.

    Control panel

    Manage everything shown on the site — news & videos, posts, homepage headlines, and subscribers. Admin only.

    Overview
    Content
    Site
    Account & Security

    Email settings

    SMTP on ports 25/465/587 is blocked outbound by some hosts (e.g. DigitalOcean droplets by default) — Resend and Brevo send over their HTTPS API instead, so they work even then. Only the selected provider is used to send; the others stay saved but idle, so you can switch back any time without losing settings.

    Get a key from resend.com/api-keys. Uses the "From address" below as the sender — it must be on a domain you've verified with Resend.

    Get an API key (not an SMTP key) from app.brevo.com/settings/keys/api. Uses the "From address" below as the sender — it must be a verified sender in your Brevo account.

    "From address" and "Site name/URL" are shared by SMTP, Resend, and Brevo — they control what recipients see, regardless of which provider is active.

    Send a test email

    Sends through whichever provider is currently active above. Save your settings first if you just changed them.

    SIGNAL LOST

    We couldn't find this page

    The page may have been moved or deleted, or the address was mistyped.