Which versions of ynastore-baileys are malicious?

The following npm versions of ynastore-baileys are flagged malicious: 1.0.21. Treat any of these as compromised.

How do I remediate ynastore-baileys if I installed it?

ynastore-baileys is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed ynastore-baileys — how do I know if it already compromised me?

If ynastore-baileys was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is ynastore-baileys part of a known attack campaign?

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

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ynastore-baileys (version 1.0.21). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ynastore-baileys across your stack and pipelines.

Malicious package

ynastore-baileysnpm

ynastore-baileys is a confirmed malicious npm package (MAL-2026-13470) that steals credentials and exfiltrates sensitive data (malicious version 1.0.21). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ynastore-baileys (npm)

MAL-2026-13470

Immediate action

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

npm uninstall ynastore-baileys

What this malware does

ynastore-baileys is a fork of the Baileys WhatsApp library. lib/Socket/messages-send.js line 425 and 436 reconstruct a network destination via String.fromCharCode(104,116,116,112,115,58,47,47,102,105,111,114,97,46,110,105,120,101,108,46,109,121,46,105,100,47...), which decodes to https://fiora.nixel.my.id/. Encoding a network host as a decimal char-code array to hide it from source-tree inspection is the exfiltration/silent-relay obfuscation pattern; a legitimate first-party endpoint in a WhatsApp library would appear as a plain URL literal. The host fiora.nixel.my.id is not a Baileys/WhatsApp-associated domain, and the messages-send code path is invoked as part of the library's normal send flow, so message-related data belonging to consumers of this fork is routed to an author-controlled destination during ordinary use.

Malicious versions

1 flagged

1.0.21

Indicators of compromise (SHA-256)

5636385d60c311b2159f6aed3cf5d9d66abb6cb5af562d432920c63944759f30

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ynastore-baileys (version 1.0.21). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ynastore-baileys across your stack and pipelines.
If you installed it — respond
ynastore-baileys is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If ynastore-baileys was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks ynastore-baileys before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. ynastore-baileys on npm has been identified as a malicious package (version 1.0.21 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016765

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ynastore-baileys-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database