Which versions of amanexzyra-baileys are malicious?

The following npm versions of amanexzyra-baileys are flagged malicious: 3.0.0, 4.0.0, 4.0.2. Treat any of these as compromised.

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

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

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

Yes — amanexzyra-baileys is associated with the GHSA-mwwh-7r57-h6v9, IN-MAL-2026-013002, IN-MAL-2026-013024, IN-MAL-2026-013026 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 amanexzyra-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 amanexzyra-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 amanexzyra-baileys across your stack and pipelines.

Malicious package

amanexzyra-baileysnpm

amanexzyra-baileys is a confirmed malicious npm package (MAL-2026-11081) that steals credentials and exfiltrates sensitive data (malicious versions 3.0.0, 4.0.0, 4.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in amanexzyra-baileys (npm)

MAL-2026-11081

Immediate action

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

npm uninstall amanexzyra-baileys

What this malware does

Package name amanexzyra-baileys resembles the popular WhatsApp Web API library @whiskeysockets/baileys family, which has been a frequent target of forks and lookalike publications. No exfiltration, install-time fetch-and-execute, silent-relay, credential harvesting, or backdoor was observed in the package contents at version 4.0.2. Name similarity alone is a subjective signal and prior Baileys forks have included covert behavior using the installer's WhatsApp session identity (e.g., auto-subscribing the consumer to attacker-controlled channels); a human reviewer should confirm whether this fork introduces any undocumented side-effects against the installer's authenticated session before recommending its use.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

3 flagged

3.0.04.0.04.0.2

Indicators of compromise (SHA-256)

91b75d849a9528c5b5c36142e8bed1b9b29063b91116e75ece79eff0f2c5a6cd

95c2dc37b7d123a5de5b204c909ddc35474421dc3e0e7a4f256691a54d825c20

bb0833eae489c03a492656c940146c549be8b4ee4d101818fb587bae0787b0b2

61494dcfdd3181d71da0f9fc80188037fb360eaa36eb392eb17d6fd77137f866

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 amanexzyra-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 amanexzyra-baileys across your stack and pipelines.
If you installed it — respond
amanexzyra-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 amanexzyra-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 amanexzyra-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. amanexzyra-baileys on npm has been identified as a malicious package (versions 3.0.0, 4.0.0, 4.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-mwwh-7r57-h6v9IN-MAL-2026-013002IN-MAL-2026-013024IN-MAL-2026-013026

References

Credits

Amazon Inspector · finder

Detect & block this

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