Banco Central de la República Argentina

About zerotolerance

The zerotolerance ransomware group is a recently emerged threat actor first observed in May 2024, appearing to be financially motivated based on their ransomware operations targeting the financial sector. Given their recent emergence and limited observed activity, there is insufficient public intelligence to determine their country of origin, affiliations with other threat groups, or whether they operate as an independent entity or under a Ransomware-as-a-Service model. The group's attack methodology, tools, and tactics remain largely undocumented by major cybersecurity firms and government agencies due to their limited operational footprint. Their targeting appears geographically focused on Argentina within the financial services sector, though with only one documented victim, broader targeting patterns cannot be definitively established. No major campaigns, high-profile incidents, or law enforcement actions have been publicly reported against this group by CISA, FBI, or established threat intelligence organizations. The current operational status of zerotolerance remains unclear due to the limited intelligence available, though no recent activity has been publicly documented since their initial observation. The group has been linked to 1 public disclosures across our corpus. First observed on a leak site on May 9, 2024. The operation is currently inactive.

Timeline of this disclosure

• May 9, 2024Banco central argentina listed by zerotoleranceon the group's public leak site

Sector and geography

This disclosure adds to ransomware activity in the Financial sector, which has 426 disclosures indexed across all operators we track. Geographically, Banco central argentina is reported in Argentina, a country with 29 ransomware disclosures in our corpus.

If your organisation is affected

A listing by zerotolerance means Banco central argentina 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 zerotolerance's leak site and across paste and breach channels, and brief downstream partners who may be exposed through you.