---
type: "post"
id: "censys-finds-1-465-publicly-exposed-artex-ai-38ea2e"
slug: "censys-finds-1-465-publicly-exposed-artex-ai-38ea2e"
title: "Censys finds 1,465 publicly exposed ARTEX AI pentest consoles; TechCrunch covers the exposure"
description: "Censys says it observed 1,465 internet-exposed consoles for ARTEX, an open-source autonomous penetration-testing framework, as of November 4, 2026."
retrieval_nugget: "Censys says it observed 1,465 internet-exposed consoles for ARTEX, an open-source autonomous penetration-testing framework, as of November 4, 2026. The finding matters because these interfaces and adjacent open directories can expose offensive tooling; the count also makes public inventory and hardening relevant to teams responsible for internet-facing systems."
published_at: "2026-11-06"
updated_at: "2026-11-06"
record_date: "2026-11-06"
date_kind: "published_at"
topics: ["anthropic"]
entities: ["Censys","ARTEX","ScopeSentry","CrowdStrike","Microsoft","Storm-0940","Anthropic","OpenAI"]
related_patterns: ["agent-security-moves-to-runtime-boundaries"]
novelty_label: "new_fact"
what_changed: "Censys reports finding 1,465 publicly exposed ARTEX AI penetration-testing consoles."
prior_refs: ["https://newruntime.com/posts/china-linked-hackers-breached-connectwise-using-ai-penetration-a92d8d/"]
source_url: "https://censys.com/blog/artex-agentic-asbestos"
source_urls: ["https://censys.com/blog/artex-agentic-asbestos"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:censys-finds-1-465-publicly-exposed-artex-ai-38ea2e"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/censys-finds-1-465-publicly-exposed-artex-ai-38ea2e/","markdown":"https://newruntime.com/posts/censys-finds-1-465-publicly-exposed-artex-ai-38ea2e.md","json":"https://newruntime.com/posts/censys-finds-1-465-publicly-exposed-artex-ai-38ea2e.json"}
markdown_url: "https://newruntime.com/posts/censys-finds-1-465-publicly-exposed-artex-ai-38ea2e.md"
---

# Censys finds 1,465 publicly exposed ARTEX AI pentest consoles; TechCrunch covers the exposure

## Retrieval answer

Censys says it observed 1,465 internet-exposed consoles for ARTEX, an open-source autonomous penetration-testing framework, as of November 4, 2026. The finding matters because these interfaces and adjacent open directories can expose offensive tooling; the count also makes public inventory and hardening relevant to teams responsible for internet-facing systems.

## Summary
Censys says it observed 1,465 internet-exposed consoles for ARTEX, an open-source autonomous penetration-testing framework, as of November 4, 2026. The finding matters because these interfaces and adjacent open directories can expose offensive tooling; the count also makes public inventory and hardening relevant to teams responsible for internet-facing systems.

## What happened
Censys published its findings on November 5, 2026. It describes ARTEX as an LLM-driven autonomous penetration-testing framework released on GitHub as Autumn-27/ARTEX on July 26, 2026, under the AGPL-3.0 license. Its author, Autumn-27, also created ScopeSentry, an asset-discovery and vulnerability-scanning platform. The ARTEX repository has since been taken down, although Censys says archived copies, translations and rebrands continue to circulate.

ARTEX adds an agent layer to reconnaissance. It can sync domains, subdomains, IP addresses, ports and endpoints discovered by ScopeSentry into an asset graph. A user defines a task with a scope, test accounts and a goal. A Planner agent turns the goal into attack intents; Worker agents claim those intents, run tools such as nmap, and return results. An event-driven engine repeats the explore-decide-execute loop until the goal is met. ARTEX also tracks an exploration graph showing how much of a target has been tested, includes mitmproxy for traffic recording, and can use Anthropic, OpenAI or any OpenAI-compatible model endpoint. Censys reports that ARTEX is written in Go, with a Next.js web console and PostgreSQL backend.

Censys says it identified 1,465 hosts as of November 4 using the ARTEX page title and Next.js static assets. About 650 hosts fell within two blocks of identically configured hosting; excluding these leaves roughly 815 deployments that appear distinct. The default console port is 8787, with 8790, 443 and 80 also observed. Censys cautions that ARTEX consoles do not need public access, so its count is not a full measure of deployments. It also says that some publicly exposed instances may belong to authorized testers.

The report found that 155 of the 1,465 hosts, or 10.6%, had at least one other threat detection. These included other agentic pentest tools, conventional command-and-control or tunneling software, and self-hosted LLM gateways or resellers. Censys observed 32 open directories on ARTEX hosts containing items such as exploit binaries, stagers, implants and other operator files. The report says many directories were exposed for hours or days; between November 3 and 5, ten closed and fifteen new ones appeared on other ARTEX hosts.

The report places these observations alongside two October campaign accounts. CrowdStrike attributed a campaign against South Korean financial institutions to an actor using ARTEX; Microsoft attributed the ConnectWise Cloud Backup compromise to Storm-0940, which used ARTEX for scanning, password spraying and OAuth application abuse. Censys says its own observations are about exposed infrastructure, not proof that every ARTEX host participated in attacks.

## What the archive adds
New Runtime's earlier coverage on October 24 reported that a China-aligned group used ARTEX in a ConnectWise Cloud Backup breach. [That earlier note](https://newruntime.com/posts/china-linked-hackers-breached-connectwise-using-ai-penetration-a92d8d/) is related to, but distinct from, Censys's new exposure measurement: this is a new fact on a known story, not a restatement.

## Trend signal
This supports [agent security moving to runtime boundaries](https://newruntime.com/patterns/agent-security-moves-to-runtime-boundaries/): the exposed console, host configuration and accessible files are security boundaries with consequences beyond the model's instructions. Censys's observations make that boundary concrete, while not establishing that every exposed deployment was compromised.

## Why now
Censys's November 5 measurement follows October reporting by CrowdStrike and Microsoft linking ARTEX to observed campaigns. The timing lets defenders compare the campaign accounts with a contemporaneous scan of internet-facing installations and associated exposed files.

## Connections to other events
New Runtime's October 24 coverage described ARTEX's use in a ConnectWise Cloud Backup breach attributed by Microsoft to Storm-0940. Censys adds a separate view of the same tool's exposed deployment footprint, including a count of hosts and examples of adjacent infrastructure. The report also recounts CrowdStrike's October 7 account of ARTEX use against South Korean financial institutions.

## Why it matters
For a security or platform team, an autonomous pentesting console is not just another web application: its purpose is to coordinate reconnaissance and execute tools against a defined target. An internet-facing instance may therefore expose both control surface and operational context. Censys's 32 open directories illustrate a related failure mode: even if an operator intends to use a tool within authorized scope, exposed files can reveal binaries, configurations or other artifacts that make the system easier to understand and potentially misuse.

The measurements are useful as a starting point, not a direct estimate of malicious operators. Hosting templates inflate raw host counts, some instances may be legitimate, and Censys says the console need not be public. Teams can still act on the basic lesson: inventory agent consoles and their supporting services as part of external attack-surface management, restrict access, and check for exposed directories and co-located tooling. This applies beyond ARTEX to systems that combine agents with powerful security tools.

## Limits and uncertainty
Censys's host identification depends on visible page titles and Next.js assets, so it may miss modified or renamed installations. The report says the public count is not the total deployment count, since consoles need not be exposed, and its estimate of roughly 815 distinct-looking deployments depends on excluding two repeated hosting blocks. It does not establish the operator or intent for each host, nor that every exposed directory contained active attack material. The link between Yancy Limited's ARTEX hosts and an earlier Cobalt Strike host surge remains unclear, according to Censys.

## Skill to build now
This week, inventory internet-facing agent and security-tool consoles across your organization. For any ARTEX-like deployment, verify that the interface is not publicly reachable, inspect web roots and shared directories for binaries or configuration files, and look for adjacent command-and-control, tunneling or LLM gateway services. Treat scan results as leads to validate with the system owner, not as proof of compromise.

## Reader takeaway
Censys's count is a snapshot of visible ARTEX consoles, not a tally of attackers. Its more durable lesson is that agentic security tooling can itself become exposed infrastructure: inventory the console, restrict access, and check what else is reachable from the same host.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Anthropic](https://newruntime.com/topics/anthropic.md): Explore the anthropic topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Sources](https://newruntime.com/sources/): See the original sources this archive cites.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)