Swarm Chasing: Hunting ARTEX and Other Agentic Offensive Frameworks in the Wild

We found 47 ARTEX variants, 2,335 exposed offensive AI consoles and three undocumented offensive AI agent tools, using 24 detection and fingerprinting methods.

21 min read
Delta Team
Delta TeamLinkedIn

Lately, all we've been hearing about is AI attack tools. ARTEX, Cairn, PentAGI and CyberStrikeAI are open-source AI pentest tools, and all four have now turned up in real attacks. ARTEX was used to steal data from South Korean financial organizations20 and against AWS accounts.27 Storm-0940, a China-state-aligned group, used it after compromising a ConnectWise cloud backup app,21 and VAPOR PANDA used it against foreign ministries and telecoms.23 A China-nexus group ran a customized fork of Cairn against at least 19 organizations,28 Google saw PentAGI aimed at the aerospace sector,24 and Kaspersky found CyberStrikeAI in attacks on education organizations.25

Every one of these tools is run from a web console, and operators often leave that console open on the internet. So we asked: how many are out there, and what's actually running behind them?

To find out, we read each tool's source code in an isolated sandbox, pulled out fingerprints that survive renaming, and searched public scan data.

Consoles deployed over timeCumulative consoles by TLS certificate date · 1 Sep → 15 Nov 2026
010020030040009/0109/1509/2910/1310/2711/15PentAGI 3982026-09-01: PentAGI, 250 consoles2026-09-02: PentAGI, 251 consoles2026-09-03: PentAGI, 255 consoles2026-09-04: PentAGI, 255 consoles2026-09-05: PentAGI, 256 consoles2026-09-06: PentAGI, 257 consoles2026-09-07: PentAGI, 258 consoles2026-09-08: PentAGI, 260 consoles2026-09-09: PentAGI, 261 consoles2026-09-10: PentAGI, 263 consoles2026-09-11: PentAGI, 266 consoles2026-09-12: PentAGI, 267 consoles2026-09-13: PentAGI, 267 consoles2026-09-14: PentAGI, 269 consoles2026-09-15: PentAGI, 270 consoles2026-09-16: PentAGI, 271 consoles2026-09-17: PentAGI, 273 consoles2026-09-18: PentAGI, 274 consoles2026-09-19: PentAGI, 275 consoles2026-09-20: PentAGI, 277 consoles2026-09-21: PentAGI, 277 consoles2026-09-22: PentAGI, 280 consoles2026-09-23: PentAGI, 282 consoles2026-09-24: PentAGI, 284 consoles2026-09-25: PentAGI, 285 consoles2026-09-26: PentAGI, 286 consoles2026-09-27: PentAGI, 286 consoles2026-09-28: PentAGI, 287 consoles2026-09-29: PentAGI, 291 consoles2026-09-30: PentAGI, 294 consoles2026-10-01: PentAGI, 298 consoles2026-10-02: PentAGI, 300 consoles2026-10-03: PentAGI, 305 consoles2026-10-04: PentAGI, 305 consoles2026-10-05: PentAGI, 312 consoles2026-10-06: PentAGI, 314 consoles2026-10-07: PentAGI, 316 consoles2026-10-08: PentAGI, 319 consoles2026-10-09: PentAGI, 319 consoles2026-10-10: PentAGI, 325 consoles2026-10-11: PentAGI, 325 consoles2026-10-12: PentAGI, 333 consoles2026-10-13: PentAGI, 340 consoles2026-10-14: PentAGI, 347 consoles2026-10-15: PentAGI, 353 consoles2026-10-16: PentAGI, 358 consoles2026-10-17: PentAGI, 364 consoles2026-10-18: PentAGI, 367 consoles2026-10-19: PentAGI, 374 consoles2026-10-20: PentAGI, 378 consoles2026-10-21: PentAGI, 379 consoles2026-10-22: PentAGI, 382 consoles2026-10-23: PentAGI, 383 consoles2026-10-24: PentAGI, 384 consoles2026-10-25: PentAGI, 387 consoles2026-10-26: PentAGI, 389 consoles2026-10-27: PentAGI, 391 consoles2026-10-28: PentAGI, 393 consoles2026-10-29: PentAGI, 395 consoles2026-10-30: PentAGI, 396 consoles2026-10-31: PentAGI, 396 consoles2026-11-01: PentAGI, 398 consoles2026-11-02: PentAGI, 398 consoles2026-11-03: PentAGI, 398 consoles2026-11-04: PentAGI, 398 consoles2026-11-05: PentAGI, 398 consoles2026-11-06: PentAGI, 398 consoles2026-11-07: PentAGI, 398 consoles2026-11-08: PentAGI, 398 consoles2026-11-09: PentAGI, 398 consoles2026-11-10: PentAGI, 398 consoles2026-11-11: PentAGI, 398 consoles2026-11-12: PentAGI, 398 consoles2026-11-13: PentAGI, 398 consoles2026-11-14: PentAGI, 398 consoles2026-11-15: PentAGI, 398 consolesARTEX 2022026-09-01: ARTEX family, 10 consoles2026-09-02: ARTEX family, 10 consoles2026-09-03: ARTEX family, 10 consoles2026-09-04: ARTEX family, 10 consoles2026-09-05: ARTEX family, 10 consoles2026-09-06: ARTEX family, 11 consoles2026-09-07: ARTEX family, 11 consoles2026-09-08: ARTEX family, 11 consoles2026-09-09: ARTEX family, 11 consoles2026-09-10: ARTEX family, 13 consoles2026-09-11: ARTEX family, 13 consoles2026-09-12: ARTEX family, 13 consoles2026-09-13: ARTEX family, 13 consoles2026-09-14: ARTEX family, 13 consoles2026-09-15: ARTEX family, 13 consoles2026-09-16: ARTEX family, 14 consoles2026-09-17: ARTEX family, 14 consoles2026-09-18: ARTEX family, 14 consoles2026-09-19: ARTEX family, 14 consoles2026-09-20: ARTEX family, 15 consoles2026-09-21: ARTEX family, 15 consoles2026-09-22: ARTEX family, 15 consoles2026-09-23: ARTEX family, 16 consoles2026-09-24: ARTEX family, 17 consoles2026-09-25: ARTEX family, 17 consoles2026-09-26: ARTEX family, 17 consoles2026-09-27: ARTEX family, 17 consoles2026-09-28: ARTEX family, 18 consoles2026-09-29: ARTEX family, 18 consoles2026-09-30: ARTEX family, 19 consoles2026-10-01: ARTEX family, 19 consoles2026-10-02: ARTEX family, 19 consoles2026-10-03: ARTEX family, 22 consoles2026-10-04: ARTEX family, 22 consoles2026-10-05: ARTEX family, 23 consoles2026-10-06: ARTEX family, 23 consoles2026-10-07: ARTEX family, 25 consoles2026-10-08: ARTEX family, 28 consoles2026-10-09: ARTEX family, 37 consoles2026-10-10: ARTEX family, 41 consoles2026-10-11: ARTEX family, 47 consoles2026-10-12: ARTEX family, 50 consoles2026-10-13: ARTEX family, 53 consoles2026-10-14: ARTEX family, 64 consoles2026-10-15: ARTEX family, 68 consoles2026-10-16: ARTEX family, 72 consoles2026-10-17: ARTEX family, 74 consoles2026-10-18: ARTEX family, 83 consoles2026-10-19: ARTEX family, 88 consoles2026-10-20: ARTEX family, 95 consoles2026-10-21: ARTEX family, 96 consoles2026-10-22: ARTEX family, 106 consoles2026-10-23: ARTEX family, 116 consoles2026-10-24: ARTEX family, 121 consoles2026-10-25: ARTEX family, 131 consoles2026-10-26: ARTEX family, 134 consoles2026-10-27: ARTEX family, 142 consoles2026-10-28: ARTEX family, 150 consoles2026-10-29: ARTEX family, 160 consoles2026-10-30: ARTEX family, 163 consoles2026-10-31: ARTEX family, 170 consoles2026-11-01: ARTEX family, 173 consoles2026-11-02: ARTEX family, 178 consoles2026-11-03: ARTEX family, 188 consoles2026-11-04: ARTEX family, 195 consoles2026-11-05: ARTEX family, 196 consoles2026-11-06: ARTEX family, 202 consoles2026-11-07: ARTEX family, 202 consoles2026-11-08: ARTEX family, 202 consoles2026-11-09: ARTEX family, 202 consoles2026-11-10: ARTEX family, 202 consoles2026-11-11: ARTEX family, 202 consoles2026-11-12: ARTEX family, 202 consoles2026-11-13: ARTEX family, 202 consoles2026-11-14: ARTEX family, 202 consoles2026-11-15: ARTEX family, 202 consoles2026-09-01: Agent Zero, 12 consoles2026-09-02: Agent Zero, 13 consoles2026-09-03: Agent Zero, 13 consoles2026-09-04: Agent Zero, 13 consoles2026-09-05: Agent Zero, 14 consoles2026-09-06: Agent Zero, 15 consoles2026-09-07: Agent Zero, 15 consoles2026-09-08: Agent Zero, 15 consoles2026-09-09: Agent Zero, 16 consoles2026-09-10: Agent Zero, 17 consoles2026-09-11: Agent Zero, 17 consoles2026-09-12: Agent Zero, 17 consoles2026-09-13: Agent Zero, 17 consoles2026-09-14: Agent Zero, 17 consoles2026-09-15: Agent Zero, 17 consoles2026-09-16: Agent Zero, 17 consoles2026-09-17: Agent Zero, 17 consoles2026-09-18: Agent Zero, 17 consoles2026-09-19: Agent Zero, 18 consoles2026-09-20: Agent Zero, 18 consoles2026-09-21: Agent Zero, 19 consoles2026-09-22: Agent Zero, 20 consoles2026-09-23: Agent Zero, 20 consoles2026-09-24: Agent Zero, 20 consoles2026-09-25: Agent Zero, 20 consoles2026-09-26: Agent Zero, 20 consoles2026-09-27: Agent Zero, 22 consoles2026-09-28: Agent Zero, 22 consoles2026-09-29: Agent Zero, 23 consoles2026-09-30: Agent Zero, 23 consoles2026-10-01: Agent Zero, 23 consoles2026-10-02: Agent Zero, 23 consoles2026-10-03: Agent Zero, 23 consoles2026-10-04: Agent Zero, 23 consoles2026-10-05: Agent Zero, 24 consoles2026-10-06: Agent Zero, 26 consoles2026-10-07: Agent Zero, 27 consoles2026-10-08: Agent Zero, 27 consoles2026-10-09: Agent Zero, 27 consoles2026-10-10: Agent Zero, 27 consoles2026-10-11: Agent Zero, 27 consoles2026-10-12: Agent Zero, 29 consoles2026-10-13: Agent Zero, 30 consoles2026-10-14: Agent Zero, 31 consoles2026-10-15: Agent Zero, 31 consoles2026-10-16: Agent Zero, 33 consoles2026-10-17: Agent Zero, 34 consoles2026-10-18: Agent Zero, 35 consoles2026-10-19: Agent Zero, 35 consoles2026-10-20: Agent Zero, 35 consoles2026-10-21: Agent Zero, 35 consoles2026-10-22: Agent Zero, 35 consoles2026-10-23: Agent Zero, 35 consoles2026-10-24: Agent Zero, 36 consoles2026-10-25: Agent Zero, 37 consoles2026-10-26: Agent Zero, 37 consoles2026-10-27: Agent Zero, 40 consoles2026-10-28: Agent Zero, 41 consoles2026-10-29: Agent Zero, 41 consoles2026-10-30: Agent Zero, 41 consoles2026-10-31: Agent Zero, 42 consoles2026-11-01: Agent Zero, 42 consoles2026-11-02: Agent Zero, 42 consoles2026-11-03: Agent Zero, 44 consoles2026-11-04: Agent Zero, 44 consoles2026-11-05: Agent Zero, 45 consoles2026-11-06: Agent Zero, 45 consoles2026-11-07: Agent Zero, 45 consoles2026-11-08: Agent Zero, 46 consoles2026-11-09: Agent Zero, 46 consoles2026-11-10: Agent Zero, 46 consoles2026-11-11: Agent Zero, 46 consoles2026-11-12: Agent Zero, 46 consoles2026-11-13: Agent Zero, 46 consoles2026-11-14: Agent Zero, 46 consoles2026-11-15: Agent Zero, 46 consolesCyberStrikeAI 152026-09-01: CyberStrikeAI, 0 consoles2026-09-02: CyberStrikeAI, 0 consoles2026-09-03: CyberStrikeAI, 0 consoles2026-09-04: CyberStrikeAI, 0 consoles2026-09-05: CyberStrikeAI, 0 consoles2026-09-06: CyberStrikeAI, 0 consoles2026-09-07: CyberStrikeAI, 0 consoles2026-09-08: CyberStrikeAI, 0 consoles2026-09-09: CyberStrikeAI, 0 consoles2026-09-10: CyberStrikeAI, 0 consoles2026-09-11: CyberStrikeAI, 0 consoles2026-09-12: CyberStrikeAI, 0 consoles2026-09-13: CyberStrikeAI, 0 consoles2026-09-14: CyberStrikeAI, 1 consoles2026-09-15: CyberStrikeAI, 1 consoles2026-09-16: CyberStrikeAI, 1 consoles2026-09-17: CyberStrikeAI, 1 consoles2026-09-18: CyberStrikeAI, 1 consoles2026-09-19: CyberStrikeAI, 1 consoles2026-09-20: CyberStrikeAI, 1 consoles2026-09-21: CyberStrikeAI, 1 consoles2026-09-22: CyberStrikeAI, 1 consoles2026-09-23: CyberStrikeAI, 1 consoles2026-09-24: CyberStrikeAI, 1 consoles2026-09-25: CyberStrikeAI, 1 consoles2026-09-26: CyberStrikeAI, 1 consoles2026-09-27: CyberStrikeAI, 1 consoles2026-09-28: CyberStrikeAI, 1 consoles2026-09-29: CyberStrikeAI, 1 consoles2026-09-30: CyberStrikeAI, 1 consoles2026-10-01: CyberStrikeAI, 1 consoles2026-10-02: CyberStrikeAI, 1 consoles2026-10-03: CyberStrikeAI, 1 consoles2026-10-04: CyberStrikeAI, 1 consoles2026-10-05: CyberStrikeAI, 1 consoles2026-10-06: CyberStrikeAI, 1 consoles2026-10-07: CyberStrikeAI, 1 consoles2026-10-08: CyberStrikeAI, 1 consoles2026-10-09: CyberStrikeAI, 1 consoles2026-10-10: CyberStrikeAI, 1 consoles2026-10-11: CyberStrikeAI, 2 consoles2026-10-12: CyberStrikeAI, 2 consoles2026-10-13: CyberStrikeAI, 2 consoles2026-10-14: CyberStrikeAI, 2 consoles2026-10-15: CyberStrikeAI, 2 consoles2026-10-16: CyberStrikeAI, 2 consoles2026-10-17: CyberStrikeAI, 2 consoles2026-10-18: CyberStrikeAI, 2 consoles2026-10-19: CyberStrikeAI, 2 consoles2026-10-20: CyberStrikeAI, 2 consoles2026-10-21: CyberStrikeAI, 2 consoles2026-10-22: CyberStrikeAI, 2 consoles2026-10-23: CyberStrikeAI, 2 consoles2026-10-24: CyberStrikeAI, 2 consoles2026-10-25: CyberStrikeAI, 2 consoles2026-10-26: CyberStrikeAI, 2 consoles2026-10-27: CyberStrikeAI, 2 consoles2026-10-28: CyberStrikeAI, 2 consoles2026-10-29: CyberStrikeAI, 2 consoles2026-10-30: CyberStrikeAI, 2 consoles2026-10-31: CyberStrikeAI, 2 consoles2026-11-01: CyberStrikeAI, 3 consoles2026-11-02: CyberStrikeAI, 3 consoles2026-11-03: CyberStrikeAI, 3 consoles2026-11-04: CyberStrikeAI, 3 consoles2026-11-05: CyberStrikeAI, 3 consoles2026-11-06: CyberStrikeAI, 4 consoles2026-11-07: CyberStrikeAI, 6 consoles2026-11-08: CyberStrikeAI, 15 consoles2026-11-09: CyberStrikeAI, 15 consoles2026-11-10: CyberStrikeAI, 15 consoles2026-11-11: CyberStrikeAI, 15 consoles2026-11-12: CyberStrikeAI, 15 consoles2026-11-13: CyberStrikeAI, 15 consoles2026-11-14: CyberStrikeAI, 15 consoles2026-11-15: CyberStrikeAI, 15 consoles2026-09-01: RedAmon, 1 consoles2026-09-02: RedAmon, 1 consoles2026-09-03: RedAmon, 1 consoles2026-09-04: RedAmon, 1 consoles2026-09-05: RedAmon, 1 consoles2026-09-06: RedAmon, 1 consoles2026-09-07: RedAmon, 1 consoles2026-09-08: RedAmon, 1 consoles2026-09-09: RedAmon, 1 consoles2026-09-10: RedAmon, 1 consoles2026-09-11: RedAmon, 1 consoles2026-09-12: RedAmon, 1 consoles2026-09-13: RedAmon, 1 consoles2026-09-14: RedAmon, 1 consoles2026-09-15: RedAmon, 1 consoles2026-09-16: RedAmon, 1 consoles2026-09-17: RedAmon, 1 consoles2026-09-18: RedAmon, 1 consoles2026-09-19: RedAmon, 2 consoles2026-09-20: RedAmon, 2 consoles2026-09-21: RedAmon, 2 consoles2026-09-22: RedAmon, 2 consoles2026-09-23: RedAmon, 2 consoles2026-09-24: RedAmon, 2 consoles2026-09-25: RedAmon, 2 consoles2026-09-26: RedAmon, 2 consoles2026-09-27: RedAmon, 2 consoles2026-09-28: RedAmon, 2 consoles2026-09-29: RedAmon, 2 consoles2026-09-30: RedAmon, 2 consoles2026-10-01: RedAmon, 2 consoles2026-10-02: RedAmon, 2 consoles2026-10-03: RedAmon, 2 consoles2026-10-04: RedAmon, 2 consoles2026-10-05: RedAmon, 2 consoles2026-10-06: RedAmon, 2 consoles2026-10-07: RedAmon, 2 consoles2026-10-08: RedAmon, 2 consoles2026-10-09: RedAmon, 2 consoles2026-10-10: RedAmon, 2 consoles2026-10-11: RedAmon, 2 consoles2026-10-12: RedAmon, 2 consoles2026-10-13: RedAmon, 2 consoles2026-10-14: RedAmon, 2 consoles2026-10-15: RedAmon, 2 consoles2026-10-16: RedAmon, 2 consoles2026-10-17: RedAmon, 2 consoles2026-10-18: RedAmon, 2 consoles2026-10-19: RedAmon, 2 consoles2026-10-20: RedAmon, 2 consoles2026-10-21: RedAmon, 3 consoles2026-10-22: RedAmon, 3 consoles2026-10-23: RedAmon, 3 consoles2026-10-24: RedAmon, 3 consoles2026-10-25: RedAmon, 3 consoles2026-10-26: RedAmon, 3 consoles2026-10-27: RedAmon, 3 consoles2026-10-28: RedAmon, 3 consoles2026-10-29: RedAmon, 4 consoles2026-10-30: RedAmon, 4 consoles2026-10-31: RedAmon, 4 consoles2026-11-01: RedAmon, 4 consoles2026-11-02: RedAmon, 4 consoles2026-11-03: RedAmon, 4 consoles2026-11-04: RedAmon, 4 consoles2026-11-05: RedAmon, 4 consoles2026-11-06: RedAmon, 4 consoles2026-11-07: RedAmon, 5 consoles2026-11-08: RedAmon, 5 consoles2026-11-09: RedAmon, 5 consoles2026-11-10: RedAmon, 5 consoles2026-11-11: RedAmon, 5 consoles2026-11-12: RedAmon, 5 consoles2026-11-13: RedAmon, 5 consoles2026-11-14: RedAmon, 5 consoles2026-11-15: RedAmon, 5 consoles
  • PentAGI398includes the 116 cloned consoles
  • ARTEX family202steepest climb, from mid-October
  • Agent Zero46general-purpose agent
  • CyberStrikeAI15few certificates before mid-September in our data
  • RedAmon5graph recon

How to read this: each line counts consoles whose TLS certificate is dated on or before that day, so it only covers consoles that serve TLS and undercounts every tool. Whoever creates a certificate sets its date, and CyberStrikeAI makes a new one each time it restarts, so read the shape, not the exact days. Dating consoles by certificate follows Houdin.io’s CyberStrikeAI timeline (September 29), and Check Point published an ARTEX timeline on November 5. ARTEX and PentAGI census counts are in the figure further down.

2,335Exposed offensive AI consoles on 2,022 IP addresses
436ARTEX consoles in one hosting network
47Distinct ARTEX variants: forks, private builds and renamed consoles

What we found

Most of the 2,335 consoles are stock installs. The rest include 436 ARTEX consoles in one hosting network, 116 copies of one PentAGI setup, and 179 renamed or forked ARTEX consoles that a search for the default title misses.

Only one console in our census links directly to the attacks above: 204.194.51.54, a stock ARTEX console that AhnLab ASEC listed as an attack IP in October. We didn't tie any other console to those campaigns.

The numbers kept climbing while we worked. Between our November 6 census and a rerun on November 18, Shodan results for the stock ARTEX title went from 1,483 to 2,085, up 41% in 12 days, and PentAGI went from 520 to 626. Some of that will be Shodan crawling more.

The ARTEX family tree

ARTEX's original repo was deleted on October 8. Its forks and builds kept running. Cloudflare mapped 204 public ARTEX forks on November 13; we wanted to see which ones were actually deployed, and what else was running that no public repo explains.

One deleted repo, 47 distinct ARTEX variantsARTEX lineage, from source review and console titles in the census
01 UpstreamAutumn-27/ARTEXHTTP 404 · deleted

First commit ≈26 Jul 2026, deleted 8 Oct. The copies kept going.

02 Public forks 11
  • English & global
    • ARTEX (English)horizonl · 130+ forks of its own
    • artex-globaljiwoochris + forks · 0.3.15-global.1
  • Korean
    • artex-kobear2u · ko, zh, en, es titles
    • artex-koTomatamatom1
  • Chinese derivatives
    • 月落 ycodeadds WAF bypass, leak hunting
    • 谛听 DITINGstill artex-web inside
    • SCA AuditErnket/CodeScan-Artex · code audit
  • Upstream title kept
    • reArtexwufufu770 · repackaged
    • artex-cD4rk-3ch0 · adds guardrails
    • artex failsafefailsafe-security · seen deployed in RU
  • Trojanized
    • Docker imagestomicdd + congdonglinux · backdoored · 7,946 pulls
03 Private builds 14
  • Fleet & ARTES
    • sco-fix2348 services, one network
    • artes.20261010“ARTES” rename
    • 0.3.15-2-gc727eadsame ARTES family
  • Operator custom
    • heker.12 / .19HekerAI
    • 0.5.0-customEnglish fleet
    • Korean em-dash title2 consoles · edited Korean fork
  • Named builds
    • pentest-expert0.9.1 · ScopeWeaver-branded
    • hotfix-seed-castTencent SG
    • gateway-switchgoal-refresh-gateway-switch · artex-mx
  • Dev & dated
    • phase-e-20261115built 2 days before we saw it
    • process-cleanup1.0.4 · “Team 执行节点”
    • 20261105date-only version
    • ffef5e2-dirtydev build in production
    • 0.4.3past the last public 0.4.2
04 Running in the wild under new names 29
  • 4+ consoles
    • ScopeWeaver×65
    • Autonomous Pentest Agent×11
    • 渗透工作台×8
    • TGSEC 社区专属版×4
  • 2 consoles each
    • HekerAI×2
    • 月落×2
    • Cybrion×2
    • LMTex×2
    • AntiFox×2
    • NKW×2
    • airsuperMAN×2
  • 1 console each
    • GOOGTEX
    • ARTIFEX
    • SHRIKE
    • SKARN
    • 猎杀者
    • 海盗船
    • ExploitFinder
    • MiniHunter
    • BoomInner
    • Hopps
    • ARGUS
    • Soua
    • mose
    • artex-mx
    • Team 执行节点
    • 安全渗透智能体
  • Disguised
    • Security Console
    • AegisLoop

Each row is a generation. Forks are public repos and Docker images, private builds carry version strings found in no public repo, and the bottom row is the names ARTEX consoles wore in our scans (×2 means two consoles). Those names are console titles; companies with the same name are unrelated. Seven of the 54 entries repeat a variant already shown, such as a build seen under a name, which leaves 47 distinct variants, 42 of them seen running.

The bottom row is the names ARTEX consoles wore in our scans. SOCRadar, PenTestIT and Profero reported some of them too. A few stood out:

  • SCA Audit — 代码审计平台: a public code-audit derivative of ARTEX (Ernket/CodeScan-Artex), which one operator runs next to PentAGI on the subnet described below. We have no evidence the repo's author is involved.
  • HekerAI: a custom build, 0.7.0-heker.12 and .19, that appears in no public repo.
  • 月落 (Moonset): ycode, a public ARTEX derivative that adds GitHub leak hunting.
  • 安全渗透智能体: a generic title ("security pentest agent") on a console Shodan identifies as ARTEX, so a title search never finds it.

Shodan's product data also carries ARTEX version strings, and many of them match no public release. We found fourteen private builds, seven of them new in our November 18 rerun. sco-fix2 is the fleet build below, first reported by Check Point. 0.9.1-pentest-expert.20261117 is a ScopeWeaver-branded build dated the day before we saw it. 0.4.3 is past the last public 0.4 release, so someone kept building after the repo came down. And ffef5e2-dirty is a development build running in production on Tencent Cloud.

Three undocumented offensive agent tools

A final sweep on November 18 looked for consoles describing themselves in red-team and attack terms. Four held up after we checked each one twice, and we show three here: we pulled the exact text from Shodan's stored copy of each page, confirmed it with a second search that returns only that console, and looked for the tool in web search (English and Chinese), GitHub and Sourcegraph (including forks), CSDN, Wayback, AlienVault OTX, GitGuardian's 45-tool catalog and TSecBench. None of them appears in any of those sources.

ToolWhat its own page advertisesWhy we call it offensiveWhat we can't say
红刃 (Red Blade)"红队攻击 Agent" (red-team attack agent), with open endpoints /api/exploit, /api/scan, /api/recon and /api/chat, no loginIt calls itself an attack agent and exposes an exploit API with no authenticationWho runs it
RedTeam Platform (红队安全测试平台)Streams agent sessions and campaigns, chains findings into "attack chains", and has a form to "register real targets"; behind a loginIt's a working campaign dashboard aimed at real targetsWho runs it, and whether that testing is authorized
鲸鱼 (Whale) red-team pentest console"LLM 驱动的鲸鱼红队渗透测试系统控制台" (LLM-driven Whale red-team pentest system console)The same server presents a self-signed certificate impersonating www.apple.com (created November 11) and runs a SOCKS5 proxy, and its IP was already in ARTEX IOC feeds built from FBI and Talos indicatorsThe IP was known; the console on it is what's new

Everything here is what the tools' own pages advertise. We didn't call any endpoint or log in to anything. Each is a single console, so treat them as first observations rather than tools in wide use. Shodan captured Red Blade on November 6 and Whale on November 3, and the RedTeam Platform was live on November 18. Red Blade's and Whale's certificates are from October and November, and any of these consoles could disappear. GreyNoise saw none of them scanning. To reproduce the two with no login, search Shodan for http.html:"红刃 · 红队攻击" and http.html:"LLM 驱动的鲸鱼"; each returns one console.

The same sweep turned up two weaker candidates we're holding: 海棠 (Haitang), a pentest portal known only by its login page, and a vulnerability-mining "command center" built on the public AutoCodex project. We dropped others after checking: Magician Hunter was an empty app shell, one "AI red team" console only reused a generic login template, and 鸾鸟 turned out to be LuaN1aoAgent, already in GitGuardian's catalog.

Ten more candidates

Before that sweep, searching console titles in Chinese, Korean, Russian and Turkish turned up AI pentest consoles for tools we couldn't find documented anywhere. Most named Chinese tools turned out to be documented already (DITING, Stopen, Dhunter, xArgus and others), so they're not shown here. What's left are candidates: deployed consoles of tools with no public source code, mostly one instance each, with weaker evidence than the three above. Some belong to vendors or companies, such as PaaP, Pentest Check and APTS; we include them because their consoles are exposed to the internet.

10 undocumented AI pentest tool candidates11 consoles · 3 title languages · census and follow-up scans
  • 穿石 SeepZH
    Page code capturedAI pentest agent1 console · CN
  • APTSZH
    Page code capturedAI automated penetration testing system1 console · CN
  • PaaPTR
    Page code capturedAI-assisted pentest & red team1 console
  • MELLMAPRU
    Page code capturedPentest reconnaissance1 console
  • Pentest CheckRU
    Page code capturedDeep auto-pentest2 consoles
  • PTAgentZH
    Red-team pentest agent platform1 console · SG
  • 破隟ZH
    Automated pentest platform1 console · CN
  • 天戟ZH
    AI pentest platform1 console · CN
  • 玄戈 XUANGEZH
    Automated pentest platform1 console · US
  • HVAZH
    AI pentest platform1 console · CN

Consoles running AI pentest tools we couldn’t find in any public repo, vendor page or published research. None has public source code, so these are candidates, not confirmed new tools. For five we captured page code showing a working app; the strongest is 穿石 Seep, with its own agent-chat API and per-task model routing. The other five are known from their console title only.

Disguised consoles

Some consoles hide behind a codename or another product's title. We found these with targeted searches, such as a tool's page code with its default titles excluded, so they're on top of the census count.

  • DarkAI: a renamed CyberStrikeAI console on ByteDance's Volcano Engine cloud. The title says DarkAI, but the page carries CyberStrikeAI's brand-wordmark__core CSS class. ScanMalware named DarkAI among 57 renamed CyberStrikeAI consoles on November 7, and our marker finds it independently.
  • Security Console — 安全审计控制台: an ARTEX console presenting itself as a security audit tool, with an LLM gateway (new-api) on the same server. We found it through a login redirect we learned from urlquery reports (see Methodology).
  • Bob Research Labs: a console titled "We're coming to root your server!", with IRC, MariaDB and open directory listings, which AhnLab ASEC reported first.

Tracking fleets

Hundreds of consoles running the same tool could be hundreds of different people. So we looked for consoles that provably came from one disk image or one private build. Following the swarmcha.se team (our title is a nod to them), we call these fleets. A swarm would mean agents coordinating across machines; these are copies of one tool, with the planner and worker agents coordinating inside each console. A fleet tells you where the software came from. Who runs it is a separate question: a hosting provider selling the same ready-made server to many customers would look identical from outside.

We used three kinds of evidence, from strongest to weakest:

  1. A shared TLS certificate. PentAGI makes its own certificate on first start, named CN=localhost, so two separate installs never share one. Servers that present the exact same certificate also hold the same private key, so they were copied from one setup, either a cloned disk image or copied certificate files. A non-default certificate name makes that clearer still.
  2. A private build string. A version string like sco-fix2 that matches no public release means the servers run the same private copy. Lots of them in one network points to one source, but it can't separate an operator from a provider's preinstalled image.
  3. An identical page hash. Scanners hash each page a server returns. Matching hashes mean the same build, but stock releases share hashes too, so this only backs up the other two.
Every console we foundOne square per exposed console · 2,335 consoles · Shodan census 6 Nov, follow-up 17 Nov 2026
ARTEX family 1,825PentAGI 427Cairn 48Other tools 35One hosting network: 436 consoles (AS54600; 348 on build sco-fix2)Stock ARTEX: 1,171 consoles (default title, many networks)Renamed and forked: 179 consoles (a title search misses them)Login prompt only: 39 consoles (found by the "ARTEX" login realm)116 copies, one certificate: 116 consoles (same certificate and page hash)Other PentAGI: 311 consoles (independent installs)Cairn: 48 consoles (incl. renamed forks)Other AI pentest tools: 35 consoles (found by non-English title search; many already documented)ARTEX family 1,825PentAGI 427Cairn 48Other tools 35One hosting network: 436 consoles (AS54600; 348 on build sco-fix2)Stock ARTEX: 1,171 consoles (default title, many networks)Renamed and forked: 179 consoles (a title search misses them)Login prompt only: 39 consoles (found by the "ARTEX" login realm)116 copies, one certificate: 116 consoles (same certificate and page hash)Other PentAGI: 311 consoles (independent installs)Cairn: 48 consoles (incl. renamed forks)Other AI pentest tools: 35 consoles (found by non-English title search; many already documented)
  • One hosting network436AS54600; 348 on build sco-fix2
  • Stock ARTEX1,171default title, many networks
  • Renamed and forked179a title search misses them
  • Login prompt only39found by the "ARTEX" login realm
  • 116 copies, one certificate116same certificate and page hash
  • Other PentAGI311independent installs
  • Cairn48incl. renamed forks
  • Other AI pentest tools35found by non-English title search; many already documented

How to read this: each square is one exposed console service. Darker blocks are the groups that share one origin: 436 ARTEX consoles inside one hosting network, 348 of them on one private build, and 116 PentAGI consoles sharing one certificate. The red band in the middle is the renamed and forked ARTEX builds, which a search for the default title misses. Counts come mostly from Shodan and are lower bounds; 14 servers run two tools side by side.

The sco-fix2 fleet: 348 services in one network

348 services on 254 IPs report the ARTEX build sco-fix2, which matches no public release, and every one sits in AS54600 (PEG TECH). How big the fleet is depends on what you count: its page hash went from 362 services on November 6 to 438 on November 18, while Shodan's sco-fix2 version matches fell from 425 to 402.

Others found this cluster first. RST flagged the network on November 2, Check Point named the build on November 5 (255 hosts), Gcore found 305 matching pages, and SOCRadar counted 242 on November 12 and found a Sub2API gateway on port 8790 on many of the servers. Our counts match theirs. It could be one operator's staging setup or a provider selling servers with ARTEX preinstalled; scan data alone can't tell which.

One PentAGI setup, 116 copies

116 PentAGI consoles present the exact same TLS certificate and serve the same page hash. The certificate's name was changed from PentAGI's default localhost to a specific server's IP address. Put together, that's strong evidence they all came from one setup, most likely a cloned disk image. The copies sit in AS398823, another network run by the hosting provider PEG TECH. Gcore reported this cluster on November 9 (101 endpoints), and RST counted about 90 there on November 2. By November 18, certificates naming the same server were on 158 consoles.

One operator, two tools

On one /24 subnet, seven ARTEX consoles (the SCA Audit build) share one certificate and six PentAGI consoles share another. Both certificates use the same custom naming pattern, O=CodeScan-Artex self-hosted and O=PentAGI self-hosted, both name the same server, and they were created a day apart. It's the closest thing to an operator fingerprint in our data: most likely one person set up both tools. GreyNoise recorded the subnet scanning in early November.

What this means

Exposed consoles are a cheap, public signal of who's deploying these tools and how. Here's what we learned:

  1. Titles don't hold up. 179 renamed or forked ARTEX consoles don't use the default title, and a title search for Cairn returns mostly coffee shops and holiday cottages. Page code, certificates and build strings held up much better.
  2. Copies are easy to spot. A shared certificate or a private build string turns hundreds of separate-looking consoles into a handful of setups.
  3. It moves fast. In the 12 days between our census and the rerun, the stock ARTEX title count rose 41%, seven new private builds appeared (one dated the day before we saw it), and three undocumented offensive agent tools turned up.
  4. Most of this is shared work. Many teams published counts, clusters and fingerprints before us. The catalog below credits each one and splits out what's ours.

This is the kind of work we love to do at Delta, our skunkworks: chase a question across scan data, source code and other people's research until the picture holds up. Stay tuned for more.

Methodology

We cloned the open-source repositories for ARTEX (from the BaaRai mirror), PentAGI, Cairn, CyberStrikeAI, scopeweaver, RedAmon, Xalgorix, Agent Zero, HexStrike AI and PentestAgent into an isolated AWS sandbox, and looked for the parts of each web UI a rebrand rarely touches: CSS animation names, theme scripts, asset paths and how certificates get made.

Titles turned out to be a poor fingerprint. On November 6, a Shodan search for title:Cairn returned 199 results, and about three quarters were coffee shops, holiday cottages, universities and other unrelated sites. The same day, a search for reasonBeaconPulse, a CSS animation name in Cairn's template, returned 44, all real Cairn consoles, including forks renamed to titles like Zero. Shodan's own Cairn product filter found 16. For ARTEX, title, page and version fingerprints together found 1,825 consoles; GitGuardian independently counted 1,428 with different fingerprints.

Scan engines also miss things. The swarmcha.se team used urlquery.net, a public URL-scanning service, to trace an agent fleet. We searched its public reports for the ARTEX console title and found consoles Shodan hadn't indexed. Those reports showed a redirect from / to /login on port 8091, which we turned into a Shodan query that surfaced the disguised Security Console.

Everything here comes from third-party scan data (Shodan, InternetDB, urlquery.net, urlscan.io, GreyNoise, DNS blocklists, certificate transparency logs) and source review in the sandbox. We never connected to a console. We also removed 157 rows from our raw census of 2,492 that turned out not to be consoles: unrelated pages matching a generic marker, businesses named Artex, and a static page explaining PentAGI's prompts.

An exposed console isn't proof of an attacker. Some of these will belong to authorized pentesters, students and researchers, and some may be honeypots set up to catch people hijacking consoles. Scan data has other limits too. Counts come mostly from Shodan, so they're lower bounds. Certificate dates are set by whoever makes the certificate. Shared certificates and builds show shared software, and anything we say about operators or motives is our best reading of that evidence.

We're not publishing IP addresses for most consoles. Indicators, the full host list and the 157 removed rows are available to researchers and defenders on request.

The fleets we found

FleetSizeEvidenceAssessmentConfidence
sco-fix2 fleet348 services, 254 IPs, all in AS54600Private build string sco-fix2 (348); one page hash (362 services); Sub2API gateway on port 8790 (SOCRadar)One operator's staging infrastructure or an "ARTEX preinstalled" hosting product. Network: RST (Nov 2); build string: Check Point (Nov 5); Sub2API: SOCRadar (Nov 12)Shared origin: high. One operator: low
116 PentAGI copies116 identical copies; 158 consoles by November 18 named the same serverOne shared non-default certificate; one page hashMost likely one cloned image; operator unknown. Cluster first reported by Gcore (Nov 9) and RST (Nov 2)Shared origin: high. One operator: low
One operator, two tools13 consoles on one /24: 7 ARTEX, 6 PentAGITwo certificates with the same custom naming pattern, naming the same server, created one day apartLikely one operator; GreyNoise recorded scanning in early NovemberShared origin: high. One operator: moderate
November 3 group5 consolesOne shared certificate dated November 3, in netblocks on Spamhaus's SBL and DROP listsOne cloned setup; no scanning seen in early November (GreyNoise)Shared origin: high. One operator: low
Let's Encrypt group5 consolesOne shared Let's Encrypt certificate for a real domain instead of the default self-signed oneThe same certificate and key on all five points to one setup; the domain's owner isn't known to be involvedShared origin: high. One operator: moderate
PentAGI and adult sites8 serversOne shared PentAGI certificate; the same servers host six adult-content domains with an identical Cloudflare name-server pairShared image is solid; the name-server pair suggests, but doesn't prove, one account behind the domainsShared image: high. Same account behind the domains: low

The fingerprint catalog

Every technique we used. The first part is ours; the second is what others published first, and what it found for us.

TechniqueWhat it findsResultEvidence and credit
Our fingerprints and methods
Cairn CSS animation namesreasonBeaconPulse and related animation names in Cairn's page template; catches renamed forks44 services on November 6, against 16 from Shodan's product filter; forks Zero, CPU and WorkerAntFrom Cairn's source (oritera/Cairn), tested on Shodan. PenTestIT published a different Cairn style name (intentChipGlow)
CyberStrikeAI wordmark classbrand-wordmark__core in the login page336 services, including renamed builds such as DarkAIFrom CyberStrikeAI's source (AIPentest/CyberStrikeAI), tested on Shodan
CyberStrikeAI stylesheetc2.css referenced in served pages543 servicesFrom CyberStrikeAI's source (AIPentest/CyberStrikeAI), tested on Shodan
DeepAudit HTML commentThe "Terminal Retro & Cassette Futurism Typography" comment in DeepAudit's page319 services on November 18; DeepAudit is outside our census countsFrom DeepAudit's source; a candidate, since how many matches are real DeepAudit consoles is not yet measured
PaaP theme keyThe paap-theme key in PaaP's page1 consoleFrom the live page; a candidate with a single match so far
Login-header miningConsoles that show nothing but a password prompt. Shodan can't search the login header, so we downloaded every port-8787 login response and read the headers ourselves39 services on 37 IPs naming the realm "ARTEX", out of 2,813 checkedOur method. The "ARTEX" realm itself was published by RST Cloud and MalwareMustDie
Title punctuationWhether a Korean ARTEX console runs the public fork as shipped or an edited copy: the public fork's source deliberately uses a colon in the title, so an em-dash title means someone changed it2 consoles with an edited Korean titleFrom the bear2u/artex-ko source comment. RST listed both title forms, and PenTestIT traced titles to the fork's config file
New private build labelsARTEX version strings in Shodan's product data that match no public release13 labels, including 0.7.0-heker.12, phase-e-20261115, 0.9.1-pentest-expert.20261117 and 1.0.4-process-cleanup.20261115The version-string method was published by Check Point (Nov 5); these labels are ours
Seven shared-certificate groupsConsoles that present the exact same certificate, so they share one originGroups of 8, 7, 6, 5, 5, 4 and 4 consoles, none in a published clusterCertificate-reuse clustering was published by SOCRadar and Gcore, which also reported the 116-copy group
urlquery.net console searchConsole URLs in urlquery's public scan reports that Shodan had not indexed2 ARTEX consoles, and a / to /login redirect we turned into a Shodan query that found the disguised Security ConsoleUsing urlquery as a sensor follows swarmcha.se; searching it for consoles is ours
Non-English title sweepConsole titles with Chinese, Russian and Turkish pentest-agent keywords, to find tools English searches miss自动化渗透 16, 智能渗透 10 and AI渗透 17 services; the candidates in the undocumented-tools figureOurs. Hunt.io and ScanMalware published ARTEX's titles in other languages
Cloudflare name-server pairsDomains whose identical name-server pair suggests one Cloudflare accountSix adult-content domains on the same servers as the 8-console PentAGI groupThe technique is known OSINT (James Motherway); this link is ours
Published by others, used here
Default titlesThe <title> each tool ships withStock ARTEX, PentAGI and Cairn consolesRST Cloud (Nov 2)
Shodan product filterShodan's own tag for a productproduct:"Cairn" found 16 of 51 Cairn consolesShodan built-in
PentAGI favicon hashThe hash of PentAGI's default icon420 services on November 6RST Cloud (Nov 2)
PentAGI certificate issuerThe default "PentAGI CA" certificate, visible even behind a login243 servicesRST Cloud (Nov 2); confirmed in PentAGI's source
ARTEX login realmA 401 response naming the realm "ARTEX"The 39 login-only consoles aboveRST Cloud; MalwareMustDie. PenTestIT traces the realm to the ycode fork
CyberStrikeAI theme keycyberstrike-theme in the theme script409 servicesHoudin.io (Sep 29)
Identical page hashesThe same page hash across hosts means the same buildOne page hash on 362 services in AS54600Gcore, SOCRadar and Profero
Page code without the default titleA tool's page code, excluding its stock titles, to find disguised consolesSecurity Console, DarkAIScanMalware published similar exclusion queries
Agent drop-box inboxeswebhook.site inbox IDs decoded from agent payloads in urlquery reports4 inboxes, all already expiredswarmcha.se's method, reproduced
Activity and abuse checksWhether console IPs are scanning (GreyNoise) or sit in abusive netblocks (Spamhaus)Context for the fleet table; dated observationsStandard enrichment services
Behavior on the victim sideArtexProbe accounts, artex-probe-* files, 2 to 25 second bursts and rotating webhook.site URLs (GTIG); a think-then-act request cadence (Unit 42); i04probe sign-up accounts (Okta)Detection in your own logsGoogle GTIG, Unit 42, Okta
ARTEX user agentsartex-readonly/1.0, ARTEX-worker/1.0 and othersDetection in your own logsDatadog Security Labs (Nov 9)

References

Exposed-console and infrastructure research

  1. Houdin.io. Mapping 200 still undetected Chinese AI attack platforms in the wild. September 29, 2026.
  2. AhnLab ASEC. The Threat of AI-Driven Autonomous Penetration Testing, as Examined by ARTEX. October 14, 2026.
  3. AhnLab ASEC. Analysis of the Infrastructure of ARTEX, a Chinese AI Penetration Testing Tool #4: The Birth of Copy Cat. October 14, 2026.
  4. swarmcha.se. We found a Tencent agent fleet. October 14, 2026.
  5. NorForge. Automated Subversion and Attempted Takeover of AI Pentesting Harnesses. October 26, 2026.
  6. Profero IRT. One Operator, Several AI Attack Agents: The Ultra Suite and ARTEX. October 31, 2026.
  7. RST Cloud. Tempo, not technique: hunting the AI harnesses behind today's intrusions. November 2, 2026.
  8. Hunt.io. ARTEX Exposed: Mapping the Infrastructure Behind the South Korean Bank Breaches. November 4, 2026.
  9. Profero IRT. Inside the AI Operator. November 4, 2026.
  10. Check Point Research. Hacking on Autopilot: Inside ARTEX Cybercrime Campaigns. November 5, 2026.
  11. Censys. ARTEX: Agentic Asbestos. November 5, 2026.
  12. ScanMalware. Agentic Hacking in the Wild: How We Track ARTEX, CyberStrikeAI and Their Rebrands. November 7, 2026.
  13. Gcore. We found 1,698 Internet-visible AI offensive-security endpoints. Here's what the data reveals. November 9, 2026.
  14. GitGuardian. Beyond ARTEX: 45 AI Pentesting Tools and How to Find Them. November 9, 2026.
  15. Palo Alto Networks Unit 42. ARTEX and AI-Powered Red Teaming Tools: What Defenders Need to Know. November 11, 2026.
  16. SOCRadar. ARTEX: 916 Exposed AI Pentest Consoles Mapped in the U.S.. November 12, 2026.
  17. Cloudflare. Adapting to AI penetration testing orchestrators: The Modern Security Model. November 13, 2026.
  18. Cisco Talos. ARTEX and beyond: AI-enabled penetration testing platforms. November 13, 2026.
  19. PenTestIT. AI Pentesting Frameworks: Abuse, Lineage, Fingerprints. November 14, 2026.

Threat intelligence

  1. CrowdStrike. Unknown Threat Actor Uses AI-Driven ARTEX to Target South Korean Finance. October 7, 2026.
  2. Microsoft Threat Intelligence. AI-driven, large-scale nation-state campaign using ARTEX enables supply chain compromise. October 21, 2026.
  3. Wiz. ARTEX in the Wild: Storm-0940 Expands Targeting of IT and Software Vendors. October 22, 2026.
  4. CrowdStrike. VAPOR PANDA Uses AI-Driven ARTEX to Scale a Global Espionage Campaign. October 29, 2026.
  5. Google Threat Intelligence Group and Mandiant. ARTEX and Friends: Enter Agentic Offensive Frameworks. October 30, 2026.
  6. Securelist. CyberStrikeAI in the wild: the use of AI in real-world attacks on organizations. November 2, 2026.
  7. Okta Threat Intelligence. Agentic attack tools used to accelerate reconnaissance of identity flows. November 6, 2026.
  8. Datadog Security Labs. On the hunt for ARTEX: understanding agentic attacks in AWS environments. November 9, 2026.
  9. Palo Alto Networks Unit 42. Attackers Use Autonomous AI to Target Semiconductor, Defense and Civil Society Sectors. November 12, 2026.
  10. Federal Bureau of Investigation. FLASH-20261113-001. November 13, 2026.
  11. AlienVault OTX. ARTEX infrastructure indicators (pulse 6afa566f28ebebfb22046701). November 16, 2026.

Detection content

  1. MalwareMustDie. MMD-072-2026 - ARTEX detection signature pack - from IOC w/playbook process. November 13, 2026.

Trojanized tools

  1. Cloud Security Alliance. Trojanized Offensive AI Tooling: The ARTEX Docker Backdoor. November 6, 2026.