---
title: Hunt: how to spot ARTEX and other AI pentest agents by behavior, from Unit 42's intrusion cases | ctxsec
url: https://ctxsec.com/items/hunt-unit42-artex-ai-red-team-framework-behavioral-hallmarks-password-reset-cloud
description: "Unit 42 says attackers are using open-source AI red-team frameworks such as ARTEX and CyberStrikeAI in real intrusions, turning public password-reset pages and exposed APIs into cloud access, sometimes in under a day and without exploiting a software vulnerability. As of October it counted 609 internet-facing ARTEX hosts and 1,323 running CyberStrikeAI. Because ARTEX is widely forked and infrastructure rotates, Unit 42 recommends detecting the operator's behavior rather than relying on indicators."
status: "vendor research (Palo Alto Networks Unit 42, Nov 11, 2026)"
published: 2026-11-11
---

> Unit 42 says attackers are using open-source AI red-team frameworks such as ARTEX and CyberStrikeAI in real intrusions, turning public password-reset pages and exposed APIs into cloud access, sometimes in under a day and without exploiting a software vulnerability. As of October it counted 609 internet-facing ARTEX hosts and 1,323 running CyberStrikeAI. Because ARTEX is widely forked and infrastructure rotates, Unit 42 recommends detecting the operator's behavior rather than relying on indicators.

[← Threat Hunting](/hunting) · [markdown](/items/hunt-unit42-artex-ai-red-team-framework-behavioral-hallmarks-password-reset-cloud.md)

vendor research (Palo Alto Networks Unit 42, Nov 11, 2026)

2026-11-11 7:41 PM ET

### Hunt: how to spot ARTEX and other AI pentest agents by behavior, from Unit 42's intrusion cases

- **Think-then-act cadence:** bursts of 1 to 14 requests about a second apart, then 25 to 31 second pauses (waiting on model inference).
- **Machine speed:** pivots within about a minute of a credential download; 200+ client secrets validated in about three minutes.
- **Spec-driven:** routes from downloaded OpenAPI specs and source maps hit almost immediately; failed HTTP 422 requests fixed and retried moments later.
- **Self-checks and canaries:** a GET after nearly every successful write, write-then-delete tests on storage buckets, bogus usernames before real ones, placeholders like `evil[.]com`, `test@example[.]com`, `deadbeefdeadbeefdeadbeef12`.
- **Breadth and loops:** ADC, a dozen VPN appliances, NAS, workforce identity and cloud ports hit within the same hour; polling every 48 seconds for days.
- **Fixes Unit 42 lists:** pull OpenAPI specs, source maps and token-bearing config off public apps; require auth on every write endpoint including dev and staging; rate-limit and bot-protect registration and password reset; never let a reset unlink a federated identity; replace long-lived cloud keys with roles.

Sources: [Unit 42: ARTEX and AI-Powered Red Teaming Tools: What Defenders Need to Know (Nov 11, 2026)](https://unit42.paloaltonetworks.com/artex-and-ai-powered-red-teaming-tools/)