Which versions of smooth_angelfish_emerald-54 are malicious?

The following npm versions of smooth_angelfish_emerald-54 are flagged malicious: 2.2.2. Treat any of these as compromised.

How do I remediate smooth_angelfish_emerald-54 if I installed it?

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

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

Search your lockfiles and build artifacts for smooth_angelfish_emerald-54 (version 2.2.2).

Malicious package

smooth_angelfish_emerald-54npm

Advisory published Nov 2, 2026Updated Nov 4, 2026

smooth_angelfish_emerald-54 is a confirmed malicious npm package (MAL-2026-18616) that executes malicious code on install (malicious version 2.2.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in smooth_angelfish_emerald-54 (npm)

MAL-2026-18616

Immediate action

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

npm uninstall smooth_angelfish_emerald-54

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: 2.2.2; tarball SHA-256 223ace08ab038a6ee47fd7d04a2f489d9d4817d4b147f164be1de264918235c1.

Malicious versions

1 flagged

2.2.2

Detection & response playbook

Malicious package

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