MAL-2026-16103 Malicious code in @neroxkira/vangal-baileys (npm)
Malicious package
Published
MAL-2026-16103 is a malicious package: @neroxkira/vangal-baileys (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-16103/ (Markdown: https://insights.sbomify.com/MAL-2026-16103/index.md)
- Package
- @neroxkira/vangal-baileys
- Registry
- npm
What is MAL-2026-16103?
MAL-2026-16103 is a malicious package in @neroxkira/vangal-baileys, published on 9 Sep 2026.
Official description
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.What should I do about MAL-2026-16103?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.