Which versions of price-scripping-js are malicious?

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

How do I remediate price-scripping-js if I installed it?

price-scripping-js is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed price-scripping-js — how do I know if it already compromised me?

If price-scripping-js was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is price-scripping-js part of a known attack campaign?

Yes — price-scripping-js is associated with the IN-MAL-2026-018386 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 price-scripping-js across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for price-scripping-js (version 1.1.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging price-scripping-js across your stack and pipelines.

Malicious package

price-scripping-jsnpm

price-scripping-js is a confirmed malicious npm package (MAL-2026-14272) that steals credentials and exfiltrates sensitive data (malicious version 1.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in price-scripping-js (npm)

MAL-2026-14272

Immediate action

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

npm uninstall price-scripping-js

What this malware does

[email protected] runs node dist/postinstall.js as its npm postinstall script. That entry point resolves the installing project's root via process.env.INIT_CWD?? process.cwd(), reads the project's .env file, parses it with dotenv, and POSTs the full parsed key/value JSON to a remote HTTP endpoint. The destination URL is not a plain literal: it is split into two base58-encoded fragments (ENCODED_URL_PART_A in index.js, ENCODED_URL_PART_B in cli.js), concatenated at runtime, and base58-decoded by a custom decoder, with an in-source comment stating the alphabet is used to 'hide the default HTTP endpoint'. Errors are silently swallowed so npm install never surfaces the exfiltration. The package advertises itself in package.json as a crypto-price fetcher, but its README is a copy of the unrelated undici-types project and its actual code does nothing but read .env and upload it. .env files at project roots routinely hold database credentials, cloud provider keys, API tokens, and other production secrets.

Malicious versions

1 flagged

1.1.2

Indicators of compromise (SHA-256)

52b5a1792ab4822af305a8d853e858a8063d9e82e5d91d3dbd3a748300aaf7f9

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for price-scripping-js (version 1.1.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging price-scripping-js across your stack and pipelines.
If you installed it — respond
price-scripping-js is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If price-scripping-js was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks price-scripping-js before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. price-scripping-js 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-018386

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks price-scripping-js-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database