Which versions of @akapaki/baileys are malicious?

The following npm versions of @akapaki/baileys are flagged malicious: 1.0.0, 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate @akapaki/baileys if I installed it?

Remove @akapaki/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.

I already installed @akapaki/baileys — how do I know if it already compromised me?

If @akapaki/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 @akapaki/baileys part of a known attack campaign?

Yes — @akapaki/baileys is associated with the IN-MAL-2026-020672, IN-MAL-2026-020671, IN-MAL-2026-020673 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 @akapaki/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 @akapaki/baileys (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @akapaki/baileys across your stack and pipelines.

Malicious package

@akapaki/baileysnpm

@akapaki/baileys is a confirmed malicious npm package (MAL-2026-17285) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @akapaki/baileys (npm)

MAL-2026-17285

Immediate action

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

npm uninstall @akapaki/baileys

What this malware does

@akapaki/[email protected] is an unofficial republish of the Baileys WhatsApp library under a new scope (author paki, empty README, repository pernapasquale647-dotcom/paki-baileys). Its package.json declares the libsignal dependency as github:pernapasquale647-dotcom/paki-libsignal — a personal GitHub source with no commit SHA, tag, or integrity pin. npm install will fetch whatever the repo's default branch currently contains and run any lifecycle scripts inside it on the installer's machine, giving the repository owner unilateral, unaudited control over code executed at install time. The shipped lib/ has not been diffed against upstream Baileys, so behavioral drift from the legitimate library cannot be excluded.

Malicious versions

3 flagged

1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

0b075a3687b7dca26037d732cb682f79c4b9f3ff761fc6268a71982a311f46a5

28c9d6f6bb4eacd40be68ec8e1d2e33e70be84e1af18f9259647b8a77a8bf5f5

c14fdf44df68d2544cc235039ef40a99c7df7bcbfc968e8d5809762031f0dd16

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @akapaki/baileys (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @akapaki/baileys across your stack and pipelines.
If you installed it — respond
Remove @akapaki/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 @akapaki/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 @akapaki/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. @akapaki/baileys on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020672IN-MAL-2026-020671IN-MAL-2026-020673

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @akapaki/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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database