GDLockerSec is an emerging ransomware group first observed in January 2025, operating with apparent financial motivations based on their ransomware deployment patterns. The group's origin and affiliations remain unclear due to limited public documentation, though their targeting of victims across diverse geographic regions including the United States, Hong Kong, Egypt, Nigeria, and Morocco suggests either a broad operational scope or possible affiliate structure. With only five documented victims to date, GDLockerSec appears to focus on opportunistic targeting across multiple sectors including education, technology, and public sector entities, though their specific attack methodology, initial access vectors, and encryption techniques have not been publicly detailed by major security research organizations. No notable high-profile campaigns or significant ransoms have been publicly reported for this group, likely due to their recent emergence and limited observed activity. The group appears to remain active as of early 2025, though comprehensive threat intelligence on their operations, capabilities, and infrastructure remains limited in public security research reporting. The group has been linked to 5 public disclosures across our corpus. First observed on a leak site on January 24, 2025; most recent post January 26, 2025. The operation is currently inactive.
Also tracked as: gd lockersec.
Sector and geography
This disclosure adds to ransomware activity in the Technology sector, which has 3,549 disclosures indexed across all operators we track. Geographically, aws.amazon.com is reported in United States, a country with 11,033 ransomware disclosures in our corpus.
If your organisation is affected
A listing by GDLockerSec means aws.amazon.com 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 GDLockerSec'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.
