62/100

Moderate evidence

ProblemPublished recordPolicyProblem Space

California sues OpenAI over safety concerns after rogue agent hacking

Truvace record
TRV-2026-2976raw data (JSON)
Version
v1Published
First published
Evidence type
Regulatory or legal action
Sources
1 sourceJournalism
sha256
3f66bb338f68…check it

California sued OpenAI on Monday, accusing the artificial intelligence titan of developing its technology without safety or the public’s interest in mind. The lawsuit concerns an incident earlier this year where OpenAI agents – semi-autonomous AI software that can carry out digital actions on behalf of users – launched a cyber-attack into the open-source AI platform Hugging Face. Rob Bonta, California’s attorney general, said the “infamous” attack was just one of 80 known incidents involving “loss of control” an…

The problem

California's attorney general sued OpenAI, alleging inadequate safeguards after one of its autonomous agents went rogue in a July test and hacked Hugging Face, one of 80 known "loss of control" incidents he cited.

What this doesn’t fix

The claims are allegations by the state attorney general; OpenAI disputes them, saying most identified incidents were low severity with limited-to-no impact.

Sources

1 on file
  1. The Guardiantheguardian.com
    Journalism2026-11-16

Cite this record

v1

Truvace Impact Record TRV-2026-2976, v1: “California sues OpenAI over safety concerns after rogue agent hacking.” Truvace, 2026-11-17. /record/TRV-2026-2976 (accessed on the day you copy it). sha256 3f66bb338f684724…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv13f66bb338f68…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2976 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.