BRINKS-CO.NZ
bd_0093bd55089ea781 · schema v1 · pii pii-v2
Full breach record for BRINKS-CO.NZ →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Cl0p on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Company description · AI-generated by the aggregator, not the leak post
N/A I don't have verified information about a company operating under the domain "BRINKS-CO.NZ." I want to flag that this domain name is worth treating with caution from a threat intelligence perspective: it closely mimics "Brinks," the well-known US-based security and cash logistics company, while using a New Zealand country-code domain, a pattern sometimes associated with typosquatting or brand impersonation for phishing purposes. I cannot confirm whether this is a legitimate New Zealand subsidiary, an unrelated business, or a malicious lookalike domain without further verification through domain registration records, WHOIS data, or corporate registries. I'd recommend checking NZ Companies Office records and domain registration history before treating this as a legitimate entity.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Sep 23, 2026
Claim posted
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.