InformationalEcosystem changeMonitoring

Cyber Security News reports Talos findings on ARTEX AI tool abuse

Cyber Security News reports Cisco Talos says attackers misuse AI pentest tools ARTEX, PentAGI and HexStrike AI; review logs and exposure.

Published
Exploitation
Not confirmed independently. Cyber Security News reports Talos saying these dual-use tools are being misused, and cites Microsoft findings on Storm-0940 sign-in attempts.

What happened

According to Cyber Security News, Cisco Talos warns that AI-powered penetration testing tools are helping attackers automate reconnaissance, vulnerability testing and follow-on attacks. The outlet says Talos identified growing malicious use of ARTEX, PentAGI and HexStrike AI in a November 13 report. The Talos report itself is not among the sources provided, so everything below is as relayed by Cyber Security News and is not independently verified.

Cyber Security News describes the tools this way:

  • ARTEX: it appeared on GitHub in July 2026 under the developer name Autumn-27. A planner agent splits an operator’s objective into tasks, worker agents run security tools, and a shared graph records assets and findings.
  • PentAGI: a self-hosted multi-agent testing environment with a web interface. The outlet says Talos found more than 700 reachable PentAGI instances online.
  • HexStrike AI: it connects with Claude Code, VS Code and other clients that support Model Context Protocol (MCP).

The outlet says ARTEX has the clearest campaign evidence. It reports that Talos cites Microsoft findings that Storm-0940 used compromised ConnectWise application credentials to accelerate sign-in attempts against more than 2,250 downstream Microsoft 365 tenants. It also reports password spraying, weak administrative credentials, missing API authentication, command injection and authorization flaws. In one Microsoft-observed case, it says, the move from GitHub searches for exposed secrets to Azure Key Vault data theft took five minutes.

Cyber Security News says Talos identified more than 2,500 ARTEX-associated infrastructure IP addresses, with tools such as PentAGI, VShell, AdaptixC2, Mimikatz, Cobalt Strike and several scanners present in overlapping periods. It adds a caveat: shared infrastructure does not prove ARTEX launched every tool or that one operator controlled everything. It also says these are dual-use security tools, not malware families, and that ARTEX does not ship with a traditional command-and-control framework.

Not confirmed: the identity of any operator behind the activity beyond the Storm-0940 reference, the number of victims, and any impact beyond what is described above. No CVE is named in the source.

Am I affected?

The source does not describe a specific vulnerable product or version. You may be relevant to this reporting if:

  • You operate Microsoft 365 tenants or grant third-party applications access to them (the ConnectWise example).
  • You have exposed systems with default or weak administrative passwords, or APIs without authentication.
  • You run PentAGI yourself and it is reachable from the internet.
  • You have secrets in public repositories or cloud credentials that could leak.

Cyber Security News lists these ARTEX-associated IPv4 addresses. Treat them only as investigative leads, since the outlet says a recognizable tool or indicator needs supporting evidence:

  • 92[.]255[.]57[.]95
  • 38[.]38[.]174[.]152
  • 62[.]171[.]139[.]26
  • 155[.]2[.]192[.]70
  • 38[.]12[.]90[.]84

What to do now

Steps 1 and 2 are the recommendations Cyber Security News attributes to Talos. Steps 3 to 5 are general “organizations should” advice in the same article, which does not attribute them to Talos. Step 6 is a practical use of the listed indicators, not a Talos recommendation.

  1. Correlate authentication, endpoint and cloud API logs for rapid requests, unfamiliar applications, unusual token use and privilege changes (attributed to Talos).
  2. Use endpoint tamper protection, and keep tested procedures for disabling suspicious applications, revoking tokens and isolating affected systems quickly (attributed to Talos).
  3. Patch exposed systems, remove default passwords, enforce multifactor authentication and apply rate limits against credential attacks (general advice in the article).
  4. Enable secret scanning on public repositories, and immediately revoke and rotate any exposed credentials (general advice in the article).
  5. Apply least-privilege permissions to applications to reduce downstream access (general advice in the article).
  6. Check the listed IP addresses against your logs, and treat matches as leads that need supporting evidence, not proof of compromise.

Sources