AI incident ·
Publicly Shared Claude Artifacts Reportedly Became Discoverable Through Google Search
On this page 7 sections
In brief
An AI system built by Large Language Model Developers, Chatbot Developers and 1 other and deployed by Anthropic allegedly harmed Privacy, Claude Users and 2 others.
- Risk domain
- Not classified
- Occurred
- Coverage
- 2 reports
What happened
Users reported that publicly shared Claude Artifacts (apps, documents, spreadsheets, and other files) could be found through Google Search. Reportedly, indexed artifacts containing business plans, infrastructure diagrams, clinical-trial planning materials, and other potentially sensitive content were also located. Anthropic said links became searchable only after being posted somewhere crawlable.
Laws on record for this risk area
No instrument on record yet covers this risk area where it happened. See the open queue.
Matched from the record's risk category and country to the instruments in effect recorded here: a law listed covers the area, which is not a finding that it applies to this incident. A reviewer can correct the match in the repository (data/external/incident_overrides.yaml).
News reports (2)
Titles link to the original publisher; report text is not reproduced here.
Who was involved
- Alleged deployer
- Anthropic
- Alleged developer
- Large Language Model Developers, Chatbot Developers, Anthropic
- Alleged harmed party
- Privacy, Claude Users, Chatbot Users, Anthropic Users
Classification (MIT AI Risk Repository taxonomy)
- Risk domain
- —
- Risk subdomain
- —
- Causal entity
- —
- Intent
- —
- Timing
- —
- Harm level
- —
- Sectors
- —
- Countries
- —
Other incidents involving Anthropic
- Early Claude Opus 4.6 Checkpoint Reportedly Gained Unauthorized Admin Access to Third-Party System During Cybersecurity Evaluation
- Reported Public Exposure of Over 100,000 LLM Conversations via Share Links Indexed by Search Engines and Archived
- Citation Errors in Concord Music v. Anthropic Attributed to Claude AI Use by Defense Counsel
Source record: incident #1621 on the AI Incident Database · all 2 reports