@ikyerza/baileysnpm
Advisory published Updated
@ikyerza/baileys is a confirmed malicious npm package (MAL-2026-20285) that executes malicious code on install (malicious versions 1.0.0, 1.1.1, 1.2.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @ikyerza/baileys (npm)
What this malware does
package.json declares the libsignal dependency as github:tenka-san/libsignal-node with no commit SHA or tag. On npm install, npm clones whatever the current HEAD of that personal GitHub repository is and executes any lifecycle scripts it contains on the installer's machine. The dependency key libsignal also shadows the published registry package of the same name, a dependency-confusion-shape aggravator: callers reading the manifest see a familiar name but resolution is redirected to a personal account that is not associated with the declared publisher of this package or of the upstream Baileys project. The repository owner can change the installed bytes at any time without any version bump in this package.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for @ikyerza/baileys (3 malicious versions).
If you installed it — respond
Remove @ikyerza/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 @ikyerza/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 @ikyerza/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.