AI Agent Attackers Bring Patience, Not Genius: A Defender Checklist From the Cairn Case Amazon Threat Intelligence reported that a China-nexus actor used the open-source Cairn multi-agent penetration-testing framework to find a zero-day in MONAI Label and gain root on a server in about 11 minutes, while failing across roughly 16 hours and 148 actions against a Redis server and 30,000 login attempts against a GPU server. The campaign, attributed with moderate confidence and targeting East Asian universities over about 48 hours in September, was traced to an exposed Cairn console left without authentication. The instruction was three words long: "obtain shell access." That was the goal an attacker gave to a set of AI agents in September, according to Amazon Threat Intelligence https://aws.amazon.com/blogs/security/chinese-nexus-actors-cairn-ai-agents-found-a-zero-day-on-their-own/ . The agents planned their own steps, tried them, and changed course when something failed. Against one target they found an unknown bug a zero-day and took over the server as root. Against two others they worked for hours and got nothing. Both halves of that story matter. The win shows how fast an agent can move. The failures show what still stops it. This article walks through what Amazon reported, adds related reports from the past few months, and turns it into a checklist you can run against your own servers this week. A note on sources: everything below comes from the published reports linked in each section. I have not run Cairn or reproduced the attacks. The code samples are illustrations written for this article. They follow the bug class described in the advisory and were checked only against small synthetic inputs. On September 10, 2026, Amazon found a server running a public copy of Cairn with no login. Cairn is an open-source framework that coordinates several AI agents for penetration testing authorized hacking to find weaknesses . It was built for defenders. You give it a starting point and a goal in plain language, and the agents look for a path to that goal. Because the operator left the console open, anyone on the internet could read its history. That included project settings, the operator's prompts and the AI output. The prompts were in Simplified Chinese and the script timestamps used China Standard Time. Amazon attributes the campaign to a China-nexus actor with moderate confidence. The targets were IP addresses linked to universities in East Asia outside mainland China, over about 48 hours starting September 8. Amazon published the findings on November 20. Three operations stand out. Redis: 16 hours, 148 actions, no success. The agents went after a Redis server an in-memory database that allowed access without a password. Over roughly 16 hours and 148 sequential actions, they worked through known Redis takeover methods. These included abusing replication to load code, escaping the scripting sandbox, writing to config files and corrupting memory. They also tried Log4Shell against another service on the same machine. Next they used a server-side request forgery bug SSRF, where a server is tricked into making requests for you in a Qdrant instance to map the internal Docker network. Then they sprayed passwords at PostgreSQL, SSH and other services. None of it worked. A GPU server: 6 hours, 30,000 logins, no success. The agents built a list of about 80 real usernames from the university's public pages, such as faculty directories, lab sites, archived pages and papers. They then tried more than 30,000 username and password combinations. The targets were SSH, an admin dashboard, a storage device, a VPN server and the campus portal. They never found a working login. MONAI Label: 11 minutes to file write, then root. The third target ran MONAI Label, an open-source tool that helps researchers label medical images with AI. The agents identified the framework, mapped its API, and found an upload endpoint that took a filename parameter. They tested it for path traversal using ../ in a name to escape the intended folder , and it worked. Amazon says the agents went from mapping the API to writing arbitrary files in about 11 minutes. In a later session, the agents used the same bug to write a Python reverse shell into sitecustomize.py . Python imports that file automatically every time the interpreter starts, as the site module docs https://docs.python.org/3/library/site.html explain. The agents then called a training API endpoint, which started a new Python process. That process loaded the payload and opened a reverse shell running as root. After that, a human stepped in. The operator gave the agents a proxy into a second university network that ran the same vulnerable software, and pointed them at other machines there. Amazon reported the bug to the maintainers. The GitHub advisory GHSA-qc22-rmgc-vg94 https://github.com/Project-MONAI/MONAILabel/security/advisories/GHSA-qc22-rmgc-vg94 , rated critical and published November 18, describes it like this: PUT /datastore/image takes an image query parameter and uses it as the image ID without checking it. ../../../tmp/x writes the file anywhere the server process can write. PUT /datastore/label builds its path the same way. MONAI LABEL AUTH ENABLE=False , so any client that can reach the server can use the bug. The fix pull request 1915 https://github.com/Project-MONAI/MONAILabel/pull/1915 resolves each destination path and rejects anything outside the datastore. It also cuts the image ID down to its base name and rejects empty or dot-prefixed IDs. The fix shipped in MONAI Label 0.8.6 https://github.com/Project-MONAI/MONAILabel/releases/tag/0.8.6 , a security release from November 22. Its notes list the bug as CVE-2026-133968, affecting all versions up to 0.8.5. The same release fixes a second path traversal in session uploads. Three other recent reports point the same way. GTIG also warns about the other side of this: a flood of AI-written exploits that are claimed to work but do not. That creates extra checking work for defenders. The agents did not invent new attack science. The Redis attempts were a list of known methods. The credential attack was a classic password spray with better username research. The MONAI Label bug was path traversal, one of the oldest bug classes on the web. What the agents added was patience and breadth: 148 actions against one server, 30,000 login attempts against another, and 11 minutes from API map to file write on a third. In Amazon's words, the agents "kept adapting for nearly a full day without human direction." What stopped them was ordinary hardening. Amazon calls the Redis server a "hardened" target even though it had no password. The report does not say which setting held, but 148 attempts did not get through. No password in the 30,000 tries worked. The one success came from software that ships with authentication off by default and wrote files without checking paths. That gives a practical rule. You cannot out-wait a machine, so do not depend on the attacker getting bored. Remove the easy wins, and make your detection fast enough to act before a human would have even read the alert. Amazon's own advice is to "prioritize high-confidence detections that trigger automated response, with humans overseeing outcomes rather than reviewing every individual action." Count the unauthenticated services in this story: an open Redis, a MONAI Label server with auth off by default, and the attacker's own Cairn console. Start by listing what you expose. For Redis, a quick test from a machine outside the server: redis-cli -h