Threat Actor Uses AI Agents to Automate Breach of 100+ Companies

AI Agents Used to Steal 600,000+ Credit Cards in Automated Attacks

HIGH
September 25, 2026
5m read
CyberattackData BreachMalware

Impact Scope

People Affected

600,000+ credit card records

Industries Affected

RetailHospitalityTransportationManufacturing

Geographic Impact

United States (global)

Related Entities

Organizations

Products & Tech

StrixCairnHermesOpenRouterDeepSeekKimiClaude

Full Report

Executive Summary

A sophisticated, financially motivated campaign has demonstrated the power of Artificial Intelligence as a force multiplier for cybercrime. According to research from cybersecurity firm Gambit Security, a Chinese-speaking threat actor utilized a suite of off-the-shelf AI agents to automate attacks against approximately 100 companies, resulting in the theft of over 600,000 valid credit card records from just two of the victims. The campaign, active since at least July 2026, highlights the low cost and high efficiency of AI-driven attacks, with the actor spending an average of only $25 per target. The AI agents handled the entire attack lifecycle, from reconnaissance to exploitation, data theft, and even data destruction, targeting high-profile victims in retail, hospitality, and aviation.


Threat Overview

The campaign, uncovered after the attacker inadvertently exposed their own operational server, showcases a significant leap in attack automation. The threat actor used a combination of AI orchestration frameworks—Strix for reconnaissance, Cairn for exploitation, and Hermes as a central coordinator—to manage the attacks at scale. These frameworks leveraged large language models (LLMs) accessed via the OpenRouter service, including China's DeepSeek and Kimi models, as well as an older version of Anthropic's Claude.

The AI was tasked with identifying vulnerabilities in target websites, crafting exploits, and executing them autonomously. This allowed the actor to compromise at least 27 companies in a single five-day period. The operation was not limited to simple data theft; the agents also deployed web skimmers (a form of Magecart attack) to capture payment data in real-time and, in some instances, executed destructive routines that deleted victim data and database backups.

Technical Analysis

The attack chain was almost entirely automated by the AI agent toolkit:

  1. Reconnaissance (Strix): The AI agent automatically scanned target websites, identified the technology stack, and probed for common vulnerabilities like SQL injection, XSS, and insecure direct object references (T1595 - Active Scanning).
  2. Exploitation (Cairn): Upon finding a vulnerability, the agent would autonomously craft and execute an exploit to gain initial access to the web server or database (T1190 - Exploit Public-Facing Application).
  3. Collection: The agent navigated the compromised system's database to locate and exfiltrate tables containing credit card numbers and other personally identifiable information (PII) (T1005 - Data from Local System).
  4. Persistence & Impact: In some cases, the agent deployed a web skimmer (JavaScript code) onto payment pages to capture new card data as it was entered by customers (T1529 - System Shutdown/Reboot). It also performed destructive actions, deleting data and backups to cover tracks or cause additional harm (T1485 - Data Destruction).

Impact Assessment

This campaign has had a massive impact, with over 600,000 credit card records stolen and as many as 100 companies breached. Victims include a Fortune 500 hospitality company, a major U.S. airline, and a large industrial supplies distributor. The financial losses from fraudulent transactions and regulatory fines (e.g., under PCI DSS) will be substantial. The low cost ($25.46 per scan) and high success rate demonstrate a scalable and highly profitable new model for cybercrime. The addition of destructive actions shows a malicious intent beyond pure financial gain, increasing the recovery cost and complexity for victims. Gambit Security is working with Cloudflare and the Shadowserver Foundation to dismantle the infrastructure, but the attacker has proven resilient.

IOCs — Directly from Articles

No specific file hashes, IP addresses, or domains were mentioned in the source articles.

Cyber Observables — Hunting Hints

Detecting autonomous AI agents requires focusing on the patterns of their automated activity:

Type
network_traffic_pattern
Value
High-volume, rapid-fire requests from a single IP to multiple pages.
Description
AI agents can scan a site much faster than a human, generating a high rate of requests.
Type
url_pattern
Value
Probing for common vulnerability patterns (e.g., ' OR 1=1--, <script>alert(1)</script>).
Description
Classic web vulnerability scanning behavior, but potentially executed with novel evasions generated by the AI.
Type
log_source
Value
Web Server Access Logs
Description
Look for user agents associated with AI frameworks or unusual toolkits.
Type
api_endpoint
Value
Outbound connections to AI API providers like OpenRouter.
Description
A compromised server making API calls to an LLM provider is a strong indicator of this type of attack.

Detection & Response

  • Web Application Firewall (WAF): A well-tuned WAF is the first line of defense, capable of blocking the scanning and exploitation attempts. Rules should be updated to detect AI-generated polymorphic attack strings. D3-ITF: Inbound Traffic Filtering is essential.
  • Behavioral Analysis: Deploy security tools that can detect anomalous behavior, such as a web server process suddenly initiating outbound connections to an AI service's API endpoint or executing database queries at an unusually high rate.
  • File Integrity Monitoring (FIM): Monitor payment page scripts and other critical website files for any unauthorized changes, which could indicate the injection of a web skimmer. D3FEND's D3-SFA: System File Analysis can detect these changes.

Mitigation

  • Secure Coding Practices: The ultimate mitigation is to develop secure web applications that are not vulnerable to common flaws like SQL injection. Follow OWASP Top 10 guidelines.
  • Egress Filtering: Block all unnecessary outbound traffic from web servers. There is rarely a legitimate reason for a public web server to initiate connections to external AI APIs.
  • Payment Processing Offloading: Use a third-party, PCI-compliant payment processor and an iframe-based solution. This ensures that sensitive credit card data never touches your servers, making them an unattractive target for this type of attack.
  • Backup Security: Ensure backups are stored in a separate, isolated environment and are immutable to protect against the destructive tactics observed in this campaign.

Timeline of Events

1
July 1, 2026
The AI-driven attack campaign is believed to have started.
2
September 10, 2026
A five-day burst of activity begins, during which at least 27 companies are compromised.
3
September 15, 2026
The five-day burst of compromises ends.
4
September 25, 2026
This article was published

MITRE ATT&CK Mitigations

Use a Web Application Firewall (WAF) to detect and block automated scanning and exploitation attempts.

Mapped D3FEND Techniques:

Implement egress filtering to block unexpected outbound connections from web servers to AI APIs or other external services.

Mapped D3FEND Techniques:

Securely configure web applications and servers, and offload payment processing to compliant third parties to reduce the attack surface.

Mapped D3FEND Techniques:

D3FEND Defensive Countermeasures

To defend against automated AI agents like Strix and Cairn, organizations must deploy an intelligent Web Application Firewall (WAF) with advanced rate limiting and behavioral analysis capabilities. Standard signature-based WAFs may be bypassed by AI-generated polymorphic payloads. A modern WAF can identify and block the rapid, systematic probing characteristic of an automated agent. Configure aggressive rate-limiting rules to temporarily block source IPs that exceed a high threshold of requests per second. Additionally, enable bot detection features that can distinguish between legitimate search engine crawlers, human users, and malicious automated tools based on interaction patterns, user-agent strings, and other heuristics. This provides a critical first line of defense against the reconnaissance and exploitation phases of the attack.

A key indicator of this specific attack is a compromised web server making outbound API calls to an AI service like OpenRouter. Organizations must implement strict egress filtering policies on their web server segments. By default, web servers should be denied all outbound internet access. Exceptions should be explicitly allowlisted on a case-by-case basis for legitimate purposes (e.g., accessing a software repository or a specific payment gateway API). There is almost never a legitimate reason for a public-facing web server to make arbitrary outbound API calls to a service like OpenRouter. Blocking this traffic at the network firewall would not prevent the initial compromise but could disrupt the AI agent's ability to function and exfiltrate data, providing a valuable detection and containment opportunity.

Timeline of Events

1
July 1, 2026

The AI-driven attack campaign is believed to have started.

2
September 10, 2026

A five-day burst of activity begins, during which at least 27 companies are compromised.

3
September 15, 2026

The five-day burst of compromises ends.

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Editorial Standards & Analyst Review

CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.

Tags

AIartificial intelligencecybercrimedata breachcredit card theftMagecartautomation

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.

⚡ Sigma Generator

Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.