Which versions of colossal_wallaby_pink-87 are malicious?

The following npm versions of colossal_wallaby_pink-87 are flagged malicious: 1.2.1. Treat any of these as compromised.

How do I remediate colossal_wallaby_pink-87 if I installed it?

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

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

Search your lockfiles and build artifacts for colossal_wallaby_pink-87 (version 1.2.1).

Malicious package

colossal_wallaby_pink-87npm

Advisory published Nov 2, 2026Updated Nov 4, 2026

colossal_wallaby_pink-87 is a confirmed malicious npm package (MAL-2026-18606) that executes malicious code on install (malicious version 1.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in colossal_wallaby_pink-87 (npm)

MAL-2026-18606

Immediate action

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

npm uninstall colossal_wallaby_pink-87

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.2.1; tarball SHA-256 eefa5998b053240ecd251b218193b2352c7dc55759fcaaeeb814f3c5fccf9539.

Malicious versions

1 flagged

1.2.1

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for colossal_wallaby_pink-87 (version 1.2.1).
If you installed it — respond
Remove colossal_wallaby_pink-87 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 colossal_wallaby_pink-87 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. colossal_wallaby_pink-87 on npm has been identified as a malicious package (version 1.2.1 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 colossal_wallaby_pink-87-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