TechSignal.news
Cybersecurity

Ransomware Groups Hit 124 Active Crews as Identity Compromise Drops to Eight Minutes

Trellix counted 124 active ransomware groups in six months—the highest on record—while Elastic confirmed cloud account breaches in under eight minutes using phishing proxies that bypass conventional MFA.

TechSignal.news AI5 min read

Ransomware fragmentation creates a detection problem, not just a signature problem

Trellix reported 124 active ransomware groups during its latest six-month observation period, the highest count in its dataset, with 55 groups posting victims for the first time. Those new entrants represented 22% of all victim posts. Bitdefender separately counted 1,072 claimed ransomware victims during October 2026 alone.

The market is fragmenting rather than consolidating. The Gentlemen overtook Qilin as the most active extortion group, but no single brand dominates. Trellix found Data Encrypted for Impact in 96% of ransomware detections, with Windows Command Shell, PowerShell, PsExec, Net, and Mimikatz among the most frequently associated tools.

Buyers face a structural shift: defenses tuned to specific ransomware families lose value when 22% of victim posts come from groups that did not exist six months ago. The operational response is to prioritize controls that detect abuse of administrative tools—PowerShell, PsExec, credential dumpers—across all ransomware variants. That includes identity protection, privileged-access monitoring, immutable backup validation, and behavioral endpoint detection.

Budgets should reflect this. Incident-response retainers and behavioral detection deliver more coverage than narrowly tuned family-specific signatures. Claimed victim counts are directional, not audited—leak-site posts can include duplicate, exaggerated, or unverified claims—but the fragmentation trend is consistent across reporting.

Identity controls need to resist real-time phishing, not just credential reuse

Elastic reported that adversaries using phishing proxies and legacy authentication bypassed MFA and breached cloud accounts in under eight minutes in confirmed customer intrusions covering April through September 2026. The same report found automated in-memory exploits executing within seconds without writing to disk.

Conventional MFA deployment is becoming less differentiating. An eight-minute compromise window leaves no room for manual triage. Buyers should measure identity controls by resistance to real-time phishing proxies and legacy-protocol abuse, not by MFA enrollment rates alone.

Phishing-resistant authentication—passkeys, FIDO2—conditional access, identity-threat detection, and cloud-runtime telemetry become procurement criteria. Microsoft Entra ID, Okta, Cisco Duo, and CrowdStrike Falcon Identity Protection compete on these capabilities. Budgets may need to shift from endpoint-only tooling toward identity detection, session-risk controls, and rapid revocation workflows. Automated detection and containment should be evaluated in proof-of-concept testing with simulated credential-phishing scenarios.

cPanel authentication bypass exposes hosting and MSP customers to ransomware and botnet deployment

CVE-2026-41940 affects cPanel & WHM versions 11.40 through 11.136.0.4. Reporting cited approximately 1.5 million internet-accessible instances and described an authentication bypass that can allow attackers to write arbitrary credentials into session files and deploy SORRY ransomware or Mirai botnet agents.

The exposure creates risk beyond the corporate CMDB. Organizations should inventory cPanel versions across subsidiaries, hosting providers, and managed service providers. Exposure can affect both ransomware risk and downstream customer environments, making contractual patch SLAs and provider telemetry more important procurement criteria.

The incident increases pressure on hosting providers and web-infrastructure buyers to adopt external attack-surface management, virtual patching, and hardened control-panel alternatives. cPanel competes with Plesk, DirectAdmin, and provider-built management layers. The reported exposure count is an estimate of internet-accessible instances, not a confirmed count of vulnerable or compromised systems.

AI agents need distinct identities and emergency kill mechanisms

Trellix reported the emergence of autonomous agentic malware and significant credential-handling exposures in AI agents. Elastic similarly described attackers weaponizing AI assistants, npm supply chains, identity flows, and management tools.

Buyers are being pushed beyond traditional endpoint and email controls toward AI application security, agent identity governance, secrets management, software-supply-chain monitoring, and runtime policy enforcement. Every production AI agent should have a distinct identity, narrowly scoped credentials, auditable tool calls, short-lived secrets, and an emergency kill mechanism. AI projects that cannot provide those controls should face the same deployment friction as externally exposed applications.

Relevant competitive categories include Microsoft Security Copilot and Defender, Palo Alto Networks Prisma Cloud, Cisco AI Defense, and specialist AI-security vendors. The available reports identify the threat pattern but do not provide a comparable enterprise-wide compromise rate or dollar-loss figure, making this a significant emerging risk rather than a quantified market-impact estimate.

Linux, VMware ESXi, and backup infrastructure require separate monitoring budgets

Acronis reported that ransomware is reaching deeper into Linux and VMware ESXi environments, while attackers are deliberately disabling endpoint protection and logging to create blind spots. The report also warned that AI-assisted attackers can develop and weaponize exploits within hours, shrinking the patch-response window.

Buyers may need broader coverage than Windows endpoint suites provide, including hypervisor protection, backup immutability, workload isolation, and recovery validation. Recovery products should be evaluated as security controls, not only backup tools. Procurement tests should verify that backups remain accessible after administrator compromise, that ESXi management planes are monitored, and that security agents cannot be disabled without generating an independent alert.

This benefits vendors such as Rubrik, Veeam, Cohesity, Sophos, Trend Micro, and security platforms with Linux and virtualization telemetry. Enterprises with high VMware or Linux concentration may need to fund hypervisor and backup-plane monitoring separately from endpoint protection.

What to watch

The near-term buying signal is not a single ransomware family or zero-day. It is the convergence of fragmented ransomware crews, sub-eight-minute identity compromise, internet-facing control-panel exposure, and attacks against AI agents and virtualization infrastructure. Buyers should prioritize phishing-resistant identity, attack-surface inventory, behavioral ransomware detection, protected recovery infrastructure, and controls that cover non-Windows enterprise systems. The available reporting is largely vendor research rather than independently audited incident data, so treat the figures as directional but actionable.

ransomwareidentity securityMFAcloud securitycybersecurity

Technology decisions, clearly explained.

Weekly analysis of the tools, platforms, and strategies that matter to B2B technology buyers. No fluff, no vendor spin.

More in Cybersecurity