DIVD Zammad volunteer-data incident

DIVD disclosed a compromise of its infrastructure and later confirmed volunteer data theft.

Last modified

Summary

  • Environment: Zammad and connected infrastructure
  • Operational impact: Datacenter access blocked during response
  • Financial impact: No incident cost established in the reviewed evidence
  • Record status: Developing record. Reviewed October 12, 2026; updated as evidence emerges.

What happened

DIVD disclosed a compromise of its infrastructure and later confirmed volunteer data theft. [2]

Impact

Exposed information included volunteer email addresses; additional contact details remained under investigation. [2]

DIVD’s investigation overview lists preliminary signs of partial exfiltration across office, helpdesk, project-support and operational systems. It also says some CSIRT correspondence was extracted; the extent remained unresolved. [1]

Timeline

  1. First access

    First malicious access recorded.

    [2]
  2. Detection

    DIVD blocked access after detection.

    [2]
  3. Public disclosure

    DIVD announced the compromise.

    [2]
  4. Data theft confirmed

    Volunteer-data exposure acknowledged.

    [2]
  5. Investigation overview updated

    The casefile timeline records an update to the data-investigation overview.

    [2]
  6. Briefing updated

    This briefing was last reviewed and updated on October 12, 2026.

Threat Group & Attack Vector

DIVD identified two Zammad zero-days enabling session hijacking, code execution and privilege escalation. [2]

Actors

  • No threat actor group has been identified in the reviewed public evidence.

TTPs

  • No specific MITRE ATT&CK technique is currently mapped for this case.

Response

DIVD blocked datacenter access, began external forensic work and notified Dutch authorities. [2]

DIVD reported no signs of compromise in HR, source-code repositories or Slack after technical investigation. Those findings are limited to the named environments. [1]