Loading story…
Interlock ransomware infections have been linked to SocGholish and the TAG-124 traffic distribution system, highlighting the role of malware-delivery networks in ransomware initial access. IBM X-Force’s examination of Interlock and Rhysida described access chains involving initial access brokers, ClickFix phishing, trojanized installers and exploitation of network-edge devices. Shared victims and network communications suggest a potentially closer relationship between Interlock operators and TAG-124, but that relationship remains unconfirmed. Amazon threat intelligence also reported an Interlock intrusion exploiting CVE-2026-20131 in March 2026.
The broader ransomware ecosystem shows how access can pass between distinct operators: Microsoft observed Gootloader handing access to Vanilla Tempest before deployment of the Supper backdoor and INC ransomware in September 2024. Technical artifacts presented by IBM illustrate payload download and execution, startup-folder persistence, encrypted HTTP communications, and host and Active Directory reconnaissance. Defenders should prioritize patching exposed network-edge systems, strengthening controls against deceptive installers and ClickFix lures, and monitoring startup-folder changes and reconnaissance activity to identify intrusions before encryption.
See which actors are running it and whether you're in range.
8 events from the most recent confirmed update back to the earliest known activity.
Amazon threat intelligence published a report documenting an Interlock intrusion that exploited CVE-2026-20131 for initial access through a network edge device. March 2026 anchors the report, not the date of the intrusion.
Huntress documented Gootloader infections that led to Tomb-crypted samples of the Supper backdoor.
Guidepoint reported an Interlock ransomware deployment likely involving initial access facilitated by SocGholish, followed by an apparent NodeSnake downloader.
Beazley Security Labs reported an Interlock-linked incident involving malware that X-Force identifies as the JunkFiction downloader. The downloader deployed a JunkFiction-crypted Supper backdoor.
Microsoft observed Gootloader handing access to Vanilla Tempest, followed by deployment of the Supper backdoor and INC ransomware. Expel also reported on the same campaign.
Recorded Future reported that Rhysida actors used the TAG-124 traffic distribution system to distribute Dave-crypted Broomstick before Interlock became active.
A paper by Julian-Ferdinand Vögele presented shared-victim and network-communication evidence suggesting a potentially stronger relationship between Interlock operators and TAG-124. The relationship was not established conclusively.
Expel used shared code-signing certificates to identify additional samples that X-Force classifies as Dave-crypted IceNova and Supper. The samples were likely associated with adjacent initial-access campaigns.
Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.
Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.
Correlate live exploitation activity against the software you actually run, and see where you're exposed.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Interlock ransomware has been highlighted as a threat actor that gains initial access through **ClickFix-style social engineering** and **fake CAPTCHA** lures rather than relying on a software exploit. The activity described shows operators tricking users into executing malicious actions, then harvesting credentials and moving laterally by abusing identity, access, and configuration weaknesses inside enterprise environments before deploying ransomware. Reporting on the broader ransomware landscape says the threat remains highly effective at scale, with Recorded Future tracking **13,000 victims** and **834 ransomware families or brands** over the past two years. The coverage points to Interlock as an example of how modern ransomware operations can bypass defenses focused mainly on CVE patching and compliance checklists, reinforcing CISA-linked guidance that organizations should prioritize mitigation of attack paths, credential abuse, and lateral movement risks alongside traditional vulnerability management.
Jul 24, 2026
**Interlock ransomware** exploited **CVE-2026-20131**, a maximum-severity zero-day in **Cisco Secure Firewall Management Center (FMC)**, more than a month before Cisco publicly disclosed and patched the flaw. The vulnerability allows an unauthenticated remote attacker to execute arbitrary Java code as `root`, giving attackers full control of exposed systems. Amazon security researchers said exploitation began on **January 26**, or **36 days before** Cisco’s March 4 disclosure, and Cisco later updated its advisory to reflect the in-the-wild abuse and urged customers to patch immediately. Amazon linked the activity to Interlock through exploit traffic observed in its **MadPot** honeypot network and through a **misconfigured Interlock server** that exposed the group’s operational toolkit. Researchers observed HTTP requests targeting a vulnerable path with embedded Java execution attempts, followed by URLs used to deliver configuration data and confirm successful compromise via an HTTP `PUT` upload. By emulating a victim host, investigators triggered delivery of a malicious **Linux ELF** payload, and the exposed staging server showed target-specific directories used to distribute tools and collect stolen data. The recovered payloads, ransom note, and **Tor-based negotiation portal** matched known Interlock tradecraft and supported attribution to the group’s **double-extortion** operations.
Jul 23, 2026
Fortinet/FortiGuard Labs reported that the **Interlock** ransomware group—described as a smaller, non-**RaaS** operation—ran a months-long intrusion campaign primarily targeting the **education sector** in the US and UK. Initial access was observed via **MintLoader**, including “ClickFix” social-engineering lures, followed by post-compromise activity using a JavaScript implant referred to as **NodeSnakeRAT**, lateral movement with valid accounts and living-off-the-land techniques, and broad discovery prior to impact. The operation follows a **double-extortion** pattern, with data exfiltration (including use of `AZcopy`) preceding ransomware deployment, and has been observed impacting both Windows endpoints and **Nutanix** hypervisor environments. A key technical finding is Interlock’s use of a **Bring Your Own Vulnerable Driver (BYOVD)** technique to neutralize endpoint defenses. Researchers identified a custom tool dubbed **“Hotta Killer”** (associated with `polers.dll`) that drops a kernel driver `UpdateCheckerX64.sys`, described as a renamed vulnerable anti-cheat driver (`GameDriverx64.sys`, **CVE-2025-61155**). Because the driver is legitimate and digitally signed, it can pass initial trust checks; once loaded, it is abused for kernel-level process termination to **kill EDR/AV processes**, with reporting noting targeting of **Fortinet** security tooling specifically, enabling subsequent ransomware execution with reduced detection and response capability.
Jun 29, 2026