Skip to content
File security for Windows systems — since 2003

How FileSure Would Have Stopped the 4EverAble2Shell and npm Supply-Chain Attacks

• By Gene Allen

The Attack: Multiple Vectors, One Common Requirement

The week of November 16, 2026 saw a coordinated assault across multiple attack vectors. Evildoers exploited zero-day vulnerabilities in N-able N-Central (tracked as 4EverAble2Shell), compromised the widely-used bee-js npm package to distribute wallet key stealers and ScreenConnect backdoors, leveraged a Windows CLFS privilege escalation flaw dubbed SignDrop to reach SYSTEM-level access, and deployed cryptominers across 21 servers in seven countries.

The attack paths varied — supply chain compromise, unauthenticated remote code execution, privilege escalation — but they all converged on the same technical requirement: writing malicious executables to disk on Windows systems.

The compromised npm package injected a malicious postinstall hook that downloaded and wrote wallet stealer executables and backdoor installers to developer workstations. The N-able exploit delivered cryptominer payloads that had to be written to disk before execution. The Windows CLFS exploit escalated privileges specifically to enable writing elevated-privilege payloads that normal user accounts couldn’t deploy.

No payload on disk means no execution. No execution means no encryption, no exfiltration, no lateral movement, no impact.

Why Signature-Based Detection Fails Here

The article notes that AI-accelerated vulnerability discovery is compressing defender response windows — Forescout found 99 flaws in 90 hours for under $1,000. That’s the new normal. Zero-days are cheap and fast to discover, and agentic ransomware is removing the human bottleneck from attack execution.

Signature-based detection is always playing catch-up. By the time your EDR vendor recognizes the new cryptominer variant or the novel wallet stealer, the payload has already landed on disk and started running. Detection after the fact means you’re in incident response mode — containing, remediating, hoping the backup wasn’t encrypted too.

This is the whack-a-mole problem: new attack, new signature, evildoer moves to the next variant.

The Kernel-Level Intervention Point

FileSure Defend operates at the Windows kernel level via a filter driver that intercepts file system operations before they complete. It enforces behavioral rules that define which users, programs, and machines can perform which file operations — independent of Windows permissions, independent of malware signatures.

A rule like this would have stopped both the npm supply-chain payload and the N-able cryptominer before they ever touched the disk:

File name filter: *.exe, *.dll, *.bat, *.ps1, *.vbs, *.scr
Program name filter: *\node.exe, *\chrome.exe, *\firefox.exe, *\outlook.exe, *\WINWORD.EXE, *\EXCEL.EXE
Operations: Write, Create
Drive type: Fixed Drive, Removable
Action: Deny and log

This rule says: programs that commonly deliver payloads — Node.js, browsers, email clients, Office applications — cannot write executable file types to disk. Period.

When the compromised bee-js package attempted to write the wallet stealer executable during its postinstall hook, FileSure would have intercepted the write operation, blocked it, and logged the attempt with full context: which user, which machine, which program (node.exe), the target file path, and the exact timestamp.

The cryptominer payload delivered via the N-able exploit would have been blocked the same way — the exploit might have succeeded in gaining code execution, but the moment it tried to write the miner executable to disk, the operation would have been denied at the kernel level.

No payload file means no execution. The attack stops before it starts.

The Windows CLFS privilege escalation exploit is interesting because it specifically targets the ability to write files with elevated privileges. But FileSure operates outside the Windows security model — even if the attacker escalates to SYSTEM, the kernel filter driver still enforces its rules. SYSTEM-level access doesn’t override a FileSure policy.

What This Looks Like in Practice

Organizations that deploy FileSure on developer workstations, managed service infrastructure, and production Windows servers get kernel-level enforcement of file operation policies without replacing their existing security stack.

A regional bank we work with deployed FileSure on their core banking infrastructure — legacy Windows systems running software that won’t run on anything newer. They passed their next PCI DSS audit using FileSure’s logs as primary evidence of access controls, and FileSure blocked multiple attempted data exfiltration incidents in the same period. The systems are still old. The software is still legacy. But unauthorized programs can’t write to those systems anymore.

The 4EverAble2Shell attacks hit managed service providers — exactly the kind of environment where a single compromised server can pivot to hundreds of client systems. Blocking the initial payload write on the MSP server stops the attack before it reaches any clients.

Try It on Your Systems

FileSure Defend installs on all Windows versions — including the ones modern security tools won’t touch. If you’re running legacy infrastructure that can’t be replaced, or managing client environments where a single compromise cascades across your entire customer base, start a free trial at bystorm.com and see what kernel-level file operation control looks like in your environment.


Source: N-able, Windows & Chrome Zero-Days Exploited | Weekly Threat Recap Nov 2026

Category: Ransomware

Tags: 4everabl2shell, n-able n-central, npm supply chain, cryptominer, kernel filter driver, zero-day exploitation, file system security, privilege escalation

Gene Allen

Written by

Gene Allen

Gene Allen is a Windows file security expert with over 20 years of experience developing kernel-level solutions that protect enterprise data from ransomware, unauthorized access, and data loss. As founder of ByStorm Software, he architected FileSure — a patented file auditing and security platform trusted by 200+ organizations across healthcare, financial services, and government. Gene holds two U.S. patents in file system security and access control.

Ready to protect your organization?

Start your free 21-day trial today. No credit card required.

Start Your Free 21-Day Trial