Skip to content
An AI-Assisted Cyber Attack: Inside a Unit 42 Investigation | Wendi Whitmore

An AI-Assisted Cyber Attack: Inside a Unit 42 Investigation | Wendi Whitmore

Linkedin • September 2, 2026

investigated a break-in this month that was over in less than ten hours. The same work would have taken a skilled human team roughly two weeks.

A single attacker found an opening in a public-facing application and got inside. From there, they did not do any manual work themselves. They pointed AI agents at the problem and let them run.

The agents systematically mapped the company's internal systems. They read through the company's own source code, hunting for passwords and keys developers had left behind, and they found them. Those keys opened the vault where the company stored its most sensitive credentials, and from that point forward the attacker had free rein.

Then came a new twist. The agents took the keys to the company's own AI systems and used them to power the rest of the attack. The victim's technology ran the intrusion, and the victim paid the compute bill for the privilege.

The attacker's parting move was to instruct the AI to generate an 80-page report on everything wrong with the company's security and leave it behind.

One control did hold. When the agents tried to bury a backdoor in the company's infrastructure code, a rule requiring human review blocked it. Good controls still work. What has to change is that they can no longer depend on someone noticing in time.

For executive leaders reading this: the response window we used to plan against was measured in days. This incident argues that window is now measured in hours. That single shift changes what "prepared" actually looks like across most enterprise environments.

Three questions worth putting to your security leader this quarter.

Do we know where every AI system, key, and connection in our environment actually lives, and who has access to use them?

If we found an intruder in our environment right now, how do we contain them & how do we prevent their access to our AI systems?

Are we running AI to hunt through our code for exposed secrets, embedded credentials, and vulnerabilities, before attackers point their agents at the same targets?