Global3 is an obscure ransomware group that first emerged in September 2017, appearing to be financially motivated based on their operational profile. Limited public documentation suggests the group operates independently with no confirmed affiliations to major ransomware families or state-sponsored actors, and there is insufficient evidence to determine their country of origin or whether they function as a Ransomware-as-a-Service operation. Technical details regarding their attack methodology, including initial access vectors, encryption techniques, and data exfiltration capabilities, remain undocumented in public threat intelligence reports from major security firms. The group's operational scope appears extremely limited, with only one documented victim identified in publicly available sources, specifically targeting a government facility within the United States, suggesting either a highly selective targeting approach or minimal operational capability. Current intelligence indicates Global3 has maintained an exceptionally low profile since their initial observation, with no significant law enforcement actions or high-profile campaigns documented, making their current operational status unclear. The group has been linked to 1 public disclosures across our corpus. First observed on a leak site on September 9, 2017. The operation is currently inactive.
Sector and geography
This disclosure adds to ransomware activity in the Government Facilities sector, which has 88 disclosures indexed across all operators we track. Geographically, Town of St Johnsbury is reported in United States, a country with 11,033 ransomware disclosures in our corpus.
If your organisation is affected
A listing by global3 means Town of St Johnsbury 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, CISA (United States), as required for your jurisdiction.
- Monitor for the data appearing on global3'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.
