Nullify

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Home
›
Incidents
›
PolinRider Loader in Hijacked npm Packages: What Happened and How to Check
Supply chain
Direct

PolinRider Loader in Hijacked npm Packages: What Happened and How to Check

Twelve releases across ten hijacked npm packages carried a runtime loader that finds its command server through Ethereum transactions and can change its payload remotely.

Nullify Team
·
Disclosed
November 4, 2026
·
Updated
November 17, 2026

What happened with the PolinRider npm packages?

In its research, Sonatype says attackers published 12 releases across 10 hijacked npm packages on November 3, 2026, some to packages that hadn't been updated in years. The releases contain a concealed runtime loader with no install hooks; it runs when the application loads the injected file.

Sonatype says the loader finds its command-and-control address from transactions sent by a hard-coded Ethereum wallet, then fetches encoded JavaScript over plain HTTP on port 443 and runs it. Because the wallet acts as a dead drop, blocking one server doesn't stop the loader, and the payload can change without a new npm release. The wallet matches loaders GitGuardian found in compromised GitHub repositories in October.

Which npm packages are affected?

  • @adminide-stack packages: client-redux, health-api-server, user-activity-browser, utils, forms-core and yantra-help-browser at the versions Sonatype lists.
  • server-hemera-mongo 0.0.15 and 0.0.16, cdeops 13.5.31, @cdmbase/wiki-browser 12.0.18-alpha.53 and @pubngo-stack/help-browser 12.0.23-alpha.3.
  • Any project that pulls these releases transitively.

How to check if you're affected

  1. Search lockfiles, internal mirrors, caches and build records for the listed versions, including transitive dependencies.
  2. On hosts, look for detached node -i processes with piped input and plain HTTP to port 443 on paths /0x/cls or /0x/ls.
  3. Check firewall logs for 95.135.181.151 and requests carrying the Sec-V header values Sonatype lists.

What to do now

  1. Replace affected versions with independently verified clean versions.
  2. Block the affected releases in mirrors, caches and dependency firewalls, and keep copies for investigation.
  3. If the code ran, treat the host as compromised and rotate publishing, source-control, cloud and CI credentials.
  4. Base the assessment on process, network and runtime records, not on the installed version alone.

Why abandoned packages make good targets

Packages that haven't shipped in years still sit in thousands of dependency trees, and nobody is watching for new releases. When one suddenly publishes again, that's a signal worth a closer look. Alert on releases from long-dormant dependencies, adopt a cooldown before taking brand-new versions, and prefer pinned versions over broad ranges for packages you don't actively track.

Where Nullify fits

How Nullify Covers This Class of Attack

Direct
Supply Chain Attack

Nullify finds every repository and container image that pulls an affected package version and runs the upgrade as one campaign, scoped by CVE, package, repo or team, with owners, Slack escalation and SLA tracking. Your developers approve every merge.

Nullify can't tell you whether the payload ran on a given machine or runner. Use the checks above for that, then fix the dependency everywhere it appears.

Frequently Asked Questions

Which npm packages contain the PolinRider loader?

Sonatype lists 12 releases across 10 packages published November 3, 2026, mostly in the @adminide-stack scope, plus server-hemera-mongo, cdeops, @cdmbase/wiki-browser and @pubngo-stack/help-browser at specific versions.

How does the PolinRider loader find its server?

It reads transactions sent by a hard-coded Ethereum wallet to get its command server address, then fetches encoded JavaScript over plain HTTP on port 443. Blocking one server doesn't stop it, because the wallet can point to a new one.

What should I do if I installed an affected release?

Replace it with a verified clean version, block the release in your mirrors, and if the code ran, treat the host as compromised and rotate publishing, source-control, cloud and CI credentials.

Update Log

  • Nov 17, 2026: page published from the primary sources linked above.

Check your own code for the bug behind this incident

Nullify's AI harness finds, proves and fixes the same class of vulnerability in your code and dependencies, and hands your team a merge-ready pull request.