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.
If your organisation is affected
A listing by benzona means *a*ame*i*a.com.g* 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.
- 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.
