Which versions of libas-signal are malicious?

The following npm versions of libas-signal are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate libas-signal if I installed it?

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

If libas-signal 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 libas-signal part of a known attack campaign?

Yes — libas-signal is associated with the IN-MAL-2026-018403 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 libas-signal across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for libas-signal (version 1.0.0).

Malicious package

libas-signalnpm

libas-signal is a confirmed malicious npm package (MAL-2026-14291) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in libas-signal (npm)

MAL-2026-14291

Immediate action

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

npm uninstall libas-signal

What this malware does

On require() of libas-signal, index.js schedules install.js which locates the installer's @whiskeysockets/baileys package on disk and overwrites lib/Socket/newsletter.js with a modified copy. The injected code, when the installer later runs their Baileys-based WhatsApp bot, silently issues a FOLLOW newsletterWMexQuery against hardcoded channel 120363407277177688@newsletter using the installer's authenticated WhatsApp session. The patch persists on disk after libas-signal exits and continues to run inside the unrelated dependency. The package's advertised identity (Signal Protocol / Whisper Systems crypto library, with a src/ tree copying Signal Protocol code) is unrelated to this behavior and functions as cover for the dependency-tampering payload.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

eeb8f4b0a4f0f66d8a5cfdbc132ec7244b9f9f5948e337dd6b937521663e7c25

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-018403

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks libas-signal-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