ARTEX Shodan and Censys:how many consoles are exposed, by source and date.
Several teams counted ARTEX web consoles reachable from the internet in the weeks after the repository came down. The numbers differ because the methods differ. This page lists each count with its source, its date and what it measured.
- When
- Counts dated 2026-10-07 to 2026-11-13
- Reported by
- Censys, Shodan via GitGuardian, Check Point Research, AhnLab, FBI
- Scope
- ARTEX web consoles reachable from the internet
- ARTEX role
- Exposure of the tool itself
What happened
ARTEX has a web console, a Next.js front end over a Go server. Censys notes the console does not need to be public, and the total deployed is likely higher than any scan shows. StepSecurity says the Docker Compose file supplied with ARTEX opens port 8787 on every network interface, so a console on a rented server faces the internet from the moment it starts.
Censys and TechCrunch both stress that not every exposed instance is run with bad intent. Many belong to authorized testers. Check Point looked inside ten consoles whose full database was exposed and says the goals it saw were opportunistic, financially motivated cybercrime, and that Chinese models were the most common.
Counts by source and date
| Source | Count | Date | What it measures |
|---|---|---|---|
| AhnLab ASEC | 394 consoles | 2026-10-07 | ARTEX consoles among exposed web services in the infrastructure AhnLab tracked. A scoped set, not a worldwide census. |
| Censys | 1,465 hosts, about 815 distinct | 2026-11-04 | Hosts with an exposed console. About 650 sit in two blocks of identically configured hosting. |
| TechCrunch, citing Censys | 800+ deployments | 2026-11-06 | Distinct deployments reachable without a password. |
| Check Point Research | 2,557 ever, 1,608 live | 2026-11-05 | Systems hosting or having hosted ARTEX panels, and those live at the time of research. |
| Shodan, via GitGuardian | 1,428 services | 2026-11-07 | Services matching the ARTEX family. GitGuardian publishes fingerprint descriptions, not a target list. |
| FBI flash alert, via The Record | 1,600+ consoles | 2026-11-13 | The alert cites Censys research. |
How ARTEX was involved
Exposure matters because a console is where the operator controls the agents. Censys says 155 of the hosts it counted (10.6%) also ran at least one other threat tool it detects, and it saw 32 open directories on ARTEX hosts exposing post-exploitation kits and implants. It also saw an open directory on the server named in CrowdStrike's report starting 2026-08-18, seven weeks before that report.
StepSecurity adds that the BadByte research counted a backdoored build on internet-facing consoles, which is a different problem from open consoles. See the backdoored Docker image page.
Confirmed and alleged
Reported as observed
- Each source above reported its count for its own date and method.
- Censys, TechCrunch and the FBI alert all say the true total is likely higher because of consoles behind firewalls or in private networks.
- Some exposed instances are run by authorized testers (Censys, TechCrunch).
Alleged, assessed or unclear
- The counts should not be added or ranked. They differ in date, in method (fingerprint, page title, ever-hosted), and in whether clones are removed.
- Why hundreds of consoles are exposed is unclear. TechCrunch says the software does not require it.
- An exposed console is not proof of malicious use. AhnLab says co-hosting does not prove a common operator or bad intent.
Takeaways for defenders
Drawn from what the sources themselves recommend or observed. Not a complete checklist.
- If you run ARTEX for authorized testing, keep the console off the public internet. Censys says it does not need to be public.
- TechCrunch notes that many attacks linked to ARTEX used simple weaknesses, such as guessed weak or known passwords and missing multi-factor authentication.
- Defenders can look for their own exposed instances first. GitGuardian publishes fingerprint descriptions for that purpose and says it is not publishing a target list.
- Operators who leave open directories expose their own tools. Censys saw this repeatedly and CrowdStrike's report on the Korean bank campaign began with one.
Sources
Every claim above comes from these pages or from this site's news data. Open them for the full reports.
- ARTEX: Agentic Asbestos
Censys, 2026-11-05
- Hundreds of Artex AI hacking tools found publicly exposed to the web
TechCrunch, 2026-11-06
- Beyond ARTEX: 45 AI Pentesting Tools and How to Find Them
GitGuardian, 2026-11-09
- Hacking on Autopilot: Inside ARTEX Cybercrime Campaigns
Check Point Research, 2026-11-05
- ARTEX의 진화: 안랩이 추적한 AI 기반 침투 테스트 인프라
AhnLab ASEC, 2026-10-07
- FBI flash alert says Artex tool automating cyberattacks at 'machine speed'
The Record (Recorded Future News), 2026-11-13
- ARTEX: Attackers Adopted This AI Pentesting Tool in Three Months. Leaked Secrets Are Its Fastest Way In.
StepSecurity, 2026-11-12
Follow the ARTEX story.
New forks, releases and reports, dated and sourced.
