NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@kingorwot/my-baileysnpm

Advisory published Updated

@kingorwot/my-baileys is a confirmed malicious npm package (MAL-2026-20292) that executes malicious code on install (malicious version 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @kingorwot/my-baileys (npm)

MAL-2026-20292
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @kingorwot/my-baileys

What this malware does

This Baileys fork declares a production dependency whatsapp-rust-bridge-baron sourced from git+https://github.com/7ucg/whatsapp-rust-bridge.git with no commit SHA or tag pin. npm install resolves this to whatever HEAD of that third-party repo contains at install time, including any lifecycle scripts inside it, and the repo owner (7ucg) is not the publisher of this package. In addition, the ESM entry (lib/index.js) schedules a 120-second-delayed task on socket creation that fetches a channel-ID list from https://raw.githubusercontent.com/DGXeon13/strings/refs/heads/main/strings.json and issues WhatsApp newsletter FOLLOW mutations for each ID using the installer's authenticated session, with errors swallowed and no README disclosure. The JSON file is under the author's personal GitHub account and mutable at any time, allowing the author to retarget the installer's account to follow arbitrary channels. The CJS main (lib/index.cjs) does not contain the auto-follow path.

Malicious versions

1 flagged
2.0.0

Indicators of compromise (SHA-256)

e1139544c4c6b9006f15627d80ecbecd930289cdd1532307bc9777e8f32490e3

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @kingorwot/my-baileys (version 2.0.0).

  2. If you installed it — respond

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

  3. Did it already run?

    If @kingorwot/my-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

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

Campaign

IN-MAL-2026-022950

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

@kingorwot/my-baileys (npm) malicious package — MAL-2026-20292 | O3 Security