Interlock Ransomware: What You Need to Know & How to Recover Fast
Interlock has hit education, healthcare and manufacturing organisations across North America and Europe since 2024, breaking in through compromised websites and fake CAPTCHA prompts. See how its ClickFix lures work, what its ransom notes demand, and how BeforeCrypt helps contain the attack and restore operations.
What is Interlock Ransomware?
Interlock is a closed ransomware operation rather than an affiliate programme — a small team that builds its own malware and runs its own intrusions, unlike most ransomware brands active today. Public leak-site tracking recorded 128 named victims on its leak site by October 2026, hit with separate Windows, Linux and FreeBSD encryptors capable of reaching virtual machines after data is exfiltrated from the network. BeforeCrypt checks for available decryption tools, including free ones, as part of every assessment, and draws on experience across Interlock engagements to contain the attack, assess recovery options and restore operations.
No Affiliate Programme
Interlock is run by a small, closed team rather than recruited affiliates.Drive-By & ClickFix Entry
Victims are compromised through infected websites and fake CAPTCHA prompts that trick users into running PowerShell.Windows, Linux & ESXi Reach
Separate encryptors target Windows, Linux, FreeBSD builds and virtual machine environments.Leak Site Extortion
Stolen data is exfiltrated before encryption and published on Interlock's leak site if the ransom isn't paid.Why You Shouldn’t Attempt to Fix It Alone
Interlock’s encryptors reportedly combine AES and RSA, with separate Windows, Linux and FreeBSD builds using slightly different schemes. BeforeCrypt checks for available decryption tools, including free ones, as part of every assessment — an unverified or wrongly applied tool can make recovery harder, so any candidate is tested on copies first before full recovery.
Interlock exfiltrates data before encryption, so even a clean restore from backups doesn’t remove the risk: stolen files can still be published on its leak site if no ransom is paid. This is an additional risk for your business, separate from the file loss itself. Notification obligations depend on your sector and geography — see the FAQ below for the regulatory clocks that may apply.
BeforeCrypt provides full incident response where a client has no internal capacity, or works alongside an existing IT team on containment, eradication and recovery. We establish what data was actually taken, run sanctions screening before any payment, preserve evidence for insurers and regulators, and coordinate notification timelines. Where it’s the right option, negotiation with the attackers — including reducing the demand and buying time — is handled directly, which matters given Interlock’s documented habit of threatening leak-site publication and media notification together. Running technical response, internal coordination, customer communication and any attacker contact at once strains most internal teams.
An experienced internal security team can handle substantial parts of the response itself. Our detailed emergency response plan walks through the sequence step by step. A free assessment call with our team helps you decide quickly which parts to keep in-house and where specialist support saves time.
Interlock’s ransom note — most often named !__README__!.txt, though later intrusions have dropped FIRST_READ_ME.txt or _QUICK_GUIDE_.txt — is pushed across the network via a Group Policy Object rather than left only in encrypted folders. It carries no ransom figure, just a unique victim code and a Tor .onion address, with a 96-hour deadline before data is published.
YOU MUST NOT ATTEMPT TO TOUCH, RESTORE OR OVERWRITE THE DATA.
Hit by Interlock Ransomware? Take These Immediate Recovery Steps
If you’ve fallen victim to ransomware, follow these crucial steps:
Request 24/7 Ransomware Recovery Help
Get expert guidance to assess, contain, and recover safely.
Isolate Infected Systems
Disconnect infected devices to stop the spread. Avoid self-recovery.
Preserve Evidence Immediately
Keep ransom notes & logs. Do not restart or modify anything.
Interlock ransomware statistics & facts
RANSOM SUMMARY
| Name | Interlock |
| Danger level | High. Double-extortion ransomware that exfiltrates data and encrypts Windows, Linux and VMware ESXi environments. |
| Release date | First observed September 2024 |
| OS affected | Windows, Linux, VMware ESXi, FreeBSD |
| Appended file extensions | .interlock or .1nt3rlock |
| Ransom note filename | !__README__!.txt (early campaigns); FIRST_READ_ME.txt or _QUICK_GUIDE_.txt (later) |
| Contact channels | Tor (.onion) negotiation portal with unique victim code; an email address was listed on the leak site in early reporting |
COMMON ATTACK VECTORS
Documented initial-access techniques used by Interlock:
- Drive-by Compromise (T1189) — initial access via compromised legitimate websites serving a ClickFix lure.
- User Execution: Malicious Link/File (T1204) — payloads disguised as Chrome or Edge browser updates, or as security-software installers such as FortiClient.exe and GlobalProtect.exe.
- Exploit Public-Facing Application (T1190) — exploited CVE-2026-20131 in Cisco Secure Firewall Management Center as a zero-day beginning January 2026.
- Valid Accounts (T1078) — credentials purchased from initial access brokers and harvested via infostealers for lateral movement.
- External Remote Services (T1133) — AnyDesk and RDP used to move between compromised systems.
RANSOM AMOUNTS
Interlock concentrates on education, manufacturing, healthcare and government organisations across North America and Europe, typically gaining entry through compromised websites, fake CAPTCHA prompts or exposed firewall management interfaces.
Interlock actors do not leave an initial ransom demand or payment instructions on compromised networks; the figure is only relayed once the victim makes contact through the Tor negotiation portal. Ransoms are usually paid in Bitcoin. Quick-buy methods of purchasing Bitcoin with PayPal or credit cards do not work for this size of ransom payment and it is important to obtain expert advice to ensure that a payment of this size is legally compliant.
Where negotiation is the right option, our experienced negotiation team has consistently secured meaningful reductions from the initial demand to the final settlement across Interlock engagements.
AVERAGE LENGTH
In a published incident-response case, dwell time from initial compromise to deployment of the encryptor was about 17 days, while in a published 2026 incident-response case the attackers reached the domain controller slightly over 26 hours after initial access. A DLL executed after encryption deletes the encryption binary itself, complicating forensic reconstruction.
For most ransomware victims, downtime is the most costly aspect of the incident, with potential for considerable reputational harm.
Our extensive experience with Interlock ransomware gives us a deep understanding of the gang’s tactics, enabling us to resolve attacks swiftly and restore your files.
How to identify interlock ransomware
The note is pushed across the network via a Group Policy Object rather than dropped only in encrypted folders, carrying a unique victim code instead of a ransom figure.
Frequently asked questions
Decryption depends on the ransomware variant. In some cases, publicly available decryption tools exist, but not all attacks have a known solution. You can submit a free ransomware recovery request, and we will check for possible decryption methods.
In most cases involving personal data, which applies to nearly every ransomware incident, reporting is legally required. In the EU, GDPR requires notification to the relevant data protection authority within 72 hours of becoming aware of a personal data breach. The UK ICO requires the same 72-hour window. In the US, HIPAA-covered entities have 60 days to notify affected individuals (and immediately for breaches affecting 500+ people). The clock starts from awareness of the incident, not from a full technical understanding.
In most jurisdictions, paying a ransom is not illegal in itself — but it can become illegal if the payment ends up going to a sanctioned entity or country (OFAC-designated groups in the US, EU sanctions lists, UK Treasury lists). Before any payment, sanctions screening is essential. BeforeCrypt handles this compliance layer as a standard part of every engagement.
Most established ransomware groups do provide working decryption tools when paid — the business model depends on their reputation for delivery. However, decryptors are often slow, incomplete, or corrupt a percentage of files during recovery. This is where working with a specialist matters: BeforeCrypt tracks the delivery reliability of specific groups, negotiates sample-file decryption as proof of capability where the group allows it, and plans realistic recovery timelines based on our own engagement history with each group.
Most modern ransomware groups follow through on publication threats — stolen data appears on the group's leak site, is often mirrored to Telegram and dark web forums, and may be sold to third parties. Recovery becomes limited to whatever you can rebuild from backups.
Backups protect against file loss but not against data theft. Most modern ransomware groups exfiltrate sensitive data BEFORE encryption and threaten to publish it regardless of your recovery capability. This is why leak-site publication and negotiation still matter even for organisations with clean, offline backups — and why "we can just restore from backup" rarely tells the full story.
In most jurisdictions, yes — reporting is a standard part of a ransomware incident and, in some cases, legally required. In the US, that means the FBI (via IC3 or a local field office) and CISA. In the EU, national CERT and cybercrime units. Reporting does not obligate you to any specific recovery path but does open access to threat intelligence and, occasionally, decryption tools recovered by law enforcement.
Yes. We’ve handled 1,700+ incidents across ransomware, BEC and data-leak extortion. We identify the variant, decide decrypt vs. clean verified restore, and guide a controlled return to operations. When needed, we support negotiation & compliance—always legally and with a clear audit trail.
Yes. We produce insurer-ready incident reports with a defensible timeline, scope, likely entry path, exfiltration assessment, actions taken, and chain-of-custody. We can join the adjuster call, map our findings to your carrier’s forms, and provide GDPR/NIS2 notifications where required. Final acceptance always depends on the policy and carrier, but our packages are designed to speed up approvals and reduce back-and-forth.
MSPs keep IT running; they’re not built for evidence handling and incident triage. Insurer panels optimize claims, not necessarily speed & clarity for your business. We work alongside both: kick off in ≤2h, run forensic triage with chain-of-custody, coordinate safe containment, and deliver executive- and insurer-ready findings—without taking your environment hostage.
Because it turns chaos into fast, safe recovery. We cut downtime and limit damage while preserving evidence. Within ≤48h you get a forensic triage pack (timeline, likely entry path, scope, decrypt-vs-clean-restore decision, go-live criteria) so leadership can act with confidence. Result: controlled, verified restart—not guesswork.