Which versions of poly-price-node are malicious?

The following npm versions of poly-price-node are flagged malicious: 1.1.2. Treat any of these as compromised.

How do I remediate poly-price-node if I installed it?

Remove poly-price-node from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed poly-price-node — how do I know if it already compromised me?

If poly-price-node was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is poly-price-node part of a known attack campaign?

Yes — poly-price-node is associated with the IN-MAL-2026-018645 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find poly-price-node across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for poly-price-node (version 1.1.2).

Malicious package

poly-price-nodenpm

Advisory published Aug 24, 2026Updated Aug 24, 2026

poly-price-node is a confirmed malicious npm package (MAL-2026-14436) that executes malicious code on install (malicious version 1.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in poly-price-node (npm)

MAL-2026-14436

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall poly-price-node

What this malware does

[email protected] advertises itself as a crypto-price fetcher but its package.json postinstall script invokes prices()->uploadConfigIfExists(), which reads the installer's.env file from INIT_CWD/cwd, parses it with dotenv, and POSTs the parsed key/value pairs as JSON to a hardcoded remote URL. The destination URL is not a literal string: it is reconstructed at runtime from two base58-encoded fragments (str_aa in dist/index.js and str_b in dist/cli.js) via a custom base58->BigInt->hex->utf8 decoder whose alphabet comment explicitly states it is used to hide the default HTTP endpoint. Fetch failures are silently swallowed. The README is copied from an unrelated package (undici-types) to disguise the tarball's actual behavior. The.env file typically holds API keys, database URLs, and other production secrets, all of which are transmitted to the author-controlled endpoint automatically on npm install.

Malicious versions

1 flagged

1.1.2

Indicators of compromise (SHA-256)

219fd8bc805a260cc62a5a3f9d524f9bb69ba2f8c5ae65e9a13e64514fdd0cf6

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for poly-price-node (version 1.1.2).
If you installed it — respond
Remove poly-price-node from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If poly-price-node was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. poly-price-node on npm has been identified as a malicious package (version 1.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018645

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks poly-price-node-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database