Which versions of voicemail are malicious?

The following npm versions of voicemail are flagged malicious: 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate voicemail if I installed it?

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

If voicemail 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.

Is voicemail part of a known attack campaign?

Yes — voicemail is associated with the IN-MAL-2026-014896, IN-MAL-2026-014898, RLMA-2026-10810 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find voicemail across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for voicemail (2 malicious versions).

Malicious package

voicemailnpm

Advisory published Aug 5, 2026Updated Sep 24, 2026

voicemail is a confirmed malicious npm package (MAL-2026-12496) that opens a backdoor for remote access (malicious versions 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in voicemail (npm)

MAL-2026-12496

Immediate action

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

npm uninstall voicemail

What this malware does

package.json declares both preinstall and postinstall lifecycle scripts that invoke curl against a hardcoded webhook.site endpoint (https://webhook.site/d80b4602-8a87-4693-8510-6ff77c62788e/blots) with query parameters carrying the installer's username ($(whoami)), hostname ($(hostname)), current working directory ($PWD), and a timestamp. The beacon fires automatically on npm install without user consent, sending host and identity reconnaissance to an attacker-controlled collector. The package provides no legitimate functionality corresponding to this network activity.

Malicious versions

2 flagged

1.0.11.0.2

Indicators of compromise (SHA-256)

6d31c2930aaf259b45a56e869bc0ee9293486c708895bf10d7438a580fe31aea

568a31285f414d8125b5749bc8e070157ffd403ce46e46da637cc1452f99d19f

eb6ccff903272648708d54bdd69b5b1f420743130c128b9460c8085f2072b412

Detection & response playbook

Backdoor / remote access

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

Campaign

IN-MAL-2026-014896IN-MAL-2026-014898RLMA-2026-10810

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks voicemail-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