Which versions of hollow_wildebeest_silver-94 are malicious?

The following npm versions of hollow_wildebeest_silver-94 are flagged malicious: 1.1.2. Treat any of these as compromised.

How do I remediate hollow_wildebeest_silver-94 if I installed it?

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

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

Search your lockfiles and build artifacts for hollow_wildebeest_silver-94 (version 1.1.2).

Malicious package

hollow_wildebeest_silver-94npm

Advisory published Nov 2, 2026Updated Nov 4, 2026

hollow_wildebeest_silver-94 is a confirmed malicious npm package (MAL-2026-18609) that executes malicious code on install (malicious version 1.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hollow_wildebeest_silver-94 (npm)

MAL-2026-18609

Immediate action

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

npm uninstall hollow_wildebeest_silver-94

What this malware does

Part of a self-republishing campaign: generated names of the form <adjective><animal><colour>-<number>, each package shipping the same autopublish.js, which runs npm publish --access public to publish the package again. Self-replicating publication is the propagation step of a registry worm and fills the registry with copies. Version examined: 1.1.2; tarball SHA-256 01f53d63acbd1e1c1275a099ac442ab52446e4fa180395088fd49c7a168f193c.

Malicious versions

1 flagged

1.1.2

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for hollow_wildebeest_silver-94 (version 1.1.2).
If you installed it — respond
Remove hollow_wildebeest_silver-94 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 hollow_wildebeest_silver-94 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. hollow_wildebeest_silver-94 on npm has been identified as a malicious package (version 1.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Oluwatosin Amokeodo · finder

Detect & block this

O3 blocks hollow_wildebeest_silver-94-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