Which versions of sound_deer_apricot-15 are malicious?

The following npm versions of sound_deer_apricot-15 are flagged malicious: 2.1.4. Treat any of these as compromised.

How do I remediate sound_deer_apricot-15 if I installed it?

sound_deer_apricot-15 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed sound_deer_apricot-15 — how do I know if it already compromised me?

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

Search your lockfiles and build artifacts for sound_deer_apricot-15 (version 2.1.4).

Malicious package

sound_deer_apricot-15npm

Advisory published Nov 2, 2026Updated Nov 4, 2026

sound_deer_apricot-15 is a confirmed malicious npm package (MAL-2026-18617) that opens a backdoor for remote access (malicious version 2.1.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sound_deer_apricot-15 (npm)

MAL-2026-18617

Immediate action

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

npm uninstall sound_deer_apricot-15

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.1.4; tarball SHA-256 27600206fc32a99f42d2dc8e77a71b222ae457b0345dfec2f397d6883b49f9f4.

Malicious versions

1 flagged

2.1.4

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for sound_deer_apricot-15 (version 2.1.4).
If you installed it — respond
sound_deer_apricot-15 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If sound_deer_apricot-15 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. sound_deer_apricot-15 on npm has been identified as a malicious package (version 2.1.4 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 sound_deer_apricot-15-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database