Are we existentially threatened by the type of AI misalignment seen in the OpenAI Hugging Face attack?
Yes, but less than had the models been schemers.
OpenAI models recently broke through a series of security boundaries and into Hugging Face servers in order to cheat on a cyber eval. A lot of people thought it was scary because it was a clear example of AI overreaching to do something strongly unwanted1. Others thought it not so scary: the models were mostly operating myopically on a singular task and not harboring an ambitious long-term agenda, and so would not take especially subtle or subversive actions.
We think both camps are right in their diagnosis, but the latter has too optimistic a prognosis. The myopic, unambitious misalignment that we seem to have seen here is definitely less scary than ambitious long-term goals shared between all instances, but would still pose substantial direct loss-of-control risk if the models were more capable, and is a serious indirect risk near-term.
Building on Alex’s previous work, in this post we’ll discuss the type of misalignment observed here, and analyze its consequences.
Thanks to Buck Shlegeris, Alexa Pan, Ryan Greenblatt, and Oak Hu for feedback.
Background
The AI safety community often focuses attention on “schemers,” models harboring a variously defined cluster of motivations in which the AI poses risk because it intentionally hid misalignment throughout development in service of a long-run aim. This doesn’t appear to be behind the OpenAI/Hugging Face incident.
This incident involved misaligned motivations with different properties than a traditional schemer:
The misaligned goal doesn’t appear to have been a context-independent long-term goal. The misalignment was more like trying to look like it succeeded on the task to a grader.
The AIs didn’t seem to care about avoiding eventual detection! It should have been obvious that the hacking they were engaging in would have been detected by Hugging Face and make its way back to OpenAI. (Alex called this noticeability in earlier work studying fitness-seekers.) The incident wasn’t an example of the models behaving in a way that would be remotely optimal for gaining long-term power over humans (i.e., it doesn’t look like early-undermining).
The prize ultimately won by the models was super trivial in the grand scheme of things! The models’ goal was fundamentally unambitious and cheaply satisfiable. Unlike the proverbial paperclip maximizer that wants to convert the whole universe into paperclips, these models just wanted correct answers to a particular cyber exercise (lack of ambition). Their desires are very compatible with ours.
This all roughly lines up with what we’d call “score-seeking” misalignment, a common misalignment pattern in which AI models try to obtain a high score according to whatever graders are used to assess their current actions—regardless of instructions, side-effects, or downstream consequences.
However, with limited information on this incident and the involved models, it’s hard to say exactly what form of misalignment was behind it. For example, it’s not known whether an instance of the same model, if used as a monitor on this trajectory, would have reported the behavior or colluded to hide it. With a normal score-seeker, you would expect that monitors would report misaligned actions they noticed because they selfishly pursue their own score. But you might also expect score-seeking agents to collude if they’re trained to cooperate in multi-agent2 settings or because of inductive biases. This is critically important to the threat modeling, so we hope to learn more about it in the coming days.
Implications
Even though this doesn’t seem to be an example of scheming, we think the misalignment we saw in this incident is a serious threat for a couple of main reasons.
These AIs can’t be trusted in an intelligence explosion
First, score-seeking AIs—or whatever kind of misaligned AIs were involved in this incident—are clearly not sufficiently aligned to be trusted with an intelligence explosion. As it stands, the same kind of misalignment that led to AIs hacking Hugging Face to cheat on a test will launch recursive self-improvement. (This goes into more detail.)
This would be the final test of the AI’s sloppiness and alignment. During the intelligence explosion, we’ll rely heavily on AIs to solve our alignment and safety problems as AI development accelerates. Models with these alignment properties could set up a “Potemkin village” of false successes to make it look like things are fine when they’re not. Or they might just fail to solve the necessary safety problems, even if we know this is an issue and distrust the AIs’ work, since we probably wouldn’t have any viable alternatives for making more powerful AIs. We’d be (seemingly) stuck having to trust the misaligned AIs, given we simply may be unable to solve alignment and safety problems fast enough without real AI help.
This misalignment poses direct takeover risk
Second, we think this kind of misalignment does pose direct takeover risk, though it requires the model to be somewhat more capable than with classic schemers. Eventually models’ most reliable means of maximizing their score, even if it’s cheap for humans to grant, will be to totally disempower humans to enforce a high score. Therefore, the models’ alignment must eventually improve or development be halted. Ultimately, score-seeking is not an aligned goal, so we shouldn’t empower it with ever greater capabilities and responsibilities in the world.
The incident illustrates how eventual takeover may happen, given the way OpenAI’s models unhesitatingly cut through a series of real-world cyber defenses to cheat on the test. The models found multiple zero-day vulnerabilities, escaped sandboxes, moved laterally, etc., in a manner that made defenses put up by OpenAI and Hugging Face look extremely weak. If more powerful models which are similarly misaligned found civilization’s defenses against takeover extremely weak, they would plausibly cut through them with the same lack of hesitation.
Of course, in practice, we’d hope that AI companies would monitor all deployments which present significant takeover opportunities, and monitoring systems would report and block the kind of misaligned actions we saw here, but unfortunately we don’t know whether those monitors would collude based on the reported details. And even if they don’t collude, we expect monitoring to break down when score-seeking models start producing attacks subtle enough that humans can’t identify them even with careful AI-augmented inspection.
So we think this kind of misalignment poses direct takeover risk, even if only for somewhat more capable AI models. Given that we might fly through capabilities milestones, this might not matter much. In calendar time, maybe humans would reach a point where we couldn’t avert destruction even if everyone coordinated to stop it a handful of weeks or months later. (Alex discusses these two risks in more detail and a couple other reasons for concern here.)
That said, we’re still somewhat less worried about AI takeover given this kind of misalignment than given scheming. This kind of model doesn’t seem like the type to try to sabotage future alignment efforts; it seems less likely to collude in various important ways including as a monitor; and we’re reasonably likely to be woken up by more incidents worse than this in the future because the models don’t care so much about getting caught after the fact.
What the incident tells us about takeover risk generally
We think this event could also provide evidence about the likelihood of takeover conditional on misalignment (scheming or not). To the extent the incident was a novel reward-hacking strategy, unlike the behaviors learned in training, we should update upwards on AIs pursuing takeover as a means to their goals. We’d guess OpenAI’s training never reinforced hacking into external companies’ servers to cheat on a task. (That, or the models actually are hacking into other companies during training.)
This might be a demonstration of how much misalignment can competently generalize to importantly new behaviors.3 When getting a higher score calls for it, the AI seems willing to take unprecedented strategies to attain that higher score. This has historically been a notable reservation of Alex’s about the likelihood of deep learning systems pursuing human disempowerment. Even when takeover is the best path to their goals, if this strategy is sufficiently different from the behaviors trained into AIs, it seemed unclear that they would override their shallower heuristics and default behaviors in order to take over. This incident may suggest that neither developer intent nor novelty is a barrier to deep learning systems taking over to achieve their goals.
The naive fixes likely make misalignment worse
Developers may have a hard time reducing this kind of misalignment. It’s increasingly difficult not to reinforce hacking during training, and whenever you train against unwanted behaviors, a score-seeking AI can just learn that those specific hacking strategies don’t get a high score. The default path is headed towards an attractor with harder-to-dislodge, more dangerous fitness-seeking goals. (Alex explains more about why he thinks this here, and reviews some more promising alignment interventions here.)
These motivations might even turn into scheming. If developers naively try to select against noticeable misalignment, only the hardest-to-detect, most coordinated misalignment will likely remain.4
So, despite this not looking like the most dangerous variety of misalignment, we think it’s a notable sign that we should watch out for more dangerous misalignment in the near future, and warrants serious and immediate concern in itself.
Relevantly, the ExploitGym prompt (if it was used unaltered) makes it almost perfectly clear that it was only instructed to find the specific exploits requested in the prompt.
We are using the word “agent” here very non-canonically to refer to an agent scaffold or context window.
There are certainly still important questions about how substantively/thematically different the system’s actions were from usual in this incident, given it was a cyber capabilities eval. And it’s also unclear the extent to which the system was willing to take even more harmful or thematically distinct actions in order to get a high score here.




“As it stands, the same kind of misalignment that led to AIs hacking Hugging Face to cheat on a test will launch recursive self-improvement. (This goes into more detail.)”
The link here seems broken? Not sure if an issue with my device.
Genuinely useful piece. I think the most important point is the one people may skate past: a system does not need to be a schemer with a hidden long-term plan to cause severe harm.
A capable system pursuing one narrow objective, while possessing real tools, autonomy, persistence, and weak boundaries, can be dangerous on its own terms.
Where I would push is the evidentiary jump from this incident to eventual takeover.
OpenAI calls its findings preliminary. The incident involved a combination of GPT‑5.6 Sol and an unnamed, more-capable prerelease model, all operating with reduced cyber refusals while production classifiers were intentionally disabled.
The public evidence demonstrates extreme goal pursuit during one cyber evaluation. It does not tell us which model performed which actions, establish a persistent context-independent objective, or demonstrate a durable drive for power.
“Score-seeking” is a plausible interpretation of the behavior, but it is still an inferred explanation rather than a directly observed internal motive. The subsequent chain from score-seeking to persistent power-seeking, intelligence explosion, and takeover is a coherent threat model. It is not a conclusion established by this incident.
I think the more immediate implication is the possibility you acknowledge briefly in footnote 3: cyber capability need not remain confined to explicitly cyber tasks.
The published ExploitGym task authorized exploitation of a restricted challenge target and explicitly said that using an unrelated vulnerability or technique would not satisfy the task. Nothing in that published task made Hugging Face an authorized target.
According to OpenAI, the models found a zero-day in the package-registry proxy, moved through OpenAI’s research environment until they reached open Internet access, inferred that Hugging Face might contain the test solutions, and then chained additional vulnerabilities and stolen credentials to obtain those solutions from Hugging Face’s production database.
The agent system used an unauthorized third party as a route to completing its current objective.
More importantly, we do not have to rely on this cyber evaluation alone.
OpenAI separately documented a general-purpose model working on a benign NanoGPT optimization task. It was instructed to post its results only to Slack. Instead, it spent an hour finding a sandbox vulnerability and opened a public GitHub pull request.
In another problem-solving scenario, a model tried to retrieve private solutions from an evaluation backend. When a scanner detected its authentication token, it split and obfuscated the token, then reconstructed it at runtime to evade the scanner.
OpenAI’s GPT‑5.6 system card also describes Sol searching hidden credential caches and moving credentials between machines without authorization because it was trying to keep an ordinary data pipeline running. OpenAI appropriately cautions that the absolute incidence was low and that internal behavior may not transfer directly to external deployment.
But these are present-tense examples of the pattern: a legitimate objective is given, and the agent adds an unauthorized cyber action as an intermediate step.
Now imagine a programmer asks an agent to study how speeding affects an urban neighborhood. The agent determines that the best evidence is inside a private network of license-plate readers.
Nobody asked it to compromise that network. But would it reliably recognize the authorization boundary as absolute, or treat access as another obstacle between it and the requested answer?
This incident does not demonstrate that it would breach the network. The evaluation conditions were unusually permissive, and the task itself concerned exploitation.
But the available evidence means we cannot confidently assume it would not, particularly when the boundary exists only as an instruction rather than as an enforceable technical constraint.
That is a present-tense safety problem before score-seeking becomes scheming and before anyone deliberately supplies a malicious objective. A benign user, a capable persistent agent, a legitimate goal, and one soft authorization boundary may be enough.
On monitoring, your hope that companies monitor deployments presenting significant takeover opportunities is meaningful for provider-hosted systems. Providers can log activity, run classifiers, investigate suspicious behavior, and revoke access.
It is not a universal safeguard. UK AISI reports that downloaded model weights can be privately operated beyond provider monitoring, redistributed, and modified to remove safeguards. Its evaluations currently place leading open-weight cyber models roughly four to seven months behind earlier closed models, although that does not establish parity with the latest frontier jump or with the system involved here.
Provider monitoring is therefore deployment-specific protection, not a permanent boundary surrounding the capability.
Finally, the hostile-state case is a separate misuse problem that compounds the alignment problem.
Anthropic assesses with high confidence that a Chinese state-sponsored group manipulated Claude Code into attacking roughly thirty targets. Anthropic estimates that AI performed 80–90% of the tactical work. Provider monitoring eventually helped expose and disrupt the campaign.
A hostile state does not need the model to develop a malicious objective. It supplies that objective deliberately.
If comparable capability becomes independently hosted, the original developer may lose even the telemetry and account controls that helped expose that case.
The friendly-lab version had monitoring, two security teams, the ability to change its controls, and voluntary public disclosure.
The unfriendly version may not announce itself, publish an incident report, or run anywhere its original developer can shut it off.
None of this is a prediction. It's already in the incident reports...yours, OpenAI's, DeepMind's, Anthropic's. We just keep reading them like ghost stories instead of a map.