ARTEX hack of the DIVD data center:two Zammad zero-days, root in 12 minutes.
DIVD, the Dutch Institute for Vulnerability Disclosure, published a running account of how an attacker got into its data center on 2026-09-21. On that page DIVD says an agentic AI attacker was involved and that, based on facts, ARTEX was used.
- When
- Attack 2026-09-21; ARTEX named in an update at the end of October
- Reported by
- DIVD (case DIVD-2026-00014)
- Scope
- DIVD data center systems and some volunteer data
- ARTEX role
- Identified by DIVD as the framework used
What happened
DIVD says that on 2026-09-21 an attacker got into its data center through two previously unknown vulnerabilities, zero-days, in Zammad, the helpdesk software behind its CSIRT. DIVD detected malicious activity within 19 minutes and blocked access to all data center systems, then shut down and rebuilt them. It reported the flaws to Zammad, which fixed them in versions 7.2 and 7.2.2, and filed a police report. The page lists CVE-2026-102489 and CVE-2026-102490, and describes one flaw as a session hijack leading to remote code execution and the other as a local privilege escalation to root.
Part of the data was exfiltrated. DIVD says user data of its volunteers got out, such as email addresses and possibly contact details, and that its separate CVE and CNA environment runs apart and shows no sign of access. It later declared itself contained and kept publishing updates and a case file.
The attackers also tried to reach DIVD's providers. DIVD says BIT B.V., which hosts the mailbox behind its ticketing system, saw the mailbox snooped on but was not impacted further, and that one other provider was affected, which DIVD leaves that provider to describe.
How ARTEX was involved
In an update dated 31 October 2026 DIVD wrote that, with its investigation nearly finished, it can say based on facts that ARTEX was used in the hack. Earlier it had noticed a modus operandi that pointed to agentic AI: the attacker's scripts held notes where the agent justified its own actions.
DIVD lists these details from its logs: the attack was split into small jobs labelled with an i and a sequential number, the first step of every job was testing whether its zero-day still worked, the agent created an admin API token for itself with no expiry date, it went from initial access to root in about twelve minutes, and it used more than 2,500 scripts where DIVD says a human attacker needs twenty or thirty. DIVD calls the activity loud and messy.
DIVD adds that ARTEX has been in the news for other attacks, which does not mean those attacks are connected. To prevent speculation it does not share information about the attacker, and it gave that to the authorities.
Confirmed and alleged
Reported as observed
- First access on 2026-09-21 through two Zammad zero-days, detected within 19 minutes (DIVD).
- Zammad fixed the flaws in versions 7.2 and 7.2.2 (DIVD).
- Volunteer user data was exfiltrated, and DIVD identified ARTEX as used in the attack (DIVD).
Alleged, assessed or unclear
- DIVD has not named the attacker, and this site does not speculate.
- DIVD does not say which copy or fork of ARTEX was used.
- The investigation was still running when DIVD published. It promised a final report, an agentic deep dive and a data overview later.
Takeaways for defenders
Drawn from what the sources themselves recommend or observed. Not a complete checklist.
- DIVD: update Zammad to version 7 or later, or take the instance offline.
- DIVD credits proper network segmentation and its incident response team with stopping the attackers from going deeper.
- Assume that attackers have any correspondence that was emailed to the DIVD CSIRT mailbox, DIVD says.
- Details DIVD published that may help detection: the job labels of an i plus a sequential number, artifact names such as artex-i13033 and ARTEX_i13444_CVE2019, and an admin API token created with no expiry.
- DIVD plans to publish its redacted research data in a public repository so the community can look for earlier detection signals.
Sources
Every claim above comes from these pages or from this site's news data. Open them for the full reports.
- DIVD hacked: updates, CSIRT case DIVD-2026-00014 and reports
DIVD (divd.nl), 2026-10-31
Related pages
Related incidents
Follow the ARTEX story.
New forks, releases and reports, dated and sourced.
