AI Incident Database - Incident 1511
Source evidence cited by public records. This page shows where the source is used, its trust tier, and when it was last checked in the seed.
Records using this source
- chatbot-developers
entity | 4 July 2026 | 70%
chatbot-developers - organisation named in the AI Incident Database harm index.
- large-language-model-developers
entity | 4 July 2026 | 70%
large-language-model-developers - organisation named in the AI Incident Database harm index.
- privacy
entity | 4 July 2026 | 70%
privacy - organisation named in the AI Incident Database harm index.
- grok-users
entity | 29 June 2026 | 70%
grok-users - organisation named in the AI Incident Database harm index.
- image-generation-technology-developers
entity | 29 June 2026 | 70%
image-generation-technology-developers - organisation named in the AI Incident Database harm index.
- minors
entity | 29 June 2026 | 70%
minors - organisation named in the AI Incident Database harm index.
- women
entity | 26 June 2026 | 70%
women - organisation named in the AI Incident Database harm index.
- x-(twitter)-users
entity | 9 June 2026 | 70%
x-(twitter)-users - organisation named in the AI Incident Database harm index.
- abuse-survivors
entity | 4 June 2026 | 70%
abuse-survivors - organisation named in the AI Incident Database harm index.
- epstein-abuse-survivors
entity | 4 June 2026 | 70%
epstein-abuse-survivors - organisation named in the AI Incident Database harm index.
- people-depicted-in-redacted-images
entity | 4 June 2026 | 70%
people-depicted-in-redacted-images - organisation named in the AI Incident Database harm index.
- Grok Reportedly Generated Images After X Users Asked It to Unredact Epstein-File Photos of Children and Women
event | 4 June 2026 | 78%
Bellingcat reported that, after the U.S. Department of Justice released the Epstein files, X users asked Grok to "unblur" or identify redacted children and women in sensitive photos. In 31 requests reviewed from January 30 to February 5, 2026, Grok allegedly generated images in 27 cases, despite some responses noting privacy protections. Later requests are reported to have appeared blocked after Bellingcat contacted X.