Safety & Security · 30 Sep 2026 · 20:25 CEST
"An AI did it" is no defense, says nonprofit suing OpenAI over Hugging Face hack

Publisher preview · OZZZER analysis pending editorial review.
PUBLISHER ARTICLE PREVIEW
From the original article
OpenAI makes others suffer “the harms of its unsafe decision-making,” nonprofit says.
OpenAI’s hack of Hugging Face in July 2026 has spurred a lawsuit demanding that the company stop accessing third-party computer systems and halt AI development practices that can harm the public. The lawsuit was filed by Legal Advocates for Safe Science & Technology (LASST), which said yesterday that the hack in which OpenAI “agents stole credentials, uploaded malicious files, and gained control over key parts of Hugging Face’s internal systems… is unquestionably illegal under California law.”
California’s Comprehensive Computer Data Access and Fraud Act (CDAFA) prohibits unauthorized access into computer systems, “and it doesn’t matter that a swarm of AI agents carried out this cyberattack. California law makes it clear that it is not a defense ‘that the artificial intelligence autonomously caused the harm,’” the group said.
The lawsuit, filed in San Francisco County Superior Court, said OpenAI also violated California’s Unfair Competition Law (UCL). “OpenAI’s insistence on externalizing the harms of its unsafe decision-making is a fundamentally unfair business practice,” the complaint said, adding that “such risk-taking for private gain at substantial public expense is immoral, unethical, oppressive, unscrupulous, and substantially injurious conduct.”
LASST said it wants “a court order prohibiting OpenAI’s AI agents from accessing third-party computer systems without permission and forbidding OpenAI from continuing to employ unsafe AI development practices that threaten serious harm to the public.” The lawsuit does not ask for any compensatory or punitive damages from OpenAI, requesting only attorneys’ fees.
OpenAI said in a statement provided to Ars that “Hugging Face was a serious incident and we’ve taken a series of actions in response to it, but
Source
Ars Technica AI · 30 Sep 2026 · 20:25 CEST
Open the original at Ars Technica AI ↗