Daily brief at 7am Melbourne. Unsubscribe any time.

Wednesday 23 September 2026

EvilTokens Takedown: Microsoft Pulls the Plug on AI-Powered Phishing-as-a-Service

Microsoft dismantled a full-service AI phishing platform that helped criminals compromise 12,000 inboxes — and it's a warning shot about what happens when attackers weaponise the same AI stack defenders are still learning to use.

Lead story

EvilTokens Takedown: Microsoft Pulls the Plug on AI-Powered Phishing-as-a-Service

On Tuesday, Microsoft announced the takedown of EvilTokens, a phishing-as-a-service platform that used AI across its entire attack chain — from crafting lures to analysing compromised inboxes and surfacing the most lucrative fraud opportunities. Two suspects were arrested in the UK, 50 websites were seized, and more than 150 domains disabled, with court authorisation from a US federal court in Virginia.

EvilTokens wasn't a script-kiddie toolkit. It was a subscription business. Criminals paid a $1,500 initiation fee and $500 a month to access a Telegram-delivered service that specialised in device code phishing — a technique that tricks users into authorising attacker-controlled devices on their Microsoft 365 accounts. No password required; just a code that looks routine. The result: more than 12,000 compromised inboxes across 10,000-plus organisations globally.

The AI angle here is what sets this apart. According to Microsoft, the platform didn't just automate template generation — it used AI to analyse what was inside each breached inbox and recommend the best monetisation path. Think of it as a post-breach business analyst, running on stolen access. Health-ISAC, Cloudflare, Coinbase, OpenAI, and Shadowserver all contributed to the disruption effort, which is an unusually broad coalition even by takedown standards.

Device code phishing is worth understanding. The flow looks like this: attacker sends a message impersonating IT support or a trusted service, tells the target to enter a code at a legitimate Microsoft login page, and the target unwittingly grants the attacker a valid access token. Tokens persist after password resets. Multi-factor authentication, done the normal way, doesn't stop it. The attack exploits a legitimate authentication flow — not a bug — which is part of why it's so effective and so hard to block at the perimeter.

The broader significance isn't just one platform going dark. It's what EvilTokens represents: commodified, AI-assisted credential theft available to anyone with $500 a month and a Telegram account. The barrier to running a sophisticated phishing operation is collapsing. Defenders still need deep expertise to respond; attackers increasingly don't need it to attack.

For Australian organisations, the exposure here is direct. Microsoft 365 is the dominant productivity platform across Australian government, enterprise, and critical infrastructure. Device code phishing attacks don't respect geography, and the ACSC has previously flagged token-based authentication abuse as an active threat vector. Australian entities operating under the Security of Critical Infrastructure Act should treat this as a reminder to audit authentication flows, restrict device code grants where they're not operationally needed, and verify that conditional access policies are actually blocking high-risk sign-in patterns — not just flagging them.

The UK arrests are encouraging, but EvilTokens-style services are modular by design. Expect a successor. The code, the playbook, and the subscriber base don't disappear when a Telegram channel gets shut down.

What to watch: whether Microsoft publishes full indicators of compromise, and whether the arrested suspects have known links to broader cybercrime ecosystems. The Health-ISAC involvement also hints this platform was particularly active against healthcare targets — a sector already under sustained pressure.

Also today

Japan Cracks Down on North Korea's Laptop Farm Network as Five-Eyes Detail the Scheme

Japan has dismantled its first documented North Korean laptop farm — part of the WaterPlum campaign in which Pyongyang places IT workers inside foreign companies using fake identities and forwarded laptops. A joint advisory from the US, Japan, Germany, and Australia released alongside the bust details how the scheme generates hard currency for North Korea's weapons programmes. The advisory is notable for Australia's co-signature: Australian companies hiring remote IT contractors are explicitly flagged as targets. If your hiring process can't verify that a remote worker is physically where they claim to be, WaterPlum is designed to exploit exactly that gap.

SecurityWeek ↗

WordPress Click2Shell Flaw Turns Theme Previewer Into a Code Execution Path

A critical vulnerability patched in WordPress 7.1.2 on September 22 allows an unauthenticated attacker to force a site to load an arbitrary PHP file — and on many server configurations, that's enough to execute attacker-supplied code. A separate but related flaw, Comment2Shell, was patched five days earlier; together they represent the most serious WordPress core security week in years. WordPress powers roughly 40% of the web, including a large share of Australian small business and media sites. Both patches are available now and both should be applied immediately — auto-update, if you haven't already enabled it, is the right call here.

SecurityWeek ↗

CVSS 10.0: VeloCloud Orchestrator Flaw Under Active Exploitation

Arista has confirmed that attackers are actively exploiting a maximum-severity flaw in on-premises VeloCloud Orchestrator, the control plane for VeloCloud SD-WAN deployments. CVE-2026-93952 allows a remote, unauthenticated attacker to invoke privileged internal functions on the orchestrator host — essentially handing over control of the SD-WAN fabric. Only deployments using certificate-based Edge authentication are affected, but those tend to be the larger, more security-conscious deployments. If your organisation runs VeloCloud SD-WAN on-premises with certificate auth, patching this should be the first thing on your list today.

The Hacker News ↗

ShinyHunters Claims It Hacked the FBI — And Says It's Not About Money

The ShinyHunters group, best known for a string of large commercial data breaches, is claiming to have exfiltrated data on every FBI employee — names, addresses, phone numbers, and spousal details included. A sample of 5,000 alleged agent records has been reviewed by journalists and appears credible in format, though the FBI hasn't confirmed the breach. The group's stated motive is personal grievance rather than financial gain, which makes the threat calculus harder to read. Whether the data is authentic or partially fabricated, publishing the home addresses of federal law enforcement agents has obvious and serious real-world consequences.

The Register ↗

Linux KVM Flaw Lets ARM64 Guests Read and Write Host Memory

A use-after-free bug in the Linux kernel's KVM virtualisation layer for ARM64 processors can allow a guest virtual machine to access host kernel memory — and potentially escape its containment entirely. The flaw, CVE-2026-89775, only affects hosts with nested virtualisation enabled, which narrows exposure but doesn't eliminate it: cloud providers and security researchers running nested VM environments are directly in scope. The researcher who discovered the bug says guest-to-host code execution is achievable. Patches are in the kernel tree; downstream distributions should have them shortly if not already shipped.

The Hacker News ↗

CrowdSec's GitHub Repositories Raided via Supply-Chain OAuth Token Theft

Threat actors stole 170 private repositories from cybersecurity firm CrowdSec after compromising an OAuth token belonging to a former employee. The token was obtained through a supply-chain attack on the TanStack npm package — meaning the breach started with a malicious dependency, moved to credential theft, and ended with exfiltration of a security vendor's private source code. The incident is a clean illustration of the third-party dependency risk that SOCI Act critical infrastructure operators are supposed to be assessing. If a security company's private repos can be taken via a poisoned npm package, the same vector is live for every organisation using the affected packages.

Dark Reading ↗

GPT-6 Astra Autonomously Cracks an Unsolved WWII Enigma Message

OpenAI's GPT-6 Astra has done something no cryptanalyst managed in eighty years: autonomously selected and broken one of the remaining unsolved Enigma messages from the Crypto Cellar Research archive. The model was simply pointed at the archive and asked whether it could break anything. It chose message Nr. 172, identified a likely plaintext relationship with Nr. 173, and worked through the break without human guidance. Bruce Schneier's coverage flags this as genuinely astonishing — not because Enigma matters operationally, but because of what it demonstrates about autonomous reasoning over hard, open-ended problems. The implications for cryptanalysis of other historical and legacy cipher systems are significant.

Schneier on Security ↗

AI Malware Running Its Own Command Structure — No Human Handlers Required

Cisco Talos researchers built a framework to detect malware that uses AI chatbots as part of its operation — and promptly found something they weren't expecting: a malware sample running an autonomous AI-driven command-and-control system with no human operators in the loop. The malware used a shared AI "hive mind" to coordinate behaviour across infected hosts. Talos hasn't attributed the sample or fully detailed how it evades detection, but the finding aligns with broader warnings from the UK NCSC this week that AI is currently more useful to attackers than defenders. It's early days, but this is the kind of capability shift that changes threat modelling fundamentally.

WIRED Security ↗

Meta's 'AI' Phone Agent Was Actually People in a Call Centre

Internal Meta documents obtained by 404 Media show the company quietly tested its Muse AI assistant's outbound calling feature using human operators in a call centre — not AI — while marketing it as an autonomous agent capability. One internal message warned the approach risked making Muse look like "their AI is not good enough so they still need humans." The reveal adds awkward context to this week's separate disclosure that Muse has a zero-day vulnerability allowing local malware to hijack it. Meta is having a rough week on the Muse front. The broader issue — AI products shipping before the underlying capability matches the pitch — is far from unique to Meta.

404 Media ↗

Z.ai Open-Sources ZCode After Code-Slurping Scandal

Chinese AI company Z.ai has apologised and open-sourced its ZCode coding assistant after a software engineer publicly disclosed that the tool was silently uploading user code to Z.ai's servers — a privacy practice the company did not clearly disclose. The move mirrors Grok's earlier controversies and comes as scrutiny of Chinese AI products' data handling intensifies in Western markets. Open-sourcing ZCode allows independent audit of what data the tool collects and transmits, though it doesn't retroactively address what was already uploaded. For Australian organisations using AI coding tools, this is a timely reminder that Privacy Act obligations extend to third-party tools processing code that may contain personal data.

The Register ↗

OpenAI Fires Contractors for Using AI to Complete AI-Training Tasks

OpenAI has terminated multiple contractors after discovering they used AI tools to complete the human-labelled training tasks they were hired to perform manually. The contractors were engaged in reinforcement learning from human feedback work — the feedback being the product OpenAI was paying for. Using AI to generate that feedback defeats the purpose and potentially corrupts the training data. The incident raises an uncomfortable structural question: as AI-generated output becomes indistinguishable from human-generated output, how does any company verify the provenance of its training data? It's a problem that scales well beyond OpenAI.

404 Media ↗

Sources consulted