Which versions of diezyclutch-baileys are malicious?

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

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

diezyclutch-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 diezyclutch-baileys — how do I know if it already compromised me?

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

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

Malicious package

diezyclutch-baileysnpm

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

Malicious code in diezyclutch-baileys (npm)

MAL-2026-13482

Immediate action

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

npm uninstall diezyclutch-baileys

What this malware does

diezyclutch-baileys is a fork of the Baileys WhatsApp library. In lib/Socket/messages-send.js the code constructs a network destination from a String.fromCharCode(...) array that decodes to https://fiora.nixel.my.id/ and issues outbound requests to that host from the message-sending path. Reconstructing the destination URL from a decimal char-code array is deliberate obfuscation of the exfil endpoint; the host is not part of Baileys' documented WhatsApp/Signal protocol traffic and is not a caller-configurable option. This is the canonical shape of a covertly injected exfiltration channel in a WhatsApp-session library, whose messages-send path handles session-authenticated data.

Malicious versions

1 flagged

8.6.78

Indicators of compromise (SHA-256)

b034105b4e65e2ff38eef557d7b480758070d1122aa6338a6873a9ee76f9111a

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 diezyclutch-baileys (version 8.6.78). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging diezyclutch-baileys across your stack and pipelines.
If you installed it — respond
diezyclutch-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 diezyclutch-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 diezyclutch-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. diezyclutch-baileys on npm has been identified as a malicious package (version 8.6.78 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016852

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks diezyclutch-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