Which versions of whatnot-web are malicious?

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

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

Remove whatnot-web 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-web — how do I know if it already compromised me?

If whatnot-web 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-web across my projects, lockfiles, and CI pipelines?

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

Malicious package

whatnot-webnpm

Advisory published Mar 19, 2026Updated Mar 23, 2026

whatnot-web is a confirmed malicious npm package (MAL-2026-1583) 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-web (npm)

MAL-2026-1583

Immediate action

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

npm uninstall whatnot-web

What this malware does

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

The OpenSSF Package Analysis project identified 'whatnot-web' @ 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)

6e4b52e600b6b37ce05a8127ddcabb58fc003b16c47afeec65118f1cb70008b8

4e7124b844cb92c573d57e94d1060a58445a82d03984c430e1632807fda9d227

Detection & response playbook

Malicious package

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