@neroxkira/vangal-baileysnpm
Advisory published Updated
@neroxkira/vangal-baileys is a confirmed malicious npm package (MAL-2026-16103) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @neroxkira/vangal-baileys (npm)
What this malware does
package.json declares libsignal with the source github:RILLYZY/libsignal-node, an unpinned reference to a third-party GitHub repository with no tag or commit SHA. On npm install, npm clones that repository's default branch HEAD and runs any lifecycle scripts contained in it; libsignal-node ships a native addon with build-time scripts. There is no version pin, hash, or integrity check, so whoever controls RILLYZY/libsignal-node controls install-time code execution on every installer of this package. The referenced GitHub account is unrelated to the libsignal upstream (signalapp) and to any publisher identity declared by this package.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for @neroxkira/vangal-baileys (2 malicious versions).
If you installed it — respond
Remove @neroxkira/vangal-baileys 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 @neroxkira/vangal-baileys 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @neroxkira/vangal-baileys-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.