Security & privacy

Active exploits hit N-able, Chrome, and Windows as supply chain attacks rise

Attackers exploited zero-day flaws in N-able and Chrome while compromising open-source libraries to steal crypto keys. Default passwords also exposed vehicle control systems.

Server racks under a glass dome with warning lights and digital locks
Illustration created for this article

The week of November 16, 2026, brought a surge of active exploitation targeting critical infrastructure and widely used software. Attackers leveraged zero-day vulnerabilities in N-able’s remote monitoring tools and Google Chrome, while simultaneously compromising open-source JavaScript libraries to distribute malware. These incidents highlight how both sophisticated supply chain attacks and basic configuration errors continue to threaten self-hosted environments and enterprise networks alike.

What happened

A new set of vulnerabilities known as 4EverAble2Shell is being actively exploited to drop cryptocurrency miners on vulnerable servers. According to Huntback, attackers have successfully compromised 21 N-central servers across the United States, South Africa, Canada, the United Kingdom, Germany, France, and Sweden. The flaw allows unauthorized access to these management platforms, which are often used by IT service providers to monitor client infrastructure. Patches for the vulnerability were expected from N-able on the day of the report.

In the open-source ecosystem, threat actors compromised bee-js, the JavaScript client for the Swarm storage network. Version 13.3.0 included a malicious postinstall hook that downloaded a second-stage payload designed to steal Swarm node wallet keys and install backdoors. On Linux and macOS, this backdoor operates as a Go remote shell, while on Windows it installs a hidden ScreenConnect client running with SYSTEM privileges. The same malicious code was distributed via Swarm Desktop 0.56.2 on GitHub. SafeDep linked this activity to the SleepyDuck campaign, noting that the attacker controlled two Ethersphere GitHub accounts and injected workflows to steal CI credentials before using a release bot to publish the compromised versions.

Google also released urgent updates for Chrome to patch a high-severity use-after-free bug in the XML component, tracked as CVE-2026-125350. This vulnerability has been under active exploitation in the wild, though Google did not disclose specific details about the attack vector. The fix is included in version 157.0.8103.50/.51 for Windows and macOS, and 157.0.8103.50 for Linux. Additionally, security researcher Abdelhamid Naceri released SignDrop, a new Windows zero-day exploit that abuses the Common Log FileSystem authentication mechanism to gain SYSTEM privileges, turning a defensive feature into an attack surface.

Key details

  • N-able Exploitation: The 4EverAble2Shell vulnerabilities have compromised 21 N-central servers globally, leading to cryptocurrency miner deployment.
  • Supply Chain Compromise: Malicious code was injected into bee-js version 13.3.0 and Swarm Desktop 0.56.2, stealing wallet keys and installing backdoors.
  • Chrome Zero-Day: CVE-2026-125350, a use-after-free bug in Chrome’s XML component, is being actively exploited in the wild.
  • Windows Privilege Escalation: The SignDrop exploit abuses CLFS signing mechanisms to create privileged files in attacker-controlled locations.
  • Automotive Security Lapse: Researchers found default admin passwords on login servers for two major automakers, allowing remote vehicle control.
  • Meta Fine: Italy fined Meta €805 million for accessing Android user photos without proper disclosure or consent.

Background

Supply chain attacks occur when attackers compromise a trusted software vendor or library to distribute malware to its users. In the case of bee-js, the attackers did not need to breach every individual user; instead, they compromised the build process or repository of the library itself. This means any developer or system that automatically updated to version 13.3.0 inadvertently installed the backdoor. Such attacks are particularly dangerous for self-hosters who rely on automated updates for convenience, as they bypass traditional perimeter defenses.

Zero-day vulnerabilities are security flaws that are unknown to the vendor or for which no patch is yet available. When these are actively exploited "in the wild," it means attackers are already using them to compromise systems before a fix can be widely deployed. The SignDrop exploit demonstrates a complex technique where a security feature intended to validate data integrity is manipulated to perform unauthorized file operations. This highlights the difficulty of securing complex operating system components like the Windows Common Log FileSystem.

Why it matters

For teams running their own software, the N-able and bee-js incidents underscore the risk of trusting third-party management tools and dependencies. If you use remote monitoring and management (RMM) tools like N-central, your entire infrastructure could be exposed if the central server is compromised. Similarly, relying on open-source libraries without verifying their integrity or pinning versions can lead to silent compromises. The fact that the bee-js attack involved stealing CI credentials suggests that attackers are targeting the development pipeline itself, which can have long-term implications for software integrity.

The active exploitation of Chrome and Windows zero-days means that delay in patching is no longer just a theoretical risk but an immediate threat. For sysadmins managing fleets of devices, the window between vulnerability disclosure and active exploitation is shrinking. The automotive example further illustrates that even non-traditional IT assets are vulnerable to basic hygiene failures like default passwords. These stories collectively show that security is not just about advanced threats but also about fundamental practices like credential management and timely updates.

What you can do

  • Patch N-able and Chrome Immediately: Apply the latest patches for N-central and update Chrome to version 157.0.8103.50 or later on all endpoints.
  • Audit Open-Source Dependencies: Check if your projects use bee-js or Swarm Desktop and revert to known safe versions if compromised versions were installed.
  • Verify CI/CD Integrity: Review GitHub Actions workflows and CI credentials for signs of unauthorized access, especially if you maintain open-source projects.
  • Enforce Strong Authentication: Ensure all administrative interfaces, including those for IoT or automotive systems, use unique, strong passwords and multi-factor authentication.
  • Monitor for Anomalies: Look for unusual outbound connections or high CPU usage that might indicate cryptocurrency mining or backdoor activity on your servers.
  • Limit Privileges: Restrict SYSTEM-level access and ensure that services run with the least privilege necessary to reduce the impact of potential exploits like SignDrop.

More news

All news