Was cc***.or.*z hit by ransomware?

cc***.or.*z was listed by the benzona ransomware operation (New Zealand), and stolen data was published on the group's leak site. Darkfield tracks this disclosure with the original leak post, screenshot and group context.

Who is the benzona ransomware group?

benzona is a ransomware operator tracked by Darkfield. See the full operator dossier for its known victims, sectors targeted, IOCs and leak-site infrastructure.

What data was leaked in the cc***.or.*z breach?

benzona published data attributed to cc***.or.*z. Darkfield captured the leak post and a screenshot of the listing.

Ransomware victim disclosure

← All victims

cc***.or.*z

Claimed by Benzona · listed 6 months ago

Age

since listed · data leaked

Status timeline

ListedJan 12, 2026
Data leakeddate unknown

At a glance

Group: Benzona
Status: Data leaked
Country: New Zealand
Listed on leak site: Jan 12, 2026

About the victim

AI dossier — public-source company profile

The victim is identified only by the partially redacted domain 'cc***.or.*z' registered in New Zealand (the '.or.nz' second-level domain suggests a non-profit or community organisation). No public site content or leak post details are available to determine the organisation's nature or activities.

Attack summary

Severity: medium — Data is reported as published ('data_published' status) indicating at least some exfiltration occurred, but the absence of any leak post content, data size, or proof details prevents confirmation of scale or sensitivity, warranting a medium rating rather than high or critical.

The group 'benzona' has listed this organisation with a disclosed status of 'data_published', implying data has been exfiltrated and released; however, no leak post content is available to confirm specific claims about encryption, exfiltration scope, or data categories.

medium

Sources

Victim sitecc***.or.*z

Source

Indexed 6 months ago

This page surfaces a public ransomware disclosure indexed by Darkfield. Original posts come from the operator's own leak site; we cross-check against ransomware.live, RansomLook and RansomWatch where applicable. Share this URL freely.

Is this your supplier? Your competitor? You?

Pro plans monitor your domain, corporate emails, and crypto wallets across every new ransomware leak-site post, breach dump and Telegram callout — alerts within 5 minutes.

Disclosure context

About benzona

Benzona is an emerging ransomware group that was first observed in November 2025, operating with apparent financial motivations based on their targeting patterns across multiple sectors and geographic regions. The group has conducted at least 14 documented attacks within a short timeframe since their emergence, suggesting an active operational tempo. Given the limited public documentation available from major threat intelligence sources, specific details regarding the group's country of origin, potential affiliations, or operational model remain unclear, though their diverse geographic targeting spanning Romania, India, Côte d'Ivoire, Taiwan, and France suggests either a broad operational scope or potential ransomware-as-a-service model. The group's attack methodology and technical capabilities have not been extensively documented in public threat intelligence reporting, though their targeting of healthcare, manufacturing, hospitality and tourism, and technology sectors indicates they may be opportunistic in their victim selection rather than following highly specialized targeting criteria. No major high-profile campaigns or significant law enforcement actions against Benzona have been publicly reported by CISA, FBI, or major security firms, likely due to the group's recent emergence and relatively limited scale of operations compared to established ransomware families. Given the group's recent first observation date of November 2025, Benzona appears to remain active, though comprehensive threat intelligence profiles from established security researchers have not yet been published due to the group's nascent operational history. The group has been linked to 14 public disclosures across our corpus. First observed on a leak site on November 26, 2025; most recent post January 30, 2026. The operation is currently active.

Timeline of this disclosure

January 12, 2026cc***.or.*z listed by benzonaon the group's public leak site

Other recent disclosures by benzona

benzona has been linked to 14 public victims on Darkfield. A sample of the most recent:

See the full benzona dossier →

Sector and geography

Geographically, cc***.or.*z is reported in New Zealand, a country with 11 ransomware disclosures in our corpus.

If your organisation is affected

A listing by benzona means cc***.or.*z appeared on a ransomware extortion site and data attributed to it has been published. If this is your organisation, or a supplier you depend on, the priority is to confirm the intrusion and contain it before the window to act closes.

Engage your incident-response team and preserve forensic evidence before remediating — do not wipe affected systems first.
Force a password reset and revoke active sessions for exposed accounts; rotate any credentials, API keys or certificates that may have been in the stolen data.
Assess regulatory notification duties (GDPR, NIS2, sector regulators) — many carry a 72-hour reporting clock from awareness.
Report the incident to your national CERT, CERT NZ (New Zealand), as required for your jurisdiction.
Monitor for the data appearing on benzona's leak site and across paste and breach channels, and brief downstream partners who may be exposed through you.

How we know this. Darkfield monitors public ransomware leak sites continuously, archiving every new disclosure and the data later released against the victim. Each entry on this page is sourced from the operator's own publication and cross-checked against complementary OSINT feeds (RansomLook, ransomware.live, RansomWatch). We do not collect or host stolen data — only the metadata, timestamps and screenshots needed to make the public disclosure searchable and accountable. Records here are corrected when the original post is edited, retracted, or merged with another disclosure.