Daily Summary
INC Ransom produced 100 new samples on 2026-10-25, against a 7-day average of zero. This is the first tracked activity from this family in the reporting window, so the percentage trend is an artifact of a zero baseline rather than a meaningful rate of change. Treat this as an initial burst from a previously dormant or untracked cluster rather than a measured surge, and prioritize establishing a baseline over the next several days.
New Samples Detected
The file type split is the most informative signal today. Executables (.exe) account for 53 samples and ELF binaries (.elf) for 38, meaning nearly 40 percent of the corpus targets Linux. That is unusual for a ransomware brand historically associated with Windows enterprise intrusion. A Linux payload set of this size suggests either an ESXi/virtualization play or a pivot toward server-side and cloud-hosted victims, both consistent with the broader RaaS shift toward hypervisor and NAS targets. The remainder is small: 5 DLLs, 2 .dotm macro documents, 1 Python script, and 1 PowerShell script. The presence of a lone .py and a lone .ps1 alongside the compiled payloads points to a staging or loader layer rather than standalone tooling, though two script samples is too thin to characterize a toolchain.
Distribution Methods
The .dotm macro documents and script stagers indicate that at least part of this wave relies on user-executed delivery, likely phishing attachments or archive-borne loaders, while the bulk of compiled .exe and .elf samples would arrive through secondary stages. The channel mix is not yet attributable from sample data alone. Analysts should watch email gateway and web proxy telemetry for macro-bearing attachments referencing INC branding or invoice-style lures in the coming 48 hours.
C2 Infrastructure
No new C2 servers were recorded despite 100 new IOCs. This is the key gap in today’s picture: the IOCs are almost certainly file-level (hashes, paths, mutexes, embedded strings) with no resolved infrastructure behind them yet. That pattern fits samples that are either not yet detonated, rely on victim-side configuration, or use hardcoded or dormant endpoints. Do not assume absence of C2 indicators means absence of C2 capability.
IOC Highlights
All 100 new IOCs are hash- and artifact-level, with no network indicators. Blocking should therefore focus on execution detection rather than perimeter filtering. Prioritize hunting for the .elf samples on Linux hosts and hypervisors, and for the 5 DLLs as potential side-load or persistence components on Windows endpoints.
Security Analysis
The Windows/Linux near-parity here diverges from INC Ransom’s better-documented Windows-centric intrusion pattern and resembles the ESXi-oriented tradecraft now common across RaaS affiliates. A 38-sample ELF set appearing in a single day, with zero resolved C2, is more consistent with a builder or affiliate kit being distributed than with active exfiltration infrastructure. An actionable recommendation: treat this as a detection-engineering day, not a blocking day. Deploy file-hash rules for all 100 IOCs into EDR and AV, enable command-line logging on Linux hypervisor management hosts, and alert on bulk VM snapshot or datastore operations from those systems. Re-check C2 attribution at the next reporting cycle; if endpoints remain unresolved, escalate to sandbox detonation to recover configuration.