πŸ”’breach.co.nz Β· the NZ & Australia breach register πŸ›‘οΈ A Govern service
Register β€Ί πŸ‡¦πŸ‡Ί AU β€Ί Technology
Technology sector Β· leaderboard
Own the Technology leaderboard
The top banner across the Technology overview and every Technology record β€” one advertiser, exclusively.
Own this leaderboard β†’ breach@govern.co.nz

ZircoDATA

πŸ‡¦πŸ‡Ί Victoria Β· ZircoDATA Pty Ltd Β· Record AU-2024-0222
β—‹ Reported β€” awaiting official confirmation
Reported β€” awaiting official confirmation. The facts below are drawn from the organisation's own disclosure and credible reporting. Figures are as reported; unknowns are labelled, not estimated by us.
People affected
Not disclosed
Breach date
2024-02
Regulator
OAIC and ACSC (notified); OVIC for Victorian public-sector clients
Trust tier
B Β· Reported
TimelineDisclosed within the same month after the breach (dates as precise as the sources allow)
Breach
Feb 2024
Disclosed
Feb 2024
Disclosed β€” no regulator outcome yet
as of 7 Nov 2026
Share this record in Β· Share on LinkedIn ⬇ Download share card

Data exposed

Home Affairs Free Translating Service client data: full names, dates of birth, mobile and email; visa, driver-licence and passport data (confirmed by the affected client organisation, not ZircoDATA) Company-confirmed
Archived Monash Health records from its family-violence and sexual-assault support units, 1970–1993 (confirmed by the affected client organisation, not ZircoDATA) Company-confirmed
Melbourne Polytechnic: about 60,000 students' low-risk identity attributes β€” ~60,000 Media-reported

Confidence: Confirmed = regulator/court Β· Company-confirmed = the organisation's own disclosure Β· Media-reported = press. Figures without an official source are labelled, not estimated.

What happened

In February 2024 the records-management supplier ZircoDATA disclosed a ransomware incident affecting its systems. It said it notified the ACSC, the AFP and the OAIC [zd-idm]. In March 2024 ZircoDATA said there was no evidence that customer personal information had been affected [zd-idm].

In May 2024 the National Cyber Security Coordinator disclosed that the incident affected government and other clients [zd-itnews]. Affected client organisations then confirmed exposure of their data β€” including archived family-violence and sexual-assault support records held for Monash Health [zd-itnews], student identity data for Melbourne Polytechnic [zd-itnews], and identity and visa data from the Home Affairs Free Translating Service [zd-cd]. Victoria’s information commissioner (OVIC) told affected Victorian public-sector bodies to notify it [zd-itnews].

Timeline

  • 2024-02-08 β€” ZircoDATA discovered the encryption of its systems [zd-idm].
  • 2024-02-22 β€” ZircoDATA learned of a dark-web claim relating to the incident [zd-idm].
  • 2024-02 β€” ZircoDATA publicly acknowledged the incident [zd-idm].
  • 2024-05 β€” The National Cyber Security Coordinator disclosed impact on government and other clients; Monash Health confirmed its records were affected [zd-itnews].
  • 2024-10 β€” Home Affairs personal data reported as compromised [zd-cd].

Current status

Disclosed. As a supplier incident the exposure spans many clients; no single count of affected individuals has been published, so none is asserted here.

Why it matters

A records-management vendor concentrates other organisations’ most sensitive archives; one breach can expose government and health data across unrelated clients at once.

GGOVERN Tabletop Exercises Β· Govern house Strengthen your cyber resilience β€” rehearse the decisions that matter. Book a Discovery Call β†’