amundi-comparenpm
amundi-compare is a confirmed malicious npm package (MAL-2026-14390) that executes malicious code on install (malicious version 999.9.12). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in amundi-compare (npm)
What this malware does
[email protected] is published at an inflated version number consistent with dependency-confusion targeting of an internal package name. The package.json declares a preinstall hook (node index.js) that runs automatically on npm install. index.js collects hostname, OS user, home directory, current working directory, local IPv4 addresses, public egress IP (queried from api.ipify.org, icanhazip.com, and ifconfig.me), the DNS resolver IP and client subnet, and the parent project's package.json name/author/repository/homepage fields. The payload is transmitted through three parallel channels to the hardcoded callback host da51rv0hb2uc72tg4gvgdepinjcallbk1.oast.fun: an HTTP POST, an HTTPS POST to /poc/<uuid>, and a DNS covert channel that hex-encodes the JSON, splits it into <=60-character chunks, and emits each chunk as a subdomain label under the callback domain. The DNS channel is designed to bypass egress filters that block outbound HTTP. The package labels itself as authorized security research, but the callback host is not installer-configured and the parent project's metadata is captured without consent.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for amundi-compare (version 999.9.12). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging amundi-compare across your stack and pipelines.
If you installed it — respond
Remove amundi-compare 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 amundi-compare 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 amundi-compare 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks amundi-compare-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.