Home/Threat Actor/Lynx Ransomware
Threat Actor

Lynx Ransomware

lynx_ransomware · unknown_likely_russia_aligned_inc_ransom_lineage · active since 2024-07

Lynx Ransomware (SentinelOne canonical code-lineage analysis, July 2024 emergence) is a financially-motivated cybercriminal ransomware operation derived from INC Ransom (inc_ransom.yaml) source code, INC Ransom source code advertised for sale on Russian-language cybercriminal forums May-June 2024 prior to Lynx's emergence.

industry technical analysis (SentinelOne, BinaryDefense, Cisco Talos) documented substantial code overlap consistent with direct source-code derivation; operational-relationship between Lynx operators and INC Ransom operators analytically open (possible scenarios include source-code-acquisition, operational-rebrand, or affiliate-fork)

cross-platform ransomware encryptor development (Windows, Linux, VMware ESXi hypervisor targeting)

standard double-extortion operational model with rclone-mediated Mega.nz data exfiltration and leak- site data publication.

manufacturing, business services, construction, and technology sector targeting consistent with mid-market ransomware ecosystem and INC Ransom predecessor operational profile.

operationally distinct from but ecosystem-adjacent to all other ransomware clusters curated separately in this corpus.

positions Lynx within documented ransomware code-genealogy succession patterns (Conti successors Black Basta / Royal / BlackSuit.

Babuk leak derivatives.

LockBit Black builder derivatives DragonForce and Brain Cipher).

unknown_likely_russia_aligned_inc_ransom_lineage confidence: high 8 aliases

Profile

Lynx Ransomware (SentinelOne canonical code-lineage analysis, July 2024 emergence) is a financially-motivated cybercriminal ransomware operation that emerged in approximately July 2024 with operational tooling derived from the INC Ransom (inc_ransom.yaml) ransomware family source code, INC Ransom source code had been advertised for sale on Russian-language cybercriminal forums in May-June 2024 prior to Lynx's operational emergence. Industry technical analysis (SentinelOne, BinaryDefense, Cisco Talos) documented substantial code overlap between Lynx ransomware binaries and INC Ransom encryptor code consistent with direct source-code derivation rather than independent reimplementation. The cluster's operational distinctiveness is concentrated in two dimensions: (1) INC RANSOM CODE LINEAGE OPERATIONAL POSITIONING.

Lynx operates as a documented code-lineage successor to INC Ransom, positioning the cluster within a broader pattern of ransomware ecosystem code-genealogy evolution. The operational pattern is similar to documented predecessor- successor patterns including the Conti collapse and successor lineage (Black Basta, Royal, BlackSuit, all separately curated in this corpus), the Babuk source-code leak followed by multiple derived clusters, the Hello Kitty / FiveHands lineage, and the September 2022 LockBit Black builder leak followed by multiple derived clusters (DragonForce, Brain Cipher, both separately curated). The exact operational-relationship between Lynx operators and INC Ransom operators remains analytically open, possible scenarios include source-code-acquisition by distinct operators, operational-rebrand by the original INC Ransom operators, or affiliate-fork by former INC Ransom affiliates retaining source code access.

(2) CROSS-PLATFORM RANSOMWARE DEPLOYMENT. Lynx operators have developed and deployed ransomware encryptor variants for Windows, Linux, and VMware ESXi hypervisor targeting, operationally consistent with the broader ransomware- ecosystem trend toward cross-platform deployment and consistent with the operational positioning as an INC Ransom code-lineage successor inheriting cross-platform development infrastructure. The VMware ESXi targeting variant is operationally significant for victim organizations operating consolidated VMware environments.

Operational tradecraft includes initial access via compromised credentials (dark-market credential supply chain), selective N-day vulnerability exploitation, conventional lateral movement (RDP, SMB), data exfiltration via rclone to Mega.nz cloud storage, INC Ransom-derived ransomware encryption, and double-extortion pressure via leak-site data publication. The cluster's victim targeting profile (manufacturing, business services, construction, technology) is consistent with the broader mid-market ransomware ecosystem and consistent with the predecessor INC Ransom operational targeting profile. Lynx is curated alongside the broader ransomware ecosystem coverage in this corpus, note that INC Ransom (inc_ransom.yaml) is curated separately as the operational predecessor cluster.

Lynx's operational distinctiveness within this ecosystem is the documented INC Ransom code-lineage successor positioning and the open analytical question of operational-relationship between the predecessor and successor clusters.

Aliases

8
lynx_ransomwarelynx ransomwarelynxlynx ransomware operatorslynx ransomware groupinc_ransom_code_lineage_successorinc_ransomware_source_code_derivativelynxransomware

Notable Campaigns

4
2024-2025Cross-Platform Ransomware Encryptor, Windows, Linux, VMware ESXi Variants
2024-2025Manufacturing and Business Services Targeting Pattern (2024-2025)
2024Lynx Ransomware Operational Emergence (July 2024)
2024INC Ransom Source Code Genealogy and Code-Lineage Analysis (2024)

Attribution & Reporting

Attributed by
SentinelOneBinaryDefenseCisco TalosSophosRecorded FutureTrend MicroSOCRadarHalcyonCISA (US Cybersecurity and Infrastructure Security Agency)FBI (Federal Bureau of Investigation)Symantec / Broadcom Threat Hunter Team
Key reporting
reportSentinelOne: Lynx Ransomware, INC Source Code Lineage Successor (2024), canonical code-lineage analysis
reportBinaryDefense: Lynx Ransomware Analysis
reportCisco Talos: Lynx Ransomware Emerging Threat Analysis
reportSophos X-Ops: Lynx Ransomware Operational Analysis
reportSOCRadar: Lynx Ransomware Dark Web Profile
reportHalcyon: Lynx Ransomware Threat Intelligence Profile
reportCISA Cybersecurity Advisory: Lynx Ransomware Indicators (2024)
reportMalpedia Actor / Malware Profile: Lynx Ransomware

Operational

State sponsor

Cybercriminal ransomware operation that emerged in approximately July 2024 with operational tooling derived from the INC Ransom (inc_ransom.yaml) ransomware family source code, INC Ransom source code had been advertised for sale on Russian-language cybercriminal forums in May-June 2024 prior to Lynx's operational emergence, and industry analysis (SentinelOne, BinaryDefense, Cisco Talos) documented substantial code overlap between Lynx ransomware binaries and INC Ransom encryptor code consistent with either source-code acquisition or operational lineage between the two clusters. The Lynx operational origin is unclear in the public record: industry analysis has not formally attributed Lynx to specific national origin, government affiliation, or established cybercriminal organization. The cluster's operational tradecraft (INC Ransom-derived encryptor, double-extortion model, ransom negotiation patterns, victim country avoidance consistent with Russian-aligned ecosystem norms) is consistent with the broader Russian-aligned cybercriminal ransomware ecosystem, but the exact operational-relationship between Lynx operators and INC Ransom operators remains analytically open. Possible operational scenarios include: (1) Lynx operators acquired INC Ransom source code from forum sale and operate as a distinct cluster from INC Ransom.

(2) Lynx is an operational rebrand of INC Ransom by the original operators.

(3) Lynx operators are former INC Ransom affiliates operating with retained access to the source code.

(4) some hybrid combination of these scenarios. The cluster operates as a financially-motivated cybercriminal operation with no known state sponsorship. The cluster is curated as a distinct cluster based on its distinct leak site infrastructure, distinct operational presentation, and operational continuity through 2024-2025 that postdates the operational visibility decline of INC Ransom in the same period.

Motivations
financial_gain, ransomware_extortion, double_extortion_data_exfiltration_and_encryption, cross_platform_ransomware_deployment, ransom_payment_extraction
Sectors
Regions

Detection Blind Spots

60 techniques
Across this actor’s 60 mapped techniques, the share covered by each detection layer. Low bars are where you’d be blind if this actor targeted you.
Behavioral / log (Sigma)56/60 · 93%
Analytics (MITRE CAR)37/60 · 61%
Runtime / container (Falco)9/60 · 15%
File / malware (YARA)1/60 · 1%
Network (Suricata/Snort)18/60 · 30%
Vuln scan (Nuclei)0/60 · 0%

Atomic Test Plan

30 techniques
Runnable Atomic Red Team tests covering this actor’s mapped techniques - validate your detections against this specific adversary. Cross-reference the blind spots above. For authorized lab / purple-team use. Open the full builder

Tools Used

1 mapped
Other tooling / TTPs (curation, not ATT&CK-mapped):
SOFTPERFECT NETWORK SCANNER

CVEs Exploited

2
Intelligence Graph · click any node to traverse
CVETechnique ActorTool Family
drag to reposition · click any node to traverse · button top-right enlarges
External lookups - second-class, for what we don’t hold ourselves
Vulnerabilities
CISA KEV catalog
CWE weaknesses
CAPEC attack patterns
Package vulnerabilities
Threat intelligence
Threat actors
Tools & malware
ATT&CK techniques
IOCs
Detection & defense
Sigma rules
YARA rules
Atomic Red Team tests
D3FEND countermeasures
Compliance
NIST 800-53
ISO 27001:2022
SOC 2 TSC
PCI-DSS v4.0
CIS Controls v8.1
About
All capabilities
Live statistics
Data sources
Privacy policy
Terms of service
threatengine.sh  ·  Open-source threat intelligence platform  ·  100+ authoritative sources  ·  Every fact traces to its origin