Goznym was a banking trojan operation that emerged in January 2015, primarily motivated by financial gain through credential theft and fraudulent banking transactions rather than traditional ransomware deployment. The group is believed to have originated from Eastern Europe, operating as a collaborative criminal enterprise that combined the Gozi ISFB banking trojan with Nymaim malware to create a hybrid threat capable of stealing banking credentials and conducting unauthorized financial transfers. Goznym primarily gained initial access through malicious email campaigns containing infected attachments or links, utilizing sophisticated web injection techniques to steal online banking credentials and conducting man-in-the-browser attacks to facilitate fraudulent transactions, though they were not known to employ traditional double or triple extortion tactics associated with modern ransomware groups. The operation was notably disrupted by a major international law enforcement action in 2019, when the U.S. Department of Justice announced charges against ten individuals associated with the Goznym network, which was responsible for stealing an estimated $100 million from victims across multiple countries, primarily targeting financial institutions and their customers in the United States and other Western nations. The Goznym operation has been largely dormant since the 2019 law enforcement disruption, with key members either arrested or having moved on to other criminal enterprises. The group has been linked to 1 public disclosures across our corpus. First observed on a leak site on January 1, 2015. 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, Allegheny County DA's office is reported in United States, a country with 11,033 ransomware disclosures in our corpus.
If your organisation is affected
A listing by goznym means Allegheny County DA's office 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 goznym'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.
