Attackers have compromised 10 npm packages, introducing hidden code into 12 releases This article explores polinrider loaders hacked. . Sonatype Research Labs confirmed this finding on November 4, 2026, and assigned it the identifier sonatype-2026-010515, with a high severity score of 8.7.

According to technical research published by Sonatype Research Labs, each loader queries public Ethereum RPC servers for a transaction sent by a fixed wallet, 0x1eef0849eda15d87f64e51c73c8442cf3c8bcef3. Blocking one server doesn't stop malware from targeting the next one.

A similar tactic was employed in earlier PolinRider activities, where loaders in open-source projects hid JavaScript and used blockchain services to fetch a second stage. GitGuardian's GhostAction and PolinRider reports from October 27, 2026, identify this exact wallet as the Ethereum resolver in PolinRider loaders found in hacked GitHub repositories. PolinRider is also older than it initially appeared, with OpenSourceMalware tracing its code back to npm packages from May 2025, months before the first known victims in January 2026.

A Sonatype community report indicates that later stages install a Node remote access trojan that persists through startup files for tools like VS Code, Cursor, Discord, and GitHub Desktop. Look for detached Node processes initiated by another Node process and plain HTTP requests to port 443 that use /0x/cls or /0x/ls. Ensure any affected processes rotate their secrets, including npm publishing tokens, source repository access, cloud keys, and CI secrets.