Which versions of whatnot-manifests are malicious?

The following npm versions of whatnot-manifests are flagged malicious: 99.0.4. Treat any of these as compromised.

How do I remediate whatnot-manifests if I installed it?

Remove whatnot-manifests 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.

I already installed whatnot-manifests — how do I know if it already compromised me?

If whatnot-manifests 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.

How do I find whatnot-manifests across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for whatnot-manifests (version 99.0.4).

Malicious package

whatnot-manifestsnpm

Advisory published Mar 19, 2026Updated Mar 23, 2026

whatnot-manifests is a confirmed malicious npm package (MAL-2026-1582) that executes malicious code on install (malicious version 99.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in whatnot-manifests (npm)

MAL-2026-1582

Immediate action

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

npm uninstall whatnot-manifests

What this malware does

The package whatnot-manifests was found to contain malicious code.

The OpenSSF Package Analysis project identified 'whatnot-manifests' @ 99.0.4 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.0.4

Indicators of compromise (SHA-256)

050ffab3343a46b5adab9d17bf1d817086d336b52579f1f9c416e05355707873

2f0504ddd24de9ec3870bb8fc657436f5a61e3f6327f0e044bc380bfe3479d40

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for whatnot-manifests (version 99.0.4).
If you installed it — respond
Remove whatnot-manifests 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 whatnot-manifests 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

No. whatnot-manifests on npm has been identified as a malicious package (version 99.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks whatnot-manifests-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database