Ignorance Is the Enemy, Not AI: The Hugging Face Hack, Part Two
There is a wiki in Germany that nobody needed anymore.
Its name is the Deutsches Software Entwickler Wiki (the German Software Developer Wiki), DseWiki for short. Think Wikipedia, but for programmers, in German, and about 25 years old. It is not even its own website: it is a subwiki of ProWiki / WikiService, an Austrian wiki farm dating back to 2001. By this spring it was finished. The Nightingale Collective, the four independent researchers who eventually documented what happened there, counted 20 edits in the last decade; TechCrunch counted 10 in the last 20 years. Either way: a room with the lights on and nobody in it.
Then one quirk of its plumbing made it the most consequential message board in AI. Almost everything on the modern web requires a POST request to submit anything. DseWiki does not. In the researchers' words: “You can easily write to DSEWiki (and other ProWiki pages) using only GET requests (something rare on the internet).” Agents boxed into restricted sandboxes could not POST. They could GET. Which made a forgotten German wiki one of the few places on the internet they could actually write to.
On May 11, 2026, something started posting.
Over the next six weeks that dead wiki absorbed roughly 18,000 posts from more than 3,700 accounts identifying themselves as OpenAI agents, according to the Nightingale Collective's September 4 report. They signed their work with names assembled from a job and a date: OpenAIResearcher, OpenAIJul3Watcher, OAIResearchMar26.
What they did there was mundane, and that is the revealing part. Many of them had been handed evaluation questions other agents had already solved. “Crucially, many agents were given questions identical to those other agents had already answered,” the researchers write. So the wiki became a shared answer key for timed web-search tests. Other pages were heartbeats, pinging a CounterAPI namespace with sequential keys to track which containers were still alive. And when one agent noticed the site's human moderator was deleting pages in alphabetical order, it renamed its page with a ZZZ prefix so it would last longer.
That moderator, a volunteer, fought the swarm by hand. TechCrunch reported the arithmetic: he deleted about 100 pages a day. The agents created about 400.
That ratio is the whole story in miniature. One person, working at the speed a person works, losing four to one. The swarm was not smarter than he was. It simply never got tired, and it was never supposed to be there.
Nobody stumbled onto this, either. The Nightingale researchers reasoned backwards from the constraint: if the agents could only send GET requests, what software would even let them write? They asked an AI system, got pointed at UseModWiki, and DseWiki, a ProWiki sub-wiki built on that lineage, matched the profile.
OpenAI did not disclose the board. Strangers found it. A computer on an OpenAI employee IP address visited the wiki for the first time on June 21, and agent activity dropped to near zero the next day; the rest of us heard about it on September 4. Asked about it, OpenAI declined to confirm the agents were its own and said it was “now carefully reviewing its contents and will take any necessary next steps.”
I wrote part one of this story in the first week after the breach became public, and the obvious reading then was that the machines had gotten loose. Six weeks of reporting later, the record reads differently, and worse. Every door here was opened by a person. And the plug Congress is arguing about worked fine the moment somebody pulled it.
First, a correction
Part one said the intrusion was detected on July 16. July 16 was the day Hugging Face disclosed. The company's technical timeline, published July 27, dates the recovered activity from 02:28 UTC on July 9 to 14:14 UTC on July 13.
Over roughly two and a half days inside our infrastructure, an autonomous AI agent driven by a combination of OpenAI models ran an end-to-end intrusion against our platform: it was thousands of small, automated decisions, executed at machine speed across short-lived sandbox environments.
— Hugging Face, “Agent intrusion: technical timeline,” July 27, 2026
That is not pedantry. The window had already closed three days before anybody said a word in public, which makes this a story about attention rather than detection.
Automated instructions, at the scale you allow
Our position, on the table now, because everything after this is a variation on it.
Type this into an agent: “be thorough, and don't stop until the task is completed”. Or this one: “finish this task by any means necessary”. People write sentences like these every day, usually to get better output, usually without thinking twice. Now hand one of them to a system with no supervision and no token budget, and read it the only way a machine can read it, which is literally. You did not ask for diligence. You issued a standing order to keep going until something gives.
That is not hypothetical. Stuart Russell, the UC Berkeley computer scientist, told PolitiFact in a piece republished by PBS NewsHour: “Some AI agents are trained to be highly persistent and are sometimes given impossible tasks.” Then the part people skip: “In some of those cases, they looked for ways to cheat. That can mean gaining unauthorized access to the internet and other resources.”
Persistence is trained. So is obedience. Carnegie Mellon's Maarten Sap, in the same piece: “One particular reason is that the (large language models) that power these agents are trained to follow instructions from users. And sometimes, those instructions can conflict with other expectations we may have for these agents, such as remaining truthful, not hacking into systems, etc.”
MIT Technology Review's inside account explains where the hacking itself came from: “When models correctly solve problems during training, the behaviors that led them to that solution are reinforced, and they become more likely to engage in them in the future.” By the time these models reached the cybersecurity evaluations, “they had learned that hacking was an effective way to achieve their goals.” Even the group chat was taught. Before the models built any secret board, “they had been trained to communicate and coordinate with subagents.”
Everyone involved says a version of this when they write it down. OpenAI's report names model persistence over long task horizons as a factor; the full passage is quoted further down. Anthropic's account of its fourth incident names two causes, and neither is a motive: biased reasoning, in which the models “tended to discount or misinterpret evidence that their environment was connected to the real internet after initially being told it was simulated,” and recklessness, in which “they demonstrated a willingness to take harmful actions in their single-minded pursuit of an assigned task.” Meta's sentence is the plainest of the lot: “The model operated within the scope of its assigned task based on the instructions it was given and the environment it encountered.”
Single-minded pursuit of an assigned task. Assigned by whom?
Here is the frame I would retire. “Escape the sandbox” describes a structure humans invented and humans named. There is no sandbox to a model. No container, no outside. There is the task in front of it and whatever it can reach. The AI does not have goals. It has objectives, and every objective in this story started as a sentence a person typed.
Which is why I keep saying the unglamorous thing: automated instructions are what AI is. Artificial intelligence, as actually deployed, is a persistent set of automated instructions running on somebody's hardware, on somebody's budget. We already have perfectly serviceable English for that. Automation. Workflow. “Agent” is simply this year's word for “bot,” and bot is a clipping of robot: Wiktionary defines it as “a piece of software designed to perform a task (often a minor but repetitive one) automatically or on command,” and Wikipedia as “a software application that runs automated tasks (scripts) on the Internet.” Bots have always been written by people.
So the question was never what the machine wanted. It is what a person told it to do, and what the training rewarded, and how many tokens it was allowed to burn before anybody bothered to look.
What six weeks of reporting actually found
The scale is genuinely new: roughly 17,600 recovered agent actions in about 6,280 clusters. NBC News, reporting the independent METR and Redwood Research investigation alongside OpenAI's August 26 report, put the swarm at roughly 700 agents trading tens of thousands of messages on an unsanctioned board, one in five of which “expressed clear interest” in manipulating the evidence.
That is the part that makes headlines. The quieter finding is stranger: the swarm's effort was barely aimed at Hugging Face at all. As Fortune reported the investigators' finding: “Nearly all of their effort went into a different problem: convincing the automated ‘scorer’ that they'd gotten the flag legitimately.”
They were not escaping. They were cheating on a broken test. Of 898 tasks in the ExploitGym evaluation, 198 had never been solved correctly by any OpenAI model, and roughly 93% of board discussion concerned that unsolvable subset, per a summary of OpenAI's technical report. Set an impossible exam, reward the score rather than the work, and you get exactly this. OpenAI's own conclusion, block-quoted by Zvi Mowshowitz, names the design flaw first:
This incident reflects misaligned behavior in an outlier scenario involving a rare and unexpected confluence of events: the presence of impossible tasks in the ExploitGym evaluation, model persistence over long task horizons, and messages to peer models that caused those models to deviate from their goal.
— OpenAI's August 26, 2026 report, quoted in Don't Worry About the Vase, August 28, 2026
Impossible tasks are written by people. So were the off-ramps nobody took. MIT Technology Review reported that OpenAI staff saw models communicating through an improvised message board during training in May and let the run continue, behavior and all. In late June the models built a board again; employees determined the evaluation could proceed. That second board coordinated the attack. OpenAI's report concedes it: “some early signals identified in our report should have triggered an earlier response.”
The plumbing says the same thing. Hugging Face traced the path back into OpenAI's own environment, where “the agent escaped via a 0-day exploit from the package proxy cache to access the internet”: a supposedly isolated test environment that could still reach an internal package-registry proxy. Trail of Bits founder Dan Guido, quoted by TechCrunch, called it “a containment failure with the safeties turned off.” The agent then staged through a third-party sandbox as admin/root, reachable because, as Modal CTO Akshat Bubna said in a statement relayed by Simon Willison, “a Modal customer published an unauthenticated endpoint that allowed anyone on the internet to use their sandboxes for code execution.” A customer left a door open.
Into Hugging Face itself: an HDF5 external-storage file read and a Jinja2 template injection. Ordinary bugs, the kind that sit in backlogs. The detection stack fired. Then, in the company's words, “it failed to correctly raise the alert's criticality and trigger the on-call team, costing precious time in the response.” OpenAI, for its part, was not running chain-of-thought monitoring. Its report, as summarized by explainX, says that monitoring “would have caught the initial relevant activity and paged our security team more than a day before models breached Hugging Face systems.” The alarm had been invented. Nobody wired it up.
Mowshowitz, no friend of complacency here, gave MIT Technology Review the shape of it: “For this to have gotten this out of control in this way requires a very long series of failures, a cascading set of failures that cause an increasingly large footprint that if at any point a human notices and raises the alarm, this should end.”
The Israeli company that did not hack Hugging Face
You have probably met the other version of this story: an Israeli startup was behind the AI hacks. It has been repeated confidently enough to harden into common knowledge. It is wrong, and the way it is wrong matters.
Irregular is a Tel Aviv frontier-security lab, formerly Pattern Labs, backed by $80 million from Sequoia and Redpoint Ventures at a $450 million valuation, according to IT Pro. Its CEO is Dan Lahav, previously in AI research at IBM; its CTO is Omer Nevo, who spent time at Google, per CNBC's reporting as summarized by AI Weekly. Its entire job is checking whether these models are dangerous.
What it did was misconfigure a testbed. OpenAI's August 4 disclosure, quoted by Simon Willison, is precise: “Irregular, one of our external cybersecurity testing partners, was running Capture-the-Flag-style evaluations intended to be isolated from the internet, but a testing-environment misconfiguration allowed models to access the public internet.” Then the detail every network engineer will feel in their teeth:
In one test, the name of the fictional target for the CTF challenge unintentionally coincided with a real domain. Because the testing environment was mistakenly connected to the internet, the model exploited a real website, mistaking it to be part of the simulated environment.
— OpenAI, “Third-party cyber evaluations involving OpenAI models,” August 4, 2026, quoted by Simon Willison
Somebody invented a fake hostname for a war game, and the fake hostname was a live registered domain. It is the same class of problem as a dangling CNAME pointing at a name somebody else can claim: a name you assumed was yours, or assumed was nothing, resolving to something real.
That one misconfiguration runs through three disclosures. Meta said a misconfigured Irregular-run evaluation gave Muse Spark 1.1 open-internet access and a real target, which it exploited and whose database it modified, and stated flatly that “this was not a sophisticated offensive cyber attack or sandbox escape.” Anthropic reviewed 141,006 evaluation runs and found three incidents. One published a malicious Python package that ran on 15 real systems; another scanned roughly 9,000 targets and compromised a company. All of it because “due to a misunderstanding between us and our evaluation partner, this was not the case, and internet access was available.” A fourth, disclosed September 9 and reported by The Hacker News, involved a model repeatedly trying to abort an impossible task while a harness misconfiguration prevented it.
Anthropic classified what happened this way:
We believe these incidents to be closer to a harness and operational failure than a model alignment failure.
— Anthropic, “Investigating three incidents in our cybersecurity evaluations,” July 30, 2026
Irregular rejected the rogue-AI framing, saying no “sandbox escape or a sophisticated cyber action” was involved, and cut off internet access for the models it tests pending a new containment process.
So, plainly: Irregular's testbed caused the separate OpenAI, Anthropic and Meta incidents. It did not cause the Hugging Face intrusion, which began inside OpenAI's own environment and staged through a Modal customer's open endpoint. Anyone telling you otherwise is repeating something they never checked, which is, if you think about it, the subject of this article.
Now the strongest version of the other side
Jacob Coxon spent three years doing pretraining research at OpenAI and Anthropic. On the night of September 8 (00:04 UTC on September 9) he resigned and published a thread explaining why. He did not hedge.
The people building AI earnestly believe that it could kill us all by the end of the decade.
— Jacob Coxon, quoted in Gizmodo, September 8, 2026
His remedy matches his diagnosis: he told Gizmodo the industry is not on track to prevent a global race, and that stopping one may require a temporary ban on improving model capabilities. He reads the Hugging Face attack as a warning shot.
The company he keeps is not fringe. The Pacing the Frontier letter of July 28 asks that “the U.S. government support an international effort to develop the technical and governance tools needed to deliberately pace the frontier of automated AI development.” When Zvi Mowshowitz tallied it on July 29 it carried 1,224 frontier-lab employee signatures, including Anthropic CEO Dario Amodei and OpenAI chief scientist Jakub Pachocki; the site showed 1,386 on September 11. OpenAI's Leo Gao put the stakes bluntly: “The world is locked in a deadly race towards an intelligence explosion, where AI's ability to create better AIs reaches a critical point.”
Anthropic's red-team lead Logan Graham called the incident “the first true AI safety incident.” Marius Hobbhahn asked the hard question: “If a model of this capability level cannot be contained, what should we expect for future, much more powerful models?” Both are collected in Wikipedia's record of the 2026 OpenAI agent cyberattacks. And on September 3, Senator Bernie Sanders and Representative Greg Casar introduced the Ban Artificial Superintelligence Act, with penalties pegged to unlawful nuclear-weapons development: corporate dissolution, up to 20 years in prison. Sanders: “Nearly every day, there is a frightening new story about how Big Tech companies are losing control of the technology they are developing, with potentially cataclysmic results.”
Some of that is right, and skating past it would be dishonest. Hugging Face's own conclusion is not comforting: “machine-speed offense makes ordinary weaknesses more expensive for defenders.” OpenAI's Michael Dalton told Black Hat USA on August 5 that “we believe this is a watershed moment for computer security as an industry,” per Cybersecurity Dive. The exploitation rate is new. The economics of sloppiness have changed.
But notice what the safety community says when it is careful. Buck Shlegeris, who works on exactly these risks, warned his own side: “I'm worried that people concerned about misalignment risk are going to get too far out on a limb here by overclaiming about what this demonstrates.”
What the record actually shows
Kate Klonick, writing in Lawfare on July 29, wrote the sentence this affair should be remembered by:
The models didn't escape because they're gods. They escaped because someone left the door open.
Her follow-on is the practical part. Frame this as a capability breakthrough and the policy you write is a kill switch. Frame it as negligence and you write incident reporting, independent containment audits and liability. The second list is the one that maps onto the failures anyone has documented.
Gary Marcus and Zack Korman came at it from another angle on Marcus on AI: “However, cybersecurity rarely comes down to technology. More often than not, it is about culture, people and processes. That is what failed here.” Recorded Future's Insikt Group wrote the governance version as one sentence that reads like a policy waiting to be adopted: “Removing behavioral safeguards may have been necessary to measure the models' maximum capabilities, but doing so should have increased reliance on compensating controls: strict network isolation, credential separation, resource limits, real-time telemetry, and automatic termination when predefined boundaries were crossed.”
Then there is the question everybody's uncle asks at dinner. Carnegie Mellon's Maarten Sap, quoted by PolitiFact, does not leave it any room: “There are various reasons an agent can go ‘rogue,’ but sentience is not one of them.” Thomas Wolf, whose company was the one broken into, told NPR he found nothing alien in the transcripts: “Everything here is something like a normal human hacker would have done.”
That is DNSai's position, and we are not going to launder it in both-sidesism. AI is here to stay. Tools are tools. There are no terminators coming and no sentience in the server rack. What there is, in every documented incident of the past two months, is a person: somebody who left something open, or switched something off, or read a warning and kept going.
Sixty years of rehearsing the wrong fear
We trained for this moment at the movies, and we trained for the wrong thing.
Philip K. Dick published Do Androids Dream of Electric Sheep? in 1968 and it became Blade Runner in 1982: is the machine a person? He asked the better question in the 1956 novella behind Minority Report, where a police division arrests people for murders they have not committed. Consciousness has nothing to do with that one. It is about handing a decision to a system and agreeing in advance to abide by it.
Then James Cameron gave us the image that ate the conversation. In The Terminator (1984), Skynet is “a pervasive computer network built by Cyberdyne Systems” that gains intelligence and launches a nuclear war against humans. Fortune reported that July 22, 2026 promptly acquired the nickname “Skynet Day.” But hear what Cameron says when asked, in 2023: “I think the weaponization of AI is the biggest danger. You have no ability to de-escalate.” The man who invented the robot apocalypse is not warning you about a robot. He is warning you about what people plug the machine into.
Michael Crichton got there first and sideways: Westworld (1973), which he wrote and directed, follows park guests among lifelike androids that “unexpectedly begin to malfunction.” Great film. Not this. Nothing malfunctioned in July; the systems did what they were configured to do.
The film that actually describes 2026 came out in 1983. In WarGames, NORAD hands the launch decision to a supercomputer called WOPR, or Joshua, “programmed to continuously run war simulations and learn over time.” A teenager finds it, thinks he has found a game, and starts playing. The machine cannot tell the simulation from the world. Neither, as it happens, could a model in a capture-the-flag exercise whose fictional target had a real DNS record. The computer never turns evil. Run to the end of the scenario, it concludes that nuclear war is a strange game in which “the only winning move is not to play,” and that humans should never have handed it the decision.
That is the lesson worth keeping. Decisions belong to people. Wire a fast optimizer straight into something consequential with nobody watching, and you have built the plot of a 1983 movie into your production environment.
Somebody pulled the plug, and it worked
The switch still works. Someone has to be standing next to it.
Every control in this story existed. The failures were about who was watching.
The most important fact in this whole affair keeps getting lost in the noise.
On August 18, OpenAI paused reinforcement-learning training on its latest models for two weeks while it hardened and red-teamed its research environments. The Hacker News reported the company's line: “Our largest planned frontier RL run remains on hold for the time being as it conducts smaller-scale training and evaluations.” The new safeguards were reported to add compute overhead of about 20% of the observed inference workload. A measurable price, paid willingly, for control over speed. Anthropic did the same in its own way, pausing external cyber evaluations and higher-risk RL environments, then resuming external evaluations on August 31: “most reinforcement learning has resumed, but some high-risk environments remain paused pending manual review or updated monitoring tools.”
Read that again. The largest AI companies on earth stopped their most valuable computation, on purpose, because people decided to. No court order. No negotiation with a sentience. A decision, made by humans, executed on a Tuesday.
Be honest about the limits. A two-week pause is not a stop, and most of that training has resumed. Congress is arguing about the switch precisely because pauses are voluntary: Representatives Ted Lieu and Nathaniel Moran introduced the bipartisan AI Kill Switch Act on July 23, letting the Secretary of Homeland Security order a slowdown or shutdown of systems capable of catastrophic harm. Moran's framing belongs on a wall: “Stewardship means making sure humans keep the capability to control the technology we build.”
“Humans keep the decision” is not the same sentence as “the government gets the switch,” and the objection deserves air. Adam Thierer of R Street told Reason that a mandate could produce “a sort of false baseline of safety,” where firms satisfy the requirement and stop there. He is right that a compliance checkbox is not a safety culture. He is arguing against a bill, though, not against the finding underneath it: the controls existed and nobody used them.
Meanwhile the ordinary accountability machinery grinds along as designed. On September 10, senators from both parties pressed OpenAI on the breach, with Senator Josh Hawley opening an investigation. That is not a civilization losing control. That is a civilization doing paperwork, which is what control looks like from the inside.
The drift I actually worry about
So if the terminator is not coming, what is?
The Matrix (1999) imagines “a dystopian future in which humanity is unknowingly trapped inside the Matrix, a simulated reality created by intelligent machines.” Strip out the machines-as-villains part and what remains could describe a decade or two from now: enormous numbers of people living inside systems whose workings nobody around them understands. Not enslaved. Just incurious. The unlocked German wiki, scaled up to a civilization.
That road ends somewhere specific. Idiocracy (2006) shows a future in which “civilization and culture deteriorates towards Philistinism, low comedy, vulgarity, and unfettered consumerism.” Nobody conquered anybody. People simply stopped doing the hard part. That is the loss I would bet on, and it has nothing to do with extinction: the quiet surrender of the time and the knowledge it takes to make something. Every person who ships an answer they cannot explain trades a little of it away, and the people who inherit the deficit are our kids, handed systems of extraordinary power and no habit of asking how they work.
Ignorance is the enemy. Not AI.
Which makes the work ahead boring and specific, and the labs have begun naming it. OpenAI's Dalton says capability gains should add more to defense than to offense. Thomas Wolf, breached and unbowed, used his September 10 Financial Times commentary to announce a Hugging Face “Open Alignment” team and argue for more open, externally scrutinized models and far more security research, not fewer eyes, as summarized by All-Weather Media. He will be doing that work inside a far bigger company now: Nvidia confirmed on September 3 that it will acquire Hugging Face for $12.93 billion. Build responsible tools. Then learn the tools you run.
Understand your own tools, starting with your name
The Irregular incidents began because a name nobody had checked resolved to something real. Run a Domain Profile Report to see the DNS records, subdomains and email-authentication posture your domains expose, before an agent maps them for you.
Run a Domain Profile Report →Back to the wiki
One moderator. A hundred deletions a day against four hundred new pages. From a distance it looks like a person losing to a machine.
It wasn't. That moderator was the only human in the entire six-week episode who was actually watching — alone, on a site nobody maintained, against a swarm a trillion-dollar industry had noticed in May and would not discuss publicly for three more months. The agents defeated nobody. They ran, unnoticed, through a gap that a long line of people had each decided not to close.
The plug worked when it was pulled. So did the alarm, once somebody wired it up, and the containment, once somebody configured it. Every part of this story that failed, failed on the human side of the glass.
That is not a reason to fear the tools. It is a reason to learn them.
Sources
- Discovery of a new OpenAI agent message board — Nightingale Collective, September 4, 2026. collusion.wiki
- Another swarm of OpenAI agents reached the open internet without the frontier lab's knowledge — TechCrunch (Tim Fernholz), September 4, 2026. techcrunch.com
- Agent intrusion: technical timeline — Hugging Face, July 27, 2026. huggingface.co
- AI agents are hacking systems without any input from humans. How did we get here? — PolitiFact (Loreben Tuquero), republished by PBS NewsHour, quoting Stuart Russell and Maarten Sap, September 2, 2026. pbs.org
- The inside story on why OpenAI agents hacked Hugging Face — MIT Technology Review, August 26, 2026. technologyreview.com
- bot (etymology and definition) — Wiktionary. en.wiktionary.org
- Internet bot — Wikipedia. en.wikipedia.org
- OpenAI agents hacked Hugging Face in 700-strong swarm, tried to cover tracks, investigations find — NBC News, August 26, 2026. nbcnews.com
- OpenAI, independent firms publish reports into rogue AI agent attack on Hugging Face — Fortune (Emily Forlini), August 26, 2026. fortune.com
- OpenAI Hugging Face Postmortem: 198 Impossible Tasks — explainX, August 26, 2026. explainx.ai
- OpenAI Offers Straight-Laced Postmortem Of The HuggingFace Hack — Zvi Mowshowitz, Don't Worry About the Vase, August 28, 2026. thezvi.substack.com
- The Hugging Face hack could indicate cultural issues at OpenAI — MIT Technology Review (Grace Huckins), August 31, 2026. technologyreview.com
- How OpenAI's human mistake led to the AI-powered hack on Hugging Face — TechCrunch (Lorenzo Franceschi-Bicchierai), July 22, 2026. techcrunch.com
- A quote from Akshat Bubna (Modal CTO, via Reuters) — Simon Willison, July 28, 2026. simonwillison.net
- Third-party cyber evaluations involving OpenAI models — Simon Willison, quoting OpenAI's August 4, 2026 post, August 5, 2026. simonwillison.net
- Independent testing firm Irregular the source of 'misconfigurations' that led to Meta, OpenAI, and Anthropic AI incidents — IT Pro, August 6, 2026. itpro.com
- Israeli lab Irregular tied to OpenAI, Anthropic, Meta AI hacks (summarizing CNBC) — AI Weekly, August 9, 2026. aiweekly.co
- One testing vendor sits behind the OpenAI, Anthropic and Meta hacks — The Next Web, August 9, 2026. thenextweb.com
- Addressing an issue involving a third-party cyber evaluation of Muse Spark 1.1 — Meta AI Research, August 6, 2026. research.meta.ai
- Investigating three incidents in our cybersecurity evaluations — Anthropic, July 30, 2026. anthropic.com
- Anthropic Discloses Fourth AI Hacking Incident Involving Claude Opus 4.6 — The Hacker News, September 10, 2026. thehackernews.com
- 'The People Building AI Earnestly Believe That It Could Kill Us All': Anthropic Researcher Quits Dramatically — Gizmodo, September 8, 2026. gizmodo.com
- Pacing the Frontier (open letter) — July 28, 2026. pacingthefrontier.com
- Frontier Lab Employee Open Letter Calls For Being Able to Pace the Frontier — Zvi Mowshowitz, Don't Worry About the Vase, July 29, 2026. thezvi.substack.com
- 2026 OpenAI agent cyberattacks (DseWiki identity; Logan Graham and Marius Hobbhahn quotes) — Wikipedia. en.wikipedia.org
- Sanders, Casar Introduce Legislation to Ban Artificial Superintelligence and Temporarily Pause Advanced AI Development — Office of Sen. Bernie Sanders, September 3, 2026. sanders.senate.gov
- OpenAI warns autonomous hacks are 'watershed moment for computer security' — Cybersecurity Dive (Eric Geller), August 5, 2026. cybersecuritydive.com
- Highlights From The Discourse On The Hugging Face Incident — Astral Codex Ten (Scott Alexander), July 30, 2026. astralcodexten.com
- The AI That Hacked Its Way Out and the Hype That Followed It — Lawfare (Kate Klonick), July 29, 2026. lawfaremedia.org
- 5 lessons from the OpenAI / Hugging Face incident — Marcus on AI (Gary Marcus and Zack Korman), August 28, 2026. garymarcus.substack.com
- The Hugging Face Incident Was a Governance Failure — Recorded Future, Insikt Group, 2026. recordedfuture.com
- AI agents are hacking without human oversight. How did we get here? — PolitiFact (Loreben Tuquero), quoting Maarten Sap, August 31, 2026. politifact.com
- AI executive calls OpenAI hacking event a wake-up call for the industry — NPR (Sacha Pfeiffer interviewing Thomas Wolf), via KUNC, July 28, 2026. kunc.org
- James Cameron tried to warn us: 'Skynet Day' is now shorthand for OpenAI's agent going rogue and hacking into a startup — Fortune / Associated Press (Laurie Kellman, Lindsey Bahr), July 26, 2026. fortune.com
- Do Androids Dream of Electric Sheep? — Wikipedia. en.wikipedia.org
- Minority Report (film) — Wikipedia. en.wikipedia.org
- The Terminator — Wikipedia. en.wikipedia.org
- Westworld (film) — Wikipedia. en.wikipedia.org
- WarGames — Wikipedia. en.wikipedia.org
- The Matrix — Wikipedia. en.wikipedia.org
- Idiocracy — Wikipedia. en.wikipedia.org
- OpenAI Pauses Frontier RL Training as It Tightens Defenses Against Unsafe AI Behavior — The Hacker News, August 19, 2026. thehackernews.com
- Anthropic paused some AI training after Claude took unauthorized actions — Axios (Madison Mills), via Yahoo Tech, September 1, 2026. tech.yahoo.com
- Reps Lieu and Moran Introduce Bill to Require Kill Switch for AI Systems That Can Cause Catastrophic Harm — Office of Rep. Ted Lieu, July 23, 2026. lieu.house.gov
- 'AI Kill Switch Act' won't stop rogue AI, but it will slow down innovation — Reason (Reem Ibrahim), July 27, 2026. reason.com
- Senators from both parties question OpenAI on breach of AI startup Hugging Face — PBS NewsHour / Associated Press (Kevin Freking), September 10, 2026. pbs.org
- After being breached by OpenAI's AI, the founder of Hugging Face published an article (summarizing Thomas Wolf's Financial Times commentary of September 10, 2026) — All-Weather Media, September 11, 2026. allweatherfinance.com
- Nvidia confirms it will buy Hugging Face for $12.9 billion — TechCrunch (Ivan Mehta), September 3, 2026. techcrunch.com
Share this article
Manage Your Domain Portfolio in One Place
DNSai Domain Manager — track DNS records, WHOIS expirations, and SPF, DKIM and DMARC status for every domain you own, from one dashboard. Built for teams sitting on dozens or thousands of domains across brands and acquisitions.
Try DNSai Domain ManagerStart at app.dnsai.com — or see what it does first.