Deadlock is a ransomware group first observed in June 2026 with an apparent financial motivation, having claimed responsibility for attacks against at least 10 known victims across a geographically diverse target set. Given the recency of their emergence and limited public documentation by major threat intelligence organizations such as CISA, FBI, or Mandiant at this time, a comprehensive technical profile cannot be fully established. Based on available victimology data, the group has demonstrated a targeting pattern spanning Singapore, China, Sweden, Spain, and Nigeria, suggesting an opportunistic or globally distributed operational scope rather than a regionally focused campaign. Targeted sectors include manufacturing, business services, telecommunications, and financial services, indicating a preference for industries with high operational dependencies and potential for significant disruption, which is consistent with financially motivated ransomware actors seeking maximum leverage for ransom payment. No confirmed attribution regarding country of origin, RaaS affiliation, or specific tooling has been publicly documented by authoritative sources as of this profile's preparation. Due to the group's nascent operational timeline and the limited volume of publicly verified intelligence, analysts should treat this profile as preliminary and subject to significant revision as additional technical indicators, victim disclosures, and research reporting become available. Continued monitoring is advised given the cross-sector and cross-regional targeting behavior observed in this early operational phase. The group has been linked to 114 public disclosures across our corpus. First observed on a leak site on June 15, 2026; most recent post August 24, 2026. The operation is currently active.
If your organisation is affected
A listing by Deadlock means FBC 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, ECS-CSIRT (South Africa), as required for your jurisdiction.
- Monitor for the data appearing on Deadlock'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.
