Chronicle/Attacks & incidents

DIVD reports agent activity after root access in its Zammad breach

AttackIncidentSignificance assistant-drafted

DIVD’s case overview, updated October 9, says attackers breached its Zammad ticketing system on September 21 using two zero-days, gained root access, and then used AI agents for further activity. It reports detection after 19 minutes, a first response after 19 hours, and a further nine hours to execute containment. Its data overview reports signs of partial exfiltration in several environments and no signs of compromise in others; the investigation remains open and the agent attribution is DIVD’s own assessment.

Why it matters

It separates rapid detection from response and containment, while clarifying when DIVD says agents entered the attack and which data-exposure judgments remain preliminary.

Key facts

As stated in the sources, with where to find them.

  • DIVD’s October 9 case overview says initial access occurred through two Zammad zero-days on September 21 and AI agents were used after the attacker elevated to root. It bases agent attribution principally on the volume and speed of activity and documented scripts whose comments appeared to communicate between agents. This remains the victim’s assessment during an open investigation.Case DIVD-2026-00014, What we know sofar
  • DIVD reports a mean time to detect of 19 minutes, a mean time to respond of 19 hours and a mean time to contain of nine hours. Its narrative says the first response produced a containment plan and execution took a further nine hours, including team travel and careful network isolation. These are the victim’s metrics for this incident, not a measured average across attacks.Case DIVD-2026-00014, What we know sofar; Metrics
  • The case overview says Zammad fixed the two flaws in releases 7.2 and 7.2.2. The separately maintained vulnerability page, last modified October 1, lists affected versions and advises upgrading to Zammad 7. This record distinguishes the later incident overview from that older advisory rather than treating their version wording as synchronized.Case DIVD-2026-00014, What we know sofar; case DIVD-2026-00015, Summary and recommendation
  • The data overview reports preliminary signs of partial exfiltration in the office environment, IT support, project support and operational system data, with investigation or analysis still ongoing. It reports no signs of compromise for HR, Slack and source-code repositories, and says the separate CVE/CNA environment has no indication of access. These categories are not all final assessments.Overview of data investigation, Data about volunteers; Core business data
  • DIVD says email addresses were exfiltrated and volunteer contact details possibly were. It says the CSIRT ticketing system held incoming messages and replies, that only part of the information was extracted, and that correspondents should assume their exchanges may be exposed while the extent is investigated. Externally handled accounting and bank systems have no indication of compromise.Overview of data investigation, Current picture sections
  • The case timeline lists collaboration with Merlon Security after detection, notification of affected parties, a police report on October 5, and a data-investigation overview first published on October 1 and updated on October 9. The source-list date for that overview identifies the cited revision.Case DIVD-2026-00014, Timeline
  • September 30 press reports quote DIVD saying the combined flaws allowed root access in seconds and attribute this speed to the agentic component. The October 9 case overview describes agent use after root access; it does not independently establish that agents performed every initial exploitation step.BleepingComputer, September 30; SecurityWeek; case DIVD-2026-00014, What we know sofar

Findings that cite this record

Key questions this bears on

Sources

Related records