Executive Summary

Between October 3 and mid-November 2026, Amazon's MadPot threat intelligence team captured records from autonomous AI agents running on ARTEX, an open-source AI-powered penetration-testing framework, targeting internet-exposed AI applications including LiteLLM, One API, Dify, Langflow, RAGFlow, and others. The agents exploited default credentials, unauthenticated endpoints, authentication-bypass headers, and known CVEs to harvest AI provider API keys at scale, then verified and pooled those keys to fund further reconnaissance. China-linked operators were assessed with moderate confidence based on Simplified Chinese prompts and China time-zone metadata. Hundreds of targets across AI platforms, CI/CD pipelines, and cryptocurrency exchanges were enumerated, with Cloudflare separately confirming 400 database dump attempts in a single hour from a compromised CI/CD token.

This campaign illustrates a structural shift in attacker economics: AI agents now automate vulnerability discovery, credential harvesting, and key validation end-to-end, dramatically compressing the time between exposure and exploitation. The FBI issued a FLASH alert confirming ARTEX use across multiple sectors globally since at least August 2026, underscoring that agentic AI offensive tooling has moved from proof-of-concept to mainstream criminal infrastructure.

Why This Matters Now

ARTEX and derivative frameworks are actively scanning thousands of organizations daily—over 50 AI pentesting framework families targeted Cloudflare customers in a single three-day window. With the original repository forked into commercial variants and community archives, takedown efforts have failed. Any organization running AI middleware, LLM gateways, or inference endpoints with default credentials or unpatched CVEs faces near-real-time automated exploitation, making immediate remediation and runtime network controls urgent priorities.

Attack Path Analysis

Related CVEs

MITRE ATT&CK® Techniques

Potential Compliance Exposure

Sector Implications

Sources

Frequently Asked Questions

The campaign exploited missing authentication on inference endpoints, default hard-coded credentials, and secrets embedded in CI/CD pipelines and public repositories—gaps that map directly to failures in NIST 800-53 AC-6 (least privilege), SC-7 (boundary protection), and PCI DSS 4.0 requirement 3.5.1. Organizations without centralized secrets management and egress policy enforcement were disproportionately affected.

Cloud Native Security Fabric Mitigations and ControlsCNSF

Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.

Aviatrix Zero Trust CNSF is directly relevant to this campaign because ARTEX agents exploited internet-exposed AI application endpoints and then pivoted freely across cloud environments using stolen credentials and unrestricted network paths. Enforcing workload-level segmentation and identity-aware access boundaries would likely reduce the reachability of these exposed services and constrain the blast radius available to automated credential-harvesting agents.

Initial Compromise

Control: Cloud Native Security Fabric (CNSF)

Mitigation: Reducing direct internet reachability of AI gateway workloads through fabric-enforced perimeter segmentation would likely constrain the exposure surface available to automated ARTEX scanning agents, limiting which services could be directly probed for default credentials or unpatched vulnerabilities.

Privilege Escalation

Control: Zero Trust Segmentation

Mitigation: Zero Trust segmentation enforced at the workload and network layer would likely reduce the ability of a compromised application instance to reach cloud metadata endpoints or internal credential stores, constraining the escalation path from application-layer access toward cloud control-plane permissions.

Lateral Movement

Control: East-West Traffic Security

Mitigation: East-west traffic enforcement across cloud environments would likely reduce the ability of compromised workloads to freely communicate with adjacent cloud services or account resources, constraining lateral pivot paths that relied on static CI/CD tokens and unfiltered cross-environment connectivity.

Command & Control

Control: Multicloud Visibility & Control

Mitigation: Multicloud visibility and control over outbound traffic destinations would likely surface anomalous high-frequency communications to unexpected external LLM infrastructure, potentially enabling policy enforcement that could constrain the ability of compromised workloads to maintain reliable orchestration callbacks to attacker-controlled endpoints.

Exfiltration

Control: Egress Security & Policy Enforcement

Mitigation: Enforcing egress policies that restrict which external destinations AI application workloads are permitted to reach over HTTPS would likely reduce the ability of compromised services to transmit harvested credentials and secrets to attacker-controlled pooling infrastructure, constraining the exfiltration paths available to ARTEX agents.

Impact (Mitigations)

Where prior segmentation, east-west enforcement, and egress controls would have constrained attacker reach, residual impact would likely be scoped to workloads and credentials already reachable within breached segments, reducing the breadth of unauthorized AI inference consumption and limiting credential pooling to a narrower set of harvested keys.

Impact at a Glance

Affected Business Functions

  • AI Inference and Model Gateway Operations
  • Cloud Credential and Secret Management
  • CI/CD Pipeline Integrity
  • Third-Party API and SaaS Integration Security
Operational Disruption

Estimated downtime: 7 days

Financial Impact

Estimated loss: N/A

Data Exposure

Mass harvesting of AI provider API keys (OpenAI, Anthropic, and similar inference providers) stored in exposed LLM gateways and proxy applications including LiteLLM, One API, New API, Dify, FastGPT, Langflow, RAGFlow, Open WebUI, LobeChat, and Ollama. Cloud credentials including managed AI service identities and secret store contents were targeted. CI/CD tokens with broad account-level permissions were compromised enabling database dump attempts across customer environments. Hundreds of targets were enumerated across AI app platforms. Stolen keys were immediately weaponized to fund further attacker AI inference workloads, generating unauthorized compute spend for victims. Additionally, a secondary campaign involved deepfake-based identity bypass attempts at cryptocurrency exchanges, posing risk to customer identity verification data. Personal information on approximately 67,000 individuals was reported stolen in a related South Korean financial sector campaign attributed to the same ARTEX tooling.

Recommended Actions

  • • Apply CNSF Egress Security and Cloud Firewall (ACF) controls with FQDN-based filtering to block unauthorized outbound connections from AI application workloads to unknown or attacker-controlled LLM endpoints, preventing exfiltration of harvested API keys and stopping agent callback communications to external orchestrators.
  • • Deploy Zero Trust Segmentation and East-West Traffic Security to enforce least-privilege, identity-based policies between AI gateway services, model inference endpoints, and cloud management planes, ensuring that a single compromised AI app cannot be used to pivot into secret stores, CI/CD systems, or adjacent cloud accounts.
  • • Enable Multicloud Visibility and Control with centralized traffic observability to baseline normal AI application behavior and generate alerts on anomalous patterns such as high-frequency API scanning (69+ req/min), mass database dump requests, sudden new workload deployments matching artex-* naming patterns, or unexpected cross-account token usage.
  • • Enforce Egress Security policies requiring all AI inference traffic to exit only through approved, policy-controlled paths with application-layer inspection, preventing agents from using compromised keys to reach premium AI model services or cloud metadata endpoints via SSRF, and blocking outbound traffic to unauthorized destinations flagged as shadow AI or attacker infrastructure.
  • • Leverage the Cloud Native Security Fabric (CNSF) with inline enforcement and real-time inspection to detect agentic AI tool behaviors including automated credential scanning, LLM-guided task orchestration traffic, and prompt injection patterns at the network layer, while enforcing runtime policy that restricts AI application containers and Kubernetes pods from accessing environment variable stores, source maps, or unauthenticated management endpoints.

Secure the Paths Between Cloud Workloads

A cloud-native security fabric that enforces Zero Trust across workload communication—reducing attack paths, compliance risk, and operational complexity.

Cta pattren Image