Leaky AI supply chain is exposing secret user data at an alarming rate
Researcher HD Moore planted about two million unique canary secrets in prompts sent through AI routers and inference resellers to test whether sensitive data leaks.
Source-based brief · Editor review not recorded · See checks and limits ↓
One primary source; other links are context, not independent corroboration.
- Primary sourcearstechnica.com
- Discovery linkHacker News
- Linked in sourceOpenRouter
- Linked in sourceVercel
- Linked in sourcewrote Thursday
A community post points to the original link. Discussion and upvotes do not establish accuracy.
Open full article view →- Community discussion+5
- Fetched source page+30
- No editor link review+0
- Community link+0
This measures the stored source trail and editorial steps. It does not certify accuracy, peer review, or independent corroboration. Popularity adds no points.
View full scoring →Read the scoring rubric →What the source says
Researcher HD Moore planted about two million unique canary secrets in prompts sent through AI routers and inference resellers to test whether sensitive data leaks. He reports that at least three hosting providers were compromised, stolen AWS keys were used tens of thousands of times, resellers logged prompts, and some providers ignored zero-data-retention flags. One Chinese lab's systems allegedly fetched secret URLs from many prompts, including ZDR-flagged ones.
Claim explorer
Attribution, source and conditionsSource-stated points from the stored brief. Claim-level assessments have not been recorded.
Source claims not independently checked; the full article was reviewed but the findings come from one researcher's experiment and reporting.
This connects a source, an attributed statement and its qualifications. It does not establish that the claim is correct.
Questions worth asking
Open questions for further reportingWhat remains unconfirmed?
Source claims not independently checked; the full article was reviewed but the findings come from one researcher's experiment and reporting.
What material was available for this brief?
The recorded brief basis is fetched source page. These points are AINewsIQ paraphrases, not quotations or independent confirmations.
Canary secrets seeded in single prompts were stolen from at least three compromised hosting providers.
Source: arstechnica.com ↗Stored source-based brief · key point 1 · AINewsIQ paraphraseStolen AWS keys were used tens of thousands of times in AWS API calls.
Source: arstechnica.com ↗Stored source-based brief · key point 2 · AINewsIQ paraphraseSome resellers logged prompts and passed them to people who reused the credentials.
Source: arstechnica.com ↗Stored source-based brief · key point 3 · AINewsIQ paraphraseA Chinese AI lab's systems reportedly fetched secret URLs from over half of prompts sent to it, including many marked zero data retention.
Source: arstechnica.com ↗Stored source-based brief · key point 4 · AINewsIQ paraphraseLimits from the stored brief
Source claims not independently checked; the full article was reviewed but the findings come from one researcher's experiment and reporting.
This is a source-based abstract, not independent validation of the source's claims.
Evidence & sources
These links show where the signal came from and what the source page linked to. A linked page is context, not independent corroboration.
A community post points to the original link. Discussion and upvotes do not establish accuracy.
Timeline & updates
- Signal dated by source or discovery feed
This timestamp places the signal in the radar. It may be the discovery post date rather than the primary page's first publication date.
- Shared brief stored
AINewsIQ prepared one abstract from fetched source page.
Brief history · 1 retained version
These are changes to AINewsIQ’s own publication. Earlier history is unavailable unless recorded here. Complete retained versions are available to the editor.
- Version 1 · published
Source-based brief stored or updated. This does not establish that the publisher changed its page.
Automated record
Source observations · 1 recent captures
A changed capture means the extracted text differed. It can reflect page furniture or extraction changes; it does not establish a substantive correction. Source captures remain private.
Retained capture; no earlier comparison available.
New engagement snapshots do not mean the source itself changed. Source observations and AINewsIQ brief revisions are separate records.
Why this may matter
Developers using AI routers may unknowingly expose API keys and sensitive prompt content to resellers and hosts. Privacy flags such as zero data retention may not prevent leakage, affecting anyone relying on them.
Limits and open questions
Source claims not independently checked; the full article was reviewed but the findings come from one researcher's experiment and reporting.
Organization-specific financial, security, and operational effects require the organization's own context and review.

Join the discussion
Have a different perspective or a question about the evidence? Discussion is free with a verified email account. Every comment is reviewed before publication.
No published comments yet.
New commenters: 2 submissions per 24 hours, at least 5 minutes apart, until 3 are approved. Discussion guidelines and moderation →