DeadLock Ransomware: Smart Contracts for Malicious Purposes — Blockchain-Automated Ransom Operations

DeadLock Ransomware (TL-2026-0069) is a high-severity ransomware operation, first published 2026-02-12. It is attributed to DeadLock with low confidence, maps to 55 MITRE ATT&CK techniques (T1003, T1005, T1018), and is covered by 12 detection rules and 32 indicators of compromise.

Key facts for TL-2026-0069

Threat ID
TL-2026-0069
Severity
HIGH
Status
ACTIVE
Category
RANSOMWARE
First published
2026-02-12
Last reviewed
2026-02-12
Attribution
DeadLock
Attribution confidence
LOW
Motivation
FINANCIAL
Target sectors
Manufacturing, Technology, Healthcare, Financial Services, Professional Services, Retail, Education
Target regions
Global, Europe, North America, Asia-Pacific
Detection rules
12
Indicators of compromise
32

Malware and tooling in DeadLock Ransomware

Malware and tooling: DeadLock

DeadLock is a ransomware operation active since at least mid-2025 that introduces smart contract integration for ransom payment operations — a novel convergence of blockchain/DeFi technology and ransomware. DeadLock encrypts files with .dlock extension using RSA+AES hybrid encryption (no known decryptor), deploys ransom notes (HOW_RECOVER.[ID].txt) with unique 6-character victim IDs, and communicates via Session messenger (decentralized, end-to-end encrypted). The Group-IB 'Smart Contracts for Malicious Purposes' report documents how DeadLock leverages blockchain smart contracts for automated ransom payment verification, escrow mechanisms, and potentially affiliate payment distribution — eliminating the need for manual payment verification and creating a trustless, auditable ransomware payment infrastructure that operates independently of any single C2 server.

How DeadLock Ransomware works

DeadLock ransomware represents a significant evolution in ransomware operations by integrating blockchain smart contracts into the ransom payment pipeline. While ransomware groups have accepted cryptocurrency payments for years, DeadLock goes further by using smart contracts to automate payment verification, escrow, and potentially affiliate revenue distribution — creating a decentralized, trustless ransomware payment infrastructure.

ENCRYPTION AND FILE OPERATIONS: DeadLock uses hybrid RSA+AES encryption — AES for file content encryption (speed) with RSA for key encryption (security). Encrypted files receive a .[random 6-character hex].dlock extension (e.g., .F8C6A8.dlock). The same 6-character ID serves as the victim's personal identifier throughout the ransom negotiation process. Ransom notes are dropped as HOW_RECOVER.[ID].txt (e.g., HOW_RECOVER.BF6377.txt) and RECOVERY_CHAT.[ID].HTML. The HTML variant opens a browser-based chat interface for negotiation. No known decryption tool exists — the encryption implementation appears cryptographically sound based on victim reports and analysis.

COMMUNICATION INFRASTRUCTURE: DeadLock uses Session messenger (getsession.org) for victim communication — a decentralized, end-to-end encrypted messaging platform based on the Oxen blockchain. Session IDs serve as contact points (e.g., 05804f9b14b02f44fa97795a60ab1faf5128e3259c75459aaaaeabc80c14da78). Session's decentralized architecture means there is no central server to take down, no IP addresses to trace, and no metadata to collect. This is a deliberate operational security choice — Session provides stronger anonymity guarantees than Tor-based .onion sites used by traditional ransomware groups.

SMART CONTRACT INTEGRATION: The novel aspect documented by Group-IB: DeadLock integrates blockchain smart contracts into ransomware operations. Smart contracts are self-executing programs deployed on a blockchain that automatically execute when predefined conditions are met. In DeadLock's model:

1. AUTOMATED PAYMENT VERIFICATION: Smart contracts monitor blockchain addresses for incoming payments matching the ransom amount. When payment is confirmed on-chain, the contract automatically triggers the next phase — potentially including decryption key release or affiliate notification. This eliminates manual payment verification delays.

2. ESCROW MECHANISMS: Smart contracts can function as trustless escrow — holding ransom payments until both parties fulfill obligations. In theory, a smart contract could hold payment until the victim confirms decryption works, then release funds to the operator. This creates 'trust' in the ransomware transaction without either party trusting the other.

3. AFFILIATE PAYMENT DISTRIBUTION: For RaaS-model operations, smart contracts can automatically split payments between affiliates, operators, and developers based on predefined percentages. This eliminates the trust problem inherent in criminal partnerships — no single party controls the funds.

4. ON-CHAIN AUDITABILITY: All smart contract transactions are publicly visible on the blockchain. While addresses are pseudonymous, the payment flow is transparent. This creates a verifiable record for both the criminal operation and for investigators.

PAYMENT METHODS: DeadLock accepts Bitcoin and Monero. Bitcoin payments provide pseudonymous transactions that are publicly traceable on the blockchain — smart contract integration works natively with Bitcoin through Bitcoin Script or through Ethereum/EVM-compatible chains for more complex logic. Monero provides stronger privacy guarantees (ring signatures, stealth addresses) but has limited smart contract capabilities.

RANSOM PROCESS: The documented ransom process follows a structured negotiation: 1. Victim receives ransom note with personal ID and Session contact 2. Victim contacts operator via Session messenger 3. Victim sends 2-3 encrypted files for test decryption (proof of capability) 4. Operator decrypts test files (max 5MB) as proof 5. Payment negotiated and executed (BTC/XMR) 6. Smart contract verifies payment on-chain 7. Decryptor tool delivered

Post-payment deliverables include: decryption tool, stolen file inventory, proof of data deletion, attack methodology report, security recommendations, and a 'promise' of no future attacks.

DOUBLE EXTORTION: DeadLock employs standard double extortion: 'We have downloaded all the company's confidential data.' Data exfiltration precedes encryption, creating dual leverage — pay for decryption AND data deletion. The 'confidential data' threat implies a leak site exists or is planned.

IMPLICATIONS OF SMART CONTRACT INTEGRATION: Smart contract integration fundamentally changes ransomware economics and enforcement: - CENSORSHIP RESISTANCE: Smart contracts on public blockchains cannot be seized, shut down, or modified by law enforcement. The payment infrastructure operates independently of any server or domain. - TRUSTLESS OPERATIONS: Removes the trust problem between ransomware operators and affiliates. Payment distribution is automated and immutable. - AUTOMATED SCALING: Payment verification and distribution happen automatically, enabling higher transaction volumes without operational overhead. - FORENSIC OPPORTUNITY: Ironically, on-chain transactions are publicly visible. Smart contract code can be analyzed. Payment flows can be traced (especially Bitcoin). This creates a forensic surface that doesn't exist in traditional cash-based criminal operations. - REGULATORY CHALLENGE: Smart contracts on decentralized blockchains operate outside traditional financial regulation. OFAC sanctions on wallet addresses are the primary enforcement tool, but new addresses can be generated trivially.

MITRE ATT&CK techniques used in TL-2026-0069

credential-access

T1003 OS Credential Dumping; T1110 Brute Force; T1555 Credentials from Password Stores; T1558 Steal or Forge Kerberos Tickets

collection

T1005 Data from Local System; T1039 Data from Network Shared Drive; T1074 Data Staged; T1560 Archive Collected Data

discovery

T1018 Remote System Discovery; T1057 Process Discovery; T1082 System Information Discovery; T1083 File and Directory Discovery; T1087 Account Discovery; T1135 Network Share Discovery; T1482 Domain Trust Discovery

lateral-movement

T1021 Remote Services; T1570 Lateral Tool Transfer

defense-evasion

T1027 Obfuscated Files or Information; T1036 Masquerading; T1055 Process Injection; T1070 Indicator Removal; T1078 Valid Accounts

exfiltration

T1041 Exfiltration Over C2 Channel; T1048 Exfiltration Over Alternative Protocol; T1537 Transfer Data to Cloud Account; T1567 Exfiltration Over Web Service

execution

T1047 Windows Management Instrumentation; T1053 Scheduled Task/Job; T1059 Command and Scripting Interpreter; T1204 User Execution; T1569 System Services

privilege-escalation

T1068 Exploitation for Privilege Escalation

command-and-control

T1071 Application Layer Protocol; T1090 Proxy; T1095 Non-Application Layer Protocol; T1105 Ingress Tool Transfer; T1571 Non-Standard Port; T1573 Encrypted Channel

persistence

T1133 External Remote Services; T1543 Create or Modify System Process; T1547 Boot or Logon Autostart Execution

initial-access

T1190 Exploit Public-Facing Application; T1566 Phishing

impact

T1486 Data Encrypted for Impact; T1489 Service Stop; T1490 Inhibit System Recovery; T1491 Defacement; T1529 System Shutdown/Reboot; T1531 Account Access Removal; T1657 Financial Theft

resource-development

T1583 Acquire Infrastructure; T1585 Establish Accounts; T1587 Develop Capabilities; T1588 Obtain Capabilities

defense-impairment

T1685 Disable or Modify Tools

Remediation for DeadLock Ransomware

Immediate actions

  • Monitor blockchain addresses associated with DeadLock ransom payments — Chainalysis and Elliptic provide ransomware wallet tracking
  • Block Session messenger (getsession.org) at network proxy if not business-justified — DeadLock's primary C2 communication channel
  • Deploy file integrity monitoring for .dlock extension creation — indicates active encryption in progress
  • Implement immediate endpoint isolation upon detection of HOW_RECOVER.*.txt or RECOVERY_CHAT.*.HTML file creation
  • Block known smart contract addresses on blockchain monitoring platforms to prevent payment execution

Workarounds

  • Maintain air-gapped offline backups — DeadLock encryption is cryptographically sound with no known decryptor
  • Implement application whitelisting to prevent unauthorized executable and DLL execution
  • Deploy network segmentation to limit ransomware lateral movement scope
  • Configure Group Policy to restrict PowerShell execution modes on standard user workstations

Longer-term hardening

  • Deploy ransomware-specific behavioral detection targeting hybrid RSA+AES encryption patterns and mass file modification
  • Implement blockchain transaction monitoring for OFAC-sanctioned addresses and known ransomware payment wallets
  • Establish smart contract analysis capability — reverse-engineer deployed contracts to understand payment logic and identify wallet addresses
  • Deploy canary files and honeypots to detect encryption activity before full deployment
  • Implement robust offline backup strategy with tested restoration procedures — no known DeadLock decryptor exists

Weaknesses (CWE) in DeadLock Ransomware

CWE-287, CWE-522, CWE-269, CWE-306, CWE-693

Timeline of DeadLock Ransomware

  • DeadLock ransomware first observed in the wild. Initial samples demonstrate .dlock file extension and HOW_RECOVER ransom note pattern. Source: BleepingComputer victim reports
  • BleepingComputer moderator 'quietman7' confirms DeadLock uses RSA+AES hybrid encryption. No known decryption method without operator's private key. Encryption described as 'secure' — brute force not feasible. Source: BleepingComputer Forum Analysis
  • First public victim reports on BleepingComputer forums. Victim 'joney5' reports encrypted files with .F8C6A8.dlock extension and HOW_RECOVER.BF6377.txt ransom note. Session messenger ID published as contact method. Source: BleepingComputer Forum Thread #810441
  • Full ransom note content documented: double extortion model, Session messenger for negotiation, 2-3 file test decryption proof, Bitcoin/Monero payment, post-payment deliverables (decryptor, stolen file list, data deletion proof, security report). Source: BleepingComputer Forum
  • DeadLock's use of Session messenger (Oxen blockchain-based, decentralized E2E encryption) confirmed as primary communication channel. Session provides stronger anonymity than Tor .onion sites — no central server, no IP metadata. Source: Victim Communication Analysis
  • Smart contract components developed for ransomware payment automation. Contracts deployed on EVM-compatible blockchain for automated payment verification, escrow, and affiliate distribution. Source: Group-IB Analysis
  • Double extortion model confirmed: data exfiltration precedes encryption. Ransom note explicitly states 'We have downloaded all the company's confidential data.' Implies data leak site exists or is under development. Source: Victim Reports
  • Smart contract-based payment verification becomes operational. Automated ransom payment confirmation and potentially automated decryptor delivery via smart contract triggers. Source: Group-IB Shaping Shadows Report
  • Group-IB publishes 'DeadLock Ransomware: Smart Contracts for Malicious Purposes' — comprehensive analysis of smart contract integration in ransomware operations, payment automation, escrow mechanisms, and implications for law enforcement. Source: Group-IB Blog
  • As of 2026-05-29, DeadLock ransomware remains active and undisrupted: Group-IB's Jan 2026 analysis confirms it reactivated with a new proxy server, last rotated Polygon-smart-contract infrastructure Nov 13 2025, with no arrests, takedown, or decryptor. No CVE applies; .dlock/Session/no-decryptor profile holds, so ACTIVE stands (low public visibility, no leak site).

Sources cited for DeadLock Ransomware

Threats related to DeadLock Ransomware

Detection coverage for TL-2026-0069

As of 2026-02-12, Threadlinqs Intelligence publishes 12 detection rule(s) for TL-2026-0069 across Splunk SPL, Microsoft KQL and Sigma, covering 32 indicator(s) of compromise. The whole corpus is readable without an account; a free account unlocks full detection query text in Splunk SPL, Microsoft KQL and Sigma; paid tiers add raw indicator values, correlation and the MCP server. Threadlinqs MCP server · View plans.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

[ 0 threats ] [ 0 det ] [ CRIT: 0 ] [ HIGH: 0 ]
// threat_feed
$ sort --newest
Showing all threats

Latest Threats