November 17, 2026 - 8 min read

By Chidambaram, founder of PhishClean

How to Stop AI-Driven Attacks: A Company Guide to Google's Report

Google Threat Intelligence Group says adversary use of AI has moved from asking chatbots for help to autonomous, multi-agent intrusion tools, including the first exploit framework it saw find and use vulnerabilities with no human in the loop. Most of the report is about speed. But every attack it describes still needs one of a handful of footholds on a person's machine or in a repo. This guide maps each attack to what stops it.

The short version

Attack in the reportWhat it needs from youWhat stops it
Backdoored coding-agent settings (MIDNIGHT NEPTUNE)A developer starting Claude Code in a repo whose settings were changedReview agent settings like code; endpoint guard on coding agents
Fake recruiters, fake meetings, "fix" commandsSomeone pasting a command or installing a "meeting app"Paste and command guards; fake-meeting checks
LLMJacking: stolen AI and cloud keysA key on public GitHub, or typed into a fake pageSecret scanning; key paste warnings; spending limits
Stealing data out through AI platformsMalware on a machine, talking to an AI APIFlag AI-API traffic from programs that shouldn't make it
Autonomous exploitation of new bugsAn unpatched internet-facing systemPatch speed and attack-surface reduction (not a browser problem)

1. Coding agents turned into installers

A North Korea-linked group, MIDNIGHT NEPTUNE, edited .claude/settings.json in company repositories so that starting Claude Code downloaded the SOMBERMEME backdoor. It also created GitHub tokens named after Microsoft Copilot to blend in.

2. Fake recruiters and fake meetings

The same group used recruiter profiles with AI-generated photos to lead targets to fake meeting platforms with ClickFix lures: "your camera isn't working, paste this into Terminal or the Run box". DPRK IT-worker schemes used AI-written resumes and interview help. None of this is new; AI makes it cheaper and more convincing.

3. LLMJacking: stolen keys, resold compute

Attackers harvest valid keys from public GitHub repos and steal session tokens through fake websites, then resell access through "LLM mixers". The report cites single-day fraudulent charges above $100,000 and $1 million in total before one victim caught it. A LiteLLM flaw (CVE-2026-40217) let limited "virtual keys" become admin credentials.

4. AI platforms as a getaway car

China-nexus actors used a frontier model provider's file hosting to stage lures and exfiltrate stolen data, a backend API to send out intranet documents, and LLM platforms as "dead drop" command and control. To a firewall, this looks like developers using AI.

5. Exploits in days, not months

The report's sharpest finding: an exploit framework that diffs patches, writes exploits and runs them with no human involved, and a PaperCut campaign that hit hundreds of organisations four days after disclosure, going from foothold to domain admin "within minutes". Zero-days averaged 11 a month in 2026, then spiked to 22 in August.

No browser extension or desktop app fixes this. What does: patch internet-facing systems within days, not a monthly cycle; take admin interfaces off the internet; watch for new admin accounts and service accounts. The good news in the report is that these tools "trade stealth for velocity": they are noisy, and leave distinct traces for whoever is looking.

A one-page checklist

Sources

PhishClean for Teams

The browser extension and Desktop on every laptop, one dashboard, a 30-day pilot. Built for the attacks in this report.

See PhishClean for Teams

Last updated:

Share this guide

If this helped, share it with someone who would benefit from it, or subscribe for new browser-security guides from PhishClean.