The FBI on Nov. 13 sent out a FLASH advisory warning security teams that threat actors have used the AI-based penetration testing tool Artex to launch multiple malicious campaigns since at least August 2026.
The Artex attacks raised eyebrows at the FBI and throughout the industry because some intrusions progressed from initial targeting to privileged access in under three hours.
Attacks have been launched across multiple sectors globally, including the financial services, government, technology, defense, semiconductor, energy, healthcare, manufacturing, telecommunications, and legal industries.
According to the FBI, notable campaigns include financially motivated attacks against South Korean financial institutions resulting in exfiltration of personal information from approximately 67,000 individuals, and a supply chain compromise affecting ConnectWise Cloud Backup customers that allowed access to more than 2,250 downstream tenants.
Morey J. Haber, chief security advisor at BeyondTrust, said while information security teams have always raced the clock for vulnerability detection and remediation, the tempo has changed in the case of Artex threat actors.
“When an AI-driven framework chains reconnaissance, exploitation, and privilege escalation in under a few hours, the threat actor no longer must be skilled,” said Haber. “They only have to be pointed in the right direction using a toolkit pretuned for their nefarious activities.”
Adrian Culley, offensive security engineer at SafeBreach, pointed out that what’s notable about ARTEX isn’t the AI — it’s that the tradecraft is ordinary. Culley said SAML forgery, XXE, SSRF, Kerberoasting and DCSync are all well-worn techniques, and the framework chains them without a human at the keyboard.
“The FBI’s reporting of intrusions reaching privileged access in under three hours is a best case, but the direction is clear: the time between first foothold and domain-level impact is collapsing, so be clear that the ARTEX Genie will not be going back into its bottle any time soon,” said Culley. “That matters because most defenses were sized for an operator who sleeps, hesitates, and works one target at a time. An agent doesn’t. It enumerates an entire directory, finds the hosts without endpoint protection, and routes around the ones that have it. Cheap, lightly guardrailed models make this affordable for low-skilled actors, so the capability is now broadly available.”
Bashar Abouseido, president of Tenex.al, added that defenders do not need an exotic new tool as a starting point: they just need the controls they already own to be complete, connected, and fast.
In a Nov. 16 blog, Abousedio lays out seven steps teams can take to mitigae Artex-based threat:
- Harden every internet-facing asset: Especially secondary login portals and mobile app backends. Rate-limit and alert on bulk record lookups.
- Know the company’s vendor applications: Inventory every multi-tenant and partner application with a foothold in the organization’s tenant, what it can do, and what the team would do if its credentials were stolen. The October victims did nothing wrong inside their own tenants.
- Govern and baseline every identity, human and non-human: That means cloud applications, service accounts, service principals, IoT and machine identities. Limit who can grant application permissions, alert on new application credentials and admin role changes, and record how each identity normally behaves so departures stand out.
- Close the telemetry blind spots: Get logs from applications, servers, network devices, endpoints, security consoles and identity systems into one place, and keep constant watch on the crown-jewel applications and services. Agentic attackers look for the gaps across the stack and go there first.
- Automate containment within agreed authority: Disable accounts, revoke tokens and isolate hosts in minutes when a spray burst, an unusual run of application sign-ins or a web shell appears. A person defines the authority; the response runs at machine speed inside it.
- Retire stale secrets: Remove long-lived keys and VPN credentials or, at minimum, rotate them, review secrets with far-out expiry dates, and watch public code and breach dumps for leaks.
- Test like the attacker: Have a qualified red team run authorized AI-driven testing against the company’s own systems, in an isolated environment with no production credentials.