Interlock is a ransomware operation first seen in late September 2024 that attacks organisations in North America and Europe. Its encryptors use AES and RSA, append .interlock to encrypted files, and leave the note !__README__!.txt in each affected folder, sometimes pushed out by Group Policy. The note gives no price. It lists the data categories taken, warns against renaming files, using recovery tools or rebooting, and gives a Tor address and company ID for contact. It says the data will be released or sold and the media, regulators and competitors told if the victim stays silent for 96 hours. Interlock hits healthcare, education, manufacturing, government and technology targets, with US victims making up most of its leak-site listings. It gets in through fake browser or software updates on hacked websites and ClickFix lures, then moves laterally over remote desktop and remote-access tools. Data is usually copied to attacker-controlled Azure storage before encryption. Windows, Linux and FreeBSD encryptors exist, and the group has mostly hit virtual machines. Several investigators see overlaps with Rhysida, but the link is not confirmed.
Sources: In-house research
File extensions: .interlock
Ransom note filenames: !__README__!.txt, interlock_readme.txt
Decryptor: No public decryptor was found. Checked 2026-11-11.
Data exfiltration risk: Confirmed — Interlock copies data out before encrypting, often to attacker-controlled Azure storage, then threatens to publish it on its Tor leak site, Worldwide Secrets Blog. The site was online on 2026-10-13 and lists well over a hundred victims.
Systems typically targeted: Healthcare, education, manufacturing, government and technology organisations in North America and Europe. It has Windows, Linux and FreeBSD encryptors and has mostly been seen encrypting virtual machines.
Do this first: Entry has come from fake browser updates on compromised websites and from ClickFix prompts that trick users into pasting a PowerShell command. Look for remote access trojans, Cobalt Strike, SystemBC, AnyDesk or ScreenConnect, and check Azure Storage Explorer and AzCopy use for data leaving the network. Keep !__README__!.txt and encrypted samples, and hunt for scheduled tasks and Run keys left for persistence.
From the ransom note !__README__!.txt:
INTERLOCK - CRITICAL SECURITY ALERT To Whom It May Concern, Your organization has experienced a serious security breach. Immediate action is required to mitigate further risks. Here are the details: THE CURRENT SITUATION - Your systems have been infiltrated by unauthorized entities. - Key files have been encrypted and are now inaccessible to you. - Sensitive data has been extracted and is in our possession. […]
Checked by: Proven Data research
Dealing with an active incident? Our incident response team is available 24/7.
Emergency response: +1 (877) 364-5161