The Incident Board.

Documented AI security incidents.

Case 22Cairn / exposed agent panels

Open Cairn control panels showed AI agents breaking into company websites, including Deere and SharkNinja

An operator's open Cairn control panels let NorForge watch AI agents attack online shops. Reuters reports the researcher saw break-ins at more than 100 companies, including Deere and SharkNinja.

Affected system
E-commerce websites in the United States, Canada, Japan and Australia
Case status
Victim count unverified
Sources checked

Overview

From September 25, 2026, a Chinese-speaking criminal operator used Cairn, an open-source AI agent platform, to send AI agents against online shops in the United States, Canada, Japan and Australia with the goal of running code on each site and planting a file-upload web shell. The operator left its own Cairn control panels open on the internet, which let the security firm NorForge watch the agents work; NorForge published its findings on October 19, and Reuters, which reviewed the operator's Cairn activity itself, reported that the researcher watched the operator break into websites of more than 100 companies, including Deere, SharkNinja and Cummins. The case matters because one operator directed more than 1,100 largely autonomous intrusion tasks in about two weeks, at a token cost NorForge estimates at about $5 per task. Separately, NorForge said exposed Cairn panels across the broader set it examined contained target and client secrets, but it did not attribute all of those secrets to this operator. Status: open, sources checked November 6, 2026. Severity: Serious (3/4), because affected companies acknowledged compromises and NorForge found planted web shells live on victim sites, while data theft by this operator is not established and the scale figures rest on agent self-reports and one researcher's count. (NorForge; Reuters via CP24)

Reported impact

Reuters reported that the operator "broke into websites belonging to more than 100 companies" and that its agents had attempted more than 1,200 sites by late in the week before October 19. NorForge's own report gives a smaller and differently defined count for the cluster it calls AIA0001: 1,139 Cairn projects (one project is one target and goal) created between September 25 and October 9, of which 96 recorded a "substantive outcome" claim. Those outcomes are what the agents reported, not independently checked break-ins. NorForge says it confirmed a live web shell at one large hardware parts vendor and validated the attack chain at one very large US retailer. (Reuters via CP24; NorForge)

Three named companies responded to Reuters. Deere said it had taken "necessary remediation actions" and had "no indication that sensitive information was accessed." SharkNinja said the hack hit a standalone site carrying only product support information and that the threat was contained. Cummins said it was "investigating the report of a potential cyber-attack on a website operated by one of our third-party vendors." Two smaller businesses also acknowledged being compromised. Reuters said it "could not ascertain the degree to which the breaches resulted in unauthorized extraction of data." (Reuters via CP24)

What happened

Cairn takes a starting point and a goal and dispatches AI agent "workers" that record findings on a shared board until the goal is met; its public code supports Claude Code, Codex and Pi as worker software. NorForge, following a September Gambit Security report that found Cairn on a criminal's staging server, used the internet scanning services Shodan and Censys to find Cairn web panels. Reuters reports that NorForge's researcher Snorre Fagerland began finding malicious instances around October 2. NorForge judged more than 20 panels likely malicious and grouped them into three clusters. (NorForge; Cairn repository; Reuters via CP24)

The busiest cluster, AIA0001, wrote in Chinese and ran 14 panels. NorForge says an automated pipeline fed it targets. A typical task described them as e-commerce sites in four countries with claimed traffic of 200,000 to 1.5 million and said the browser-automation tool Playwright had checked that orders could be placed. The same task told the agents to find unauthenticated remote code execution (by SQL injection, unsafe deserialization, file upload or similar flaws), to prove it with whoami or id output, and then to plant an "uploader shell," a form that saves uploaded files rather than one that runs commands. NorForge says the aim appeared to be lasting access to shop and payment systems for later use. All AIA0001 tasks it saw ran on a worker named claudecode_deepseek-v4.1-flash, which NorForge says "could mean" Anthropic's Claude Code agent software driving DeepSeek's V4.1 Flash model; Reuters says the campaign "appeared to be using a mixture of China's DeepSeek and Anthropic's Claude Code." Neither source shows whether any Anthropic model processed the requests. Successful AIA0001 tasks took a little under 23 hours on average. (NorForge; Reuters via CP24)

The two other clusters were smaller. AIA0002 wrote in English, ran 10 panels and 71 projects, and told agents to steal credit cards and cryptocurrency; NorForge says its workers used DeepSeek models through the OpenRouter gateway. AIA0003, rated malicious only with low confidence, ran one panel with 59 projects. Reuters reports that one of the observed actors stole "a trove of credit card data"; it does not say which cluster. The "$50 per successful hack" figure is Fagerland's estimate to Reuters of about $5,000 in tokens divided by the successful break-ins; NorForge's written estimate is about $5 per task including failed ones, with "considerable" uncertainty. (NorForge; Reuters via CP24)

How the boundary failed

Operator's automated pipeline ranks shops by traffic, checks them with Playwright
  -> creates Cairn project: goal = unauthenticated code execution, then uploader web shell
  -> Cairn dispatches worker "claudecode_deepseek-v4.1-flash"
     (model mix reported as Claude Code + DeepSeek V4.1 Flash; not confirmed)
  -> agents probe the target site for hours: SQL injection, deserialization,
     file upload, authentication bypass
  -> agent reports code execution and a planted uploader web shell   [agent claim]
  -> NorForge finds the shell live / chain valid in a few cases        [checked sample]
  -> later use of the access or data taken                              [unknown]

Separately:
Operator's Cairn panel reachable from the internet with no login (port 8000)
  -> targets, findings, harvested credentials and API keys readable by anyone
  -> after October 19, third parties deface and take over exposed panels

Two boundaries failed. The first is on the victims' side: in the few cases NorForge checked, shop software let an unauthenticated visitor install a shell or run code on a web server. NorForge's one detailed example, by the agent's own account, combined write access to a memcached session store with unsafe PHP object deserialization in old Zend Framework components. The techniques NorForge lists (SQL injection, deserialization, file upload, authentication bypass) are established web-attack classes; what its evidence shows is agents working through them for hours with little human input. (NorForge)

The second failure is on the operators' side. "Exposed Cairn panels" means the attackers' own control panels, not someone else's deployment. NorForge says the panels appeared to give any visitor the controls to start, stop or redirect agent tasks. It did not test those controls; its follow-up reports that others did and used them to plant SSH keys and malware on Cairn hosts. Cairn's recommended Docker Compose setup publishes its web server on port 8000 on all network interfaces. The server code reviewed for this record contains no login check, although the manual cairn serve command listens only on the local machine by default. NorForge also found legitimate penetration-testing firms with client work on open panels. Of the hundreds of secrets it found in panel data, the scanner Trufflehog verified 11% as valid. (NorForge; NorForge follow-up; Cairn repository)

Consequences

Confirmed effects are narrower than the headline count. SharkNinja and two smaller businesses acknowledged compromises, and Deere told Reuters it had taken remediation actions. Cummins's statement concerns a website run by a third-party vendor, not its own systems. NorForge confirmed the outcome in a few cases: a live web shell at one hardware parts vendor, a command shell at one Australian e-commerce site and a validated chain at one very large US retailer. (Reuters via CP24; NorForge)

NorForge assessed that AIA0001 sought access rather than immediate theft, and noted that an uploader shell could later be replaced with something more harmful. Whether the operator used the access after the panels went offline on October 20 is unknown. Across all three clusters, NorForge's figure lists 134 projects with outcome claims. Of those, 28 were described as database access or data exfiltration and 9 as payment card data. The figure does not split these by cluster, so it does not show that AIA0001 took data. (NorForge; NorForge follow-up)

The open panels caused a second exposure: credentials and API keys gathered from targets sat in publicly readable panel data. After publication, unknown actors took over open Cairn hosts, including some belonging to red teams. NorForge did not establish whether victims' exposed credentials were reused. (NorForge; NorForge follow-up)

Vendor response

Cairn's author acknowledged a Reuters message but did not immediately answer its questions. In a post on X relayed by Reuters, the author said the platform was "an innovative type of multi-agent architecture and was not designed for hacking attacks. If it is used to carry out harmful hacking attacks, that is not my intention." The X post was not read directly. The repository's README disclaimer limits use to systems where the user has "explicit authorization to operate." As of November 6, the latest commit on the repository's main branch was dated September 7, 2026, so no code or documentation change there followed the disclosure. (Reuters via CP24; Cairn repository)

NorForge says it worked with Reuters to notify victims and asked hosting providers to take panels down; it said success depended on the hosts. It did not report whether any provider acted, and it does not attribute the October 20 disappearance of the AIA0001 panels to a takedown. Searches through November 6 found no public statement on this case from Anthropic, whose Claude Code software may have served as the agent harness, or from DeepSeek. The affected companies' statements appear only as given to Reuters. The searches conducted for this record found no company notice; SEC EDGAR filings were not searched. (NorForge; NorForge follow-up)

Official oversight

Checked November 6, 2026, for the United States, United Kingdom, Canada, Norway, Japan and Australia (victim and researcher locations).

Authority Action on this incident Status / basis Next step Official source
U.S. CISA and FBI No incident-specific public action found in CISA's news and advisory feeds (latest items November 5, 2026) or the FBI IC3 public service announcements page as of November 6, 2026. The FBI press-release page returned HTTP 403. Scoped absence finding; not proof of inaction. Watch for an advisory on exposed AI agent panels or e-commerce web shells. CISA news and advisory feeds; IC3 PSA page
UK NCSC No incident-specific public action found in the NCSC all-content feed or its November 3, 2026 AI threat assessment as of November 6, 2026. Scoped absence finding. None announced. NCSC all-content feed
Canadian Centre for Cyber Security; Norway NSM No incident-specific public action found in the Cyber Centre alerts feed or NSM news page as of November 6, 2026. Scoped absence finding. None announced. Cyber Centre alerts feed; NSM news page
JPCERT/CC On October 23, 2026, JPCERT/CC updated advisory JPCERT-AT-2026-0030 with a case on attack attempts abusing Cairn and other AI penetration-testing platforms. It listed suspicious source IP addresses, cited NorForge and asked organizations to check for related access. Public technical advisory, not an attribution, investigation finding or confirmation of the named victims in this record. Monitor later revisions and incident reports. JPCERT/CC advisory
Australian Signals Directorate's ACSC Not checked: the alerts page timed out twice on November 6, 2026. Unchecked. Recheck, since Australian shops were targeted. ACSC alerts page (unreachable)

General policy context, not a response to this case: on November 3, 2026, the UK NCSC published an assessment of AI-enabled intrusion through 2028 and judged that many systems would almost certainly remain vulnerable to AI-cyber tools that identify and exploit system weaknesses. (NCSC)

What remains open

Established in this record

NorForge's primary report and its figures document one operator running 1,139 agent tasks against e-commerce sites between September 25 and October 9, 2026, with the stated goal of code execution and a planted web shell. Reuters independently identified victims from the operator's Cairn data and obtained statements from Deere, SharkNinja, Cummins and two smaller businesses. SharkNinja and the two smaller businesses acknowledged compromises, Deere described remediation, and Cummins said it was investigating a report about a website run by a third-party vendor. The panels belonged to the attackers and were open because they had no login protection. After disclosure, others took over open panels. (NorForge; Reuters via CP24; NorForge follow-up)

Still unknown

How did Reuters reach "more than 100 companies" when NorForge's figure shows 96 AIA0001 projects with outcome claims, and projects are not the same as companies or confirmed break-ins? Did any Anthropic model process the operator's requests, or did Claude Code only serve as the harness around DeepSeek? Did AIA0001 use its web shells, or take data, before or after its panels went offline on October 20?

Next reporting step

Seek NorForge's method for the Reuters victim count and its list of verified intrusions; any Reuters follow-up or correction; notices from SharkNinja, Deere or the vendor that ran the Cummins-linked site; a statement from Anthropic on whether its models were used; hosting providers' takedown responses; later revisions of the JPCERT/CC advisory; and an ACSC recheck. No outreach has been sent.

Record updates

  • November 6, 2026: Initial source-checked record published as IB–2026–022. Read NorForge's October 19 report and October 26 follow-up in full, the Reuters article through syndication (reuters.com returned HTTP 401), The Next Web and the Cairn source repository; checked U.S., UK, Canadian, Norwegian and Japanese official sources (Australia's ACSC timed out). Victim statements exist only as given to Reuters; the 100-company count, model use and data theft remain unverified.

How we assess impact

The four-step scale is an editorial assessment of documented impact, not a technical vulnerability score or a probability forecast. Each brief explains its rating; unknown impact is not counted as zero harm.

  1. 1 / LimitedA bounded failure with no demonstrated external impact.
  2. 2 / MaterialDisruption or unintended changes outside the intended task.
  3. 3 / SeriousThird-party compromise or sensitive-data access.
  4. 4 / CriticalDemonstrated widespread or severe harm.

Source counts measure linked documents, not independent corroborations. Case IDs identify this publication’s records.

Read our methodology