Which versions of minify-replace are malicious?

The following npm versions of minify-replace are flagged malicious: 9.9.0. Treat any of these as compromised.

How do I remediate minify-replace if I installed it?

minify-replace 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 minify-replace — how do I know if it already compromised me?

If minify-replace 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 minify-replace part of a known attack campaign?

Yes — minify-replace is associated with the GHSA-c4qg-vqr5-vwq8 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 minify-replace 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 minify-replace (version 9.9.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging minify-replace across your stack and pipelines.

Malicious package

minify-replacenpm

Malicious code in minify-replace (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1503

Immediate action

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

npm uninstall minify-replace

What this malware does

The package 'minify-replace' is part of the PhantomRaven supply chain attack campaign (Wave 2). It uses a Remote Dynamic Dependency (RDD) technique: the published package appears benign but includes a URL-based dependency in package.json pointing to an attacker-controlled C2 server (npm.jpartifacts.com). During npm install, npm automatically fetches a malicious tarball from the C2. The tarball preinstall hook executes a 259-line payload that harvests developer emails from .gitconfig, .npmrc, and environment variables; collects CI/CD tokens from GitHub Actions, GitLab CI, Jenkins, and CircleCI; fingerprints the host system; and exfiltrates all data to http://npm.jpartifacts.com/jpd.php via redundant HTTP GET, POST, and WebSocket channels with no visible terminal output. The campaign was first disclosed by Koi Security in October 2025 (Wave 1) and extended across Waves 2-4 between November 2025 and February 2026. Full analysis: https://www.endorlabs.com/learn/return-of-phantomraven

Any developer or CI/CD system that installed this package should be considered compromised. All secrets, tokens, and credentials accessible from that environment should be rotated immediately from a separate, unaffected machine.

The package minify-replace was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

9.9.0

Indicators of compromise (SHA-256)

bc1cdc32189f65126189bc905bdea1854ac14e0a7ee50c598c1f37f6f46a2936

f790424307909385f6c0843b03307ad32c719b32a4fffb70acb9394b2b0ceb39

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 minify-replace (version 9.9.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging minify-replace across your stack and pipelines.
If you installed it — respond
minify-replace 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 minify-replace 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 minify-replace 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. minify-replace on npm has been identified as a malicious package (version 9.9.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-c4qg-vqr5-vwq8

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks minify-replace-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