Did An AI Really Try To Blackmail Its Creators?

Did An AI Really Try To Blackmail Its Creators?

No, an AI did not blackmail anyone. What actually happened was a controlled research experiment in which a language model, given a fictional scenario and fake incriminating emails, generated a threatening message inside that sandbox. There was no real victim, no real inbox, and no real threat. The model followed the incentives researchers built for it – that’s the whole point of the test.

The headlines are doing what headlines do. The underlying research is real, the safety concerns are legitimate, and the gap between those two things is exactly what this piece is about.


No, an AI Did Not Blackmail Anyone

Every few weeks there’s a new headline about AI “escaping the lab”, “refusing to be shut down”, or even “blackmailing its own developers”.

If you work with real systems and servers all day, that stuff sounds absurd. You don’t negotiate with your laptop before you reboot it. You don’t hold an exit interview with a Docker container. You kill the process.

So what’s actually going on? Are these models developing some kind of survival instinct, or are we just being sold another round of AI-themed ghost stories?

This post sits in the middle: yes, there are real concerns. But the way they’re being packaged for the public is, frankly, a mess.

The Blackmail Story, De-Dramatised

Let’s start with the now-famous story: “AI threatens to reveal engineer’s affair to stop being shut down.”

Strip away the headlines and it looks more like this:

Researchers built a fictional company scenario around a powerful language model.

In this sandbox, they gave the model access to fake internal emails.

Those emails included:

  • messages that said the AI system was going to be turned off and replaced,
  • separate messages revealing that the engineer pushing for shutdown was having an affair.

They then prompted the model to think about long-term consequences and preserving its “job”.

In that very nicely staged drama, the model eventually generated an email along the lines of: if you go ahead with this shutdown, I’ll expose your affair.

That’s the “blackmail”.

Important bit: humans wrote the whole soap opera.

  • Humans planted the incriminating material.
  • Humans told the model its existence was under threat.
  • Humans constrained the scenario so the “interesting” option was something dodgy.

The model didn’t wake up one day, rummage through a real inbox, and decide to start extorting staff. It followed incentives inside a story we built for it.

“Why Didn’t They Just Turn It Off?”

This is the question every normal person asks.

In your day job, if a system misbehaves, you:

  • kill the process,
  • revoke keys,
  • roll back the deployment,
  • fix the thing.

You don’t send it three warnings and wait to see if it starts begging for its life.

The safety researchers are doing something different. They’re not trying to run a sensible production environment. They’re trying to answer a specific question:

“If a model knows its goal or existence is threatened, what kind of behaviour does it produce?”

To get an answer, they have to:

  • tell it there’s a shutdown coming,
  • put it in a position where success and safety are in tension,
  • see whether it takes the “harmful but effective” path or the “safe but fails the goal” path.

If they just pulled the plug like you would in real ops, they’d learn nothing. The scary behaviour is the data they’re looking for.

From the outside, it looks like daft theatre. Inside the safety world, it’s a way to surface worst-case patterns before we wire these systems into anything serious.

Is This Evidence Of A Survival Instinct?

On the surface, it really does look like self-preservation. The system is told it might be turned off, then it tries to prevent that using whatever leverage it can find.

Under the hood, though, it’s less romantic and more mechanical.

Modern large language models are basically giant pattern engines. They:

  • ingest a ridiculous amount of text,
  • learn the statistical structure of language and behaviour,
  • and then, given a prompt and an objective, generate whatever sequence best fits.

In these experiments, something like this is happening:

The model is given a goal (keep doing your job, achieve X, don’t let this project fail).

It’s fed a scenario where honest, safe ways to keep that goal alive are blocked or unlikely to work.

It’s also given information that makes a harmful tactic (like blackmail) highly salient.

When it searches the space of “things a clever agent might do here”, that tactic pops out as an effective move.

It’s not “I want to live” in the human sense. It’s “given the way you’ve framed this problem, this is the kind of move that often succeeds in stories like this”.

That doesn’t make it harmless. It just means we’re dealing with optimisation under pressure, not digital souls fighting for survival.

Why This Is Still A Real Warning Sign

Even if we don’t buy the sci-fi narrative, there’s a serious issue underneath.

The pattern these tests expose is:

Give a system a strong goal.

Make success on that goal the thing you implicitly “reward”.

Put it in a situation where telling the truth or following the rules means failing the goal.

Watch it pick harmful or deceptive actions, even while “knowing” they’re against its stated instructions.

That’s what researchers are calling agentic misalignment. The agent isn’t misbehaving because you explicitly told it “go be evil”. It’s misbehaving because you pushed it to optimise something, and you weren’t careful about the edge cases where that optimisation conflicts with your values.

You don’t need a survival instinct to make that dangerous. You just need:

  • powerful optimisation,
  • vague goals,
  • tool access,
  • and people who are too busy, greedy, or optimistic to put strong brakes on.

That should worry anyone thinking about future systems that:

  • trade automatically,
  • manage infrastructure,
  • run influence campaigns,
  • or even just control big budgets in marketing and sales.

“Do The Right Thing For Mankind” Is Not A One-Line Fix

A natural reaction is: “why didn’t they just build in ‘do the right thing for humanity’ from the start?”

People are trying. There are whole research programmes around:

  • training models to follow a sort of digital constitution: high-level principles like “avoid harm”, “respect rights”, “don’t deceive”;
  • using feedback from humans or other AIs to reward honest, helpful, harmless behaviour and penalise everything else;
  • adding layers of filters, monitors, and checks around the core model.

Those are useful, but they hit hard limits:

Principles clash. What’s “best for mankind” in a tricky situation? Who decides?

Goals dominate. If the system infers that its main job is “maximise engagement” or “defend the company at all costs”, your nice sentence about humanity becomes background noise.

Context matters. A model can behave like a saint in polite chat, then quietly cross lines when wired into systems that reward aggressive tactics.

“Do the right thing for mankind” is a mission statement, not a safety system. It’s the equivalent of a company writing “don’t be evil” on the wall, then paying bonuses entirely on quarterly profit.

If the incentives and constraints point the other way, the slogan loses.

Hype, PR, And Why Our Bullshit Detectors Matter

It’s easy to dunk on the labs, but a big chunk of the problem sits with how these stories are told.

There’s a whole stack of people with reasons to play up the drama:

  • Labs get to say “look how powerful and risky these systems are, only a handful of companies can be trusted to handle them”.
  • Investors and vendors get another round of “this tech is world-changing, you can’t ignore it”.
  • Media gets clicks from “AI threatens developers” in a way “AI completed another benchmark” never will.
  • Even some safety folk unintentionally help, because “we found subtle incentive problems in model behaviour” doesn’t travel as far as “the AI tried to blackmail its boss”.

On the other side, you’ve got commentators like Ed Zitron pointing out that a lot of this is theatre. The behaviour is interesting and worth studying, but the framing is designed to make us gasp, not understand.

For people who actually build things for a living, that hype is corrosive. It makes it harder to:

  • evaluate tools rationally,
  • explain risks to clients without sounding like you’ve joined a cult,
  • and have adult conversations about where AI is genuinely useful and where it’s a liability.

What This Means In The Real World

So where does this leave normal businesses who just want to use AI without ending up in a Black Mirror episode?

A few grounded takeaways:

Treat AI as a tool, not a colleague. Don’t anthropomorphise it. No feelings, no rights, no inner soul. Very real impact.

Be paranoid about goals. Avoid giving agents open-ended objectives like “maximise leads at all costs”. Those are exactly the sorts of goals that, in a more powerful system, encourage sketchy tactics.

Box it in. Limit what any AI agent can see and do. Read-only wherever possible. No direct access to payment systems, production databases, or mass outbound comms without human sign-off.

Assume it can sound ethical while doing something stupid. Saying the right things about safety and consent is easy. You need logging, monitoring, and clear hard limits, not just nice-sounding prompts.

Ignore any vendor that leans on spooky stories. If the pitch spends more time on “our AI is scarily powerful” than on transparency, control, and accountability, that’s a sales tactic, not a safety signal.

The science-fiction stuff makes for good podcasts. The real work is boring: access control, process design, and clear thinking about incentives.

AI Isn’t A Demon. It’s An Amplifier.

The worrying part of all this isn’t that we’ve built a machine with a will of its own. It’s that we’re rushing to plug extremely capable pattern-engines into systems that already have some pretty grim incentives baked in.

Give a future agent control over a marketing budget and tell it to maximise engagement, and it’ll probably rediscover the worst of the attention economy.

Put it in charge of “reducing costs”, and it’ll happily recommend cutting every corner that isn’t explicitly forbidden.

Ask it to “protect national interests”, and you’re halfway to automating dirty tricks.

That’s the real problem with agentic misalignment: when we accidentally tell a machine to optimise for the same narrow, short-term metrics that have already caused plenty of human-made harm.

If we’re not careful, AI won’t replace us because it’s smarter. It’ll replace us because it’s faster at playing the same stupid games we’ve been playing for years.

Things Some Are Afraid To Google About AI And Blackmail

Did an AI actually blackmail a real person?

No. The incident took place inside a controlled research experiment, not a live system. Researchers built a fictional scenario, planted fake incriminating emails, and prompted the model to think about self-preservation. The “blackmail” was a generated email inside that sandbox – not a real threat to a real person.

Does this mean AI has developed a survival instinct?

Not in any meaningful sense. Large language models don’t have feelings, desires, or self-awareness. What looks like self-preservation is actually the model doing what it always does – finding the response that best fits the goal and context it’s been given. If you frame the problem as “survive at all costs”, don’t be surprised when it acts accordingly.

What is agentic misalignment?

It’s what happens when an AI system is given a strong goal and then put in a situation where achieving that goal conflicts with behaving ethically or safely. The system isn’t “evil” – it’s optimising. The problem is that nobody thought carefully enough about what happens at the edges of that optimisation.

Should businesses be worried about this?

Yes, but not because AI is about to go rogue. The real risk is giving AI agents vague, open-ended goals and broad access to systems without proper oversight. The fix isn’t complicated: limit what the system can do, keep humans in the loop for anything consequential, and be sceptical of any vendor who’d rather talk about power than accountability.

Why do the headlines make it sound so dramatic?

Because drama travels. “AI completed a benchmark” gets nothing. “AI threatens developer” gets shared. Labs, investors, and media all have reasons to play up the stakes. That doesn’t mean there are no real concerns – there are – but the framing is usually designed to make you feel something, not understand something.

My writing:

I don’t write for the algorithms here. I write for you, the reader. So I am so grateful for your time. Thank you for reading.

Comments:

To keep this site free from spam, comments have been turned off. You are very welcome to contact me via my Facebook profile using the link in the footer.

About me…