Trinity is a recently emerged ransomware group first observed in June 2024, operating with apparent financial motivations based on their targeting patterns across multiple sectors and countries. The group has been documented attacking 18 victims primarily across the United States, Spain, Canada, Philippines, and Argentina. Their operational methodology demonstrates a focus on business services, healthcare, technology, and manufacturing sectors, suggesting they may be opportunistically targeting organizations with critical infrastructure dependencies and higher likelihood of ransom payment. Given the limited public documentation from major cybersecurity agencies and the group's recent emergence, specific details about their country of origin, ransomware-as-a-service model, initial access vectors, encryption methods, or double extortion tactics have not been extensively reported by CISA, FBI, or established threat intelligence firms. No major high-profile attacks or significant law enforcement actions against Trinity have been publicly documented to date. The group appears to remain active as of current reporting, though their relatively small victim count and recent emergence suggest they may be in early operational phases or operating with limited scale compared to more established ransomware families. The group has been linked to 18 public disclosures across our corpus. First observed on a leak site on June 11, 2024; most recent post March 16, 2025. The operation is currently inactive.
Sector and geography
This disclosure adds to ransomware activity in the Business Services sector, which has 3,796 disclosures indexed across all operators we track. Geographically, CBSTRAINING is reported in Canada, a country with 1,055 ransomware disclosures in our corpus.
If your organisation is affected
A listing by Trinity means CBSTRAINING 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, CCCS (Canada), as required for your jurisdiction.
- Monitor for the data appearing on Trinity'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.
