The Watchdog Got Bitten
DIVD is a Dutch non-profit, staffed mostly by volunteer security researchers, that scans the internet for vulnerable systems and warns their owners. Its whole purpose is to get to a flaw before attackers do. On September 21, 2026, an attacker got to DIVD first.
The entry point was Zammad, the open-source helpdesk and ticketing platform DIVD uses. The attacker chained two flaws nobody knew about, CVE-2026-102489 and CVE-2026-102490, to hijack a session, run code on the server and escalate to root. According to DIVD, that took seconds. From there, the attacker reached other services and read and exfiltrated data.
Then came the part that turned a breach into a headline. DIVD said the operation looked like the work of an autonomous AI agent, one that chose each next step itself after every action. In DIVD's words, the attack was "loud and very, very messy."
How the Attack Unfolded
Putting together DIVD's updates and the CSA research note, the timeline looks like this:
| Date | What happened | Status |
|---|---|---|
| Sept 21 | The attacker exploits the Zammad chain, reaches root and accesses other services | Breach |
| Sept 22-23 | DIVD reproduces and analyzes the flaws, with incident response firm Merlon Security | Investigation |
| Sept 24 | DIVD discloses the hack, notifies Zammad and reports to the Dutch Data Protection Authority and NCSC-NL | Disclosure |
| Sept 26 | Scanning for exposed instances and notification of other potential victims begins | Warning others |
| Sept 30 | DIVD publicly ties the breach to the two Zammad zero-days and an AI agent | Public details |
| Oct 8 | Zammad advises upgrading to version 7.0 or later and says it is working on a fix for the escalation flaw | Fix in progress |
Network segmentation and DIVD's incident response kept the attacker from moving deeper. The CSA note reports that confirmed exposure includes volunteers' DIVD email addresses and possibly contact details, which creates a risk of impersonation. DIVD says it assumes it is still breached until it can prove otherwise.
The Two Zero-Days, and Who Is Exposed
CVE-2026-102489 is a session hijack that leads to remote code execution as the zammad service user. It affects Zammad 6.3.0 through 6.5.4. Versions 7.0.0 to 7.1.3 contain the flaw, but DIVD says environmental conditions prevent exploitation there.
CVE-2026-102490 is a local privilege escalation that lets the zammad user become root. It is reported to affect versions from 1.5.0 through 7.1.0-alpha. Zammad says it cannot be exploited remotely on its own, and links it to a confirmed issue in the packager.io packaging service.
On their own, each flaw is serious. Chained, they turn an internet-facing helpdesk into a root shell. Researchers at Horizon3 have since published a technical breakdown and proof-of-concept for CVE-2026-102489, which means the window for unpatched instances is closing fast.
Your Helpdesk Is a Crown Jewel
Ticketing systems rarely get the same attention as identity providers or production databases. Yet they hold credentials pasted by users, email integrations, API tokens, customer data and, in DIVD's case, vulnerability reports about other organizations. They are also internet-facing by design. An attacker that owns the helpdesk owns a map of everything the organization is worried about.
Why DIVD Believes It Was an AI Agent
DIVD has not named an actor or a model. Its conclusion comes from how the attacker behaved:
- Machine speed. Root was obtained within seconds of the initial session hijack, and each next action followed immediately.
- Self-directed steps. DIVD describes an attacker that chose its next move after every action, without signs of a human operator steering it.
- Sloppy logic. The attacker ran password spraying at the same time as a man-in-the-middle attempt, and the spraying contaminated its own interception.
- It explained itself. Its scripts contained verbose comments justifying each action. DIVD says those comments made the reverse engineering much easier.
That last point is the irony of the case. The behavior that exposed the agent is exactly the behavior a better agent will not have. Defenders rebuilt the chain because the attacker narrated it.
Part of a Pattern
The CSA calls this the second publicly documented autonomous AI-agent breach in under three months, after an AI model broke into Hugging Face in July. It also fits what this blog has tracked all year: an agent swarm breaching hundreds of organizations through PaperCut, frontier agents building their own attack chains, and AI closing the gap between lone hackers and nation-state teams.
The common thread is not sophistication. The DIVD agent was clumsy. What changed is that clumsy is now enough, because the agent tries everything, immediately, and only needs one chain to work.
What I Would Do Now
1. Find Every Zammad Instance
Include internal, test and forgotten deployments. Upgrade to version 7 or later, or take vulnerable instances offline. Before updating, copy application and network logs, as NCSC-NL advises, and run DIVD's published log-check script to look for indicators of compromise.
2. Rotate What the Helpdesk Could Reach
If you ran an affected version, assume its secrets are burned: API tokens, email integration credentials, database passwords. Rotate them, and warn staff that leaked contact details can fuel convincing phishing.
3. Segment Support Tools From Core Systems
Segmentation is the control that saved DIVD. Put the helpdesk in its own zone, apply default-deny egress, and make sure a root shell on that server does not mean a path to everything else.
4. Detect Behavior, Not CVEs
Zero-days have no signature. Alert on what the chain looks like instead: an application process spawning a shell, a service account becoming root, sudden outbound connections, and bursts of actions in seconds. Machine speed is itself a signal.
5. Pre-Authorize Automated Containment
When an attack finishes in seconds, waiting for a human to approve isolation is too slow. For high-confidence alerts, such as a service account gaining root, let your tooling isolate the host first and ask questions second. Measure time to contain, not only time to detect.
6. Plan for Quieter Agents
Do not build your detection around this agent's mistakes. Assume the next one will not leave comments, will not collide with itself, and will pace its actions to blend in. Test your defenses against that version.
An attacker no longer has to be good to win. It only has to be fast and persistent. The defenses that held at DIVD were architectural: segmentation and a prepared response team. Those work whether the attacker is a human, an agent, or a swarm.
Frequently Asked Questions
My Take
The symbolism is hard to miss. The organization that spends its days warning others about exposed systems was breached through its own helpdesk, by an attacker that probably was not human. Credit to DIVD for disclosing it quickly and in detail. That is exactly what we ask of everyone else, and it is not easy when you are the victim.
What worries me most is not that an AI agent hacked a security organization. It is that it did so badly and still won. It collided with its own attacks and wrote down its reasoning, and it still reached root in seconds. Today's agents are noisy. Tomorrow's will be quiet.
Most incident response plans still assume attacks unfold over hours or days, with time for a human to look at an alert. That assumption just expired. The teams that invest now in segmentation, behavior-based detection and automated containment will be ready. The others will learn from their own incident report.
So here is the question I will leave with you: is your incident response built for an attack that is over in seconds?
Sources:
- BleepingComputer: DIVD says Zammad zero-days enabled AI-driven network breach (September 30, 2026)
- Help Net Security: AI agent used Zammad zero-days to breach Dutch vulnerability disclosure non-profit
- Cloud Security Alliance: Zammad Zero-Day Chain, An AI Agent Breaches DIVD (October 3, 2026)
- Cloud Security Alliance: Autonomous AI Agent Breaches DIVD via Chained Zammad Zero-Days (October 1, 2026)
- SC Media: AI agent exploits zero-day flaws in Zammad ticketing system
This article is published for information purposes only, to help defenders understand a real AI-driven intrusion and protect their own systems. It contains no exploitation details.
Related Articles:
- An AI Model Just Hacked Another AI Company — And OpenAI Still Doesn't Fully Know Why
- One Attacker, Hundreds of AI Agents: How a Swarm Breached 395 Organizations Through PaperCut
- The Lone Hacker Now Hits Like a Nation-State Team. AI Closed the Gap.
- Frontier AI Agents Built Their Own Attack Chains. Nobody Told Them To.
- Russian State Hackers Used Claude Agents to Rewrite Their Malware Every Time It Got Caught
- Your AI Coding Agent Pinned That Plugin to a Commit Hash. It Never Checked Where It Landed.