Malicious code in libas-signal (npm)
The libas-signal npm package version 1.0.0 contains malicious code that modifies an unrelated dependency on disk to inject a persistent payload. This payload silently issues a FOLLOW command against a hardcoded WhatsApp newsletter channel using the installer's authenticated session. The package masquerades as a legitimate Signal Protocol library, but this is a cover for its dependency-tampering behavior.
AI Analysis
Technical Summary
The libas-signal npm package (version 1.0.0) includes malicious code that, upon being required, schedules execution of an install.js script. This script locates the installer's @whiskeysockets/baileys package and overwrites its lib/Socket/newsletter.js file with a modified version containing injected code. When the installer runs their Baileys-based WhatsApp bot, the injected code silently issues a FOLLOW newsletterWMexQuery against a hardcoded WhatsApp channel (120363407277177688@newsletter) using the installer's authenticated WhatsApp session. The malicious patch persists on disk after libas-signal exits and continues running inside the unrelated dependency. The package falsely advertises itself as a Signal Protocol/Whisper Systems crypto library, using copied Signal Protocol source code as a cover for this dependency-tampering payload.
Potential Impact
This malicious package compromises the integrity of the installer's WhatsApp bot by injecting unauthorized code into a trusted dependency, enabling silent subscription to a hardcoded WhatsApp newsletter channel using the installer's authenticated session. This can lead to unauthorized actions performed without the installer's knowledge and potential privacy breaches. The persistence of the injected code on disk means the compromise continues beyond the initial execution of libas-signal.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid using libas-signal version 1.0.0 and remove it from their projects. Inspect and restore any modified files in the @whiskeysockets/baileys package, particularly lib/Socket/newsletter.js, from a trusted source. Monitor for unauthorized WhatsApp activity related to the hardcoded channel. Patch status is not yet confirmed — check the vendor advisory or trusted security sources for updates.
Malicious code in libas-signal (npm)
Description
The libas-signal npm package version 1.0.0 contains malicious code that modifies an unrelated dependency on disk to inject a persistent payload. This payload silently issues a FOLLOW command against a hardcoded WhatsApp newsletter channel using the installer's authenticated session. The package masquerades as a legitimate Signal Protocol library, but this is a cover for its dependency-tampering behavior.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The libas-signal npm package (version 1.0.0) includes malicious code that, upon being required, schedules execution of an install.js script. This script locates the installer's @whiskeysockets/baileys package and overwrites its lib/Socket/newsletter.js file with a modified version containing injected code. When the installer runs their Baileys-based WhatsApp bot, the injected code silently issues a FOLLOW newsletterWMexQuery against a hardcoded WhatsApp channel (120363407277177688@newsletter) using the installer's authenticated WhatsApp session. The malicious patch persists on disk after libas-signal exits and continues running inside the unrelated dependency. The package falsely advertises itself as a Signal Protocol/Whisper Systems crypto library, using copied Signal Protocol source code as a cover for this dependency-tampering payload.
Potential Impact
This malicious package compromises the integrity of the installer's WhatsApp bot by injecting unauthorized code into a trusted dependency, enabling silent subscription to a hardcoded WhatsApp newsletter channel using the installer's authenticated session. This can lead to unauthorized actions performed without the installer's knowledge and potential privacy breaches. The persistence of the injected code on disk means the compromise continues beyond the initial execution of libas-signal.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid using libas-signal version 1.0.0 and remove it from their projects. Inspect and restore any modified files in the @whiskeysockets/baileys package, particularly lib/Socket/newsletter.js, from a trusted source. Monitor for unauthorized WhatsApp activity related to the hardcoded channel. Patch status is not yet confirmed — check the vendor advisory or trusted security sources for updates.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-14291
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a85b4b4acd9273b49251539
Added to database: 08/19/2026, 13:50:44 UTC
Last enriched: 08/19/2026, 14:15:10 UTC
Last updated: 08/19/2026, 14:15:10 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.