MAL-2026-20292: Malicious code in @kingorwot/my-baileys (npm)

Published Nov 20, 2026
·
Updated

--- -= Per source details. Do not edit below this line.=-

Source: amazon-inspector (e1139544c4c6b9006f15627d80ecbecd930289cdd1532307bc9777e8f32490e3) 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.

Affected Software

1 affected component
npm/@kingorwot/my-baileys=2.0.0

Event History

Nov 20, 2026
Advisory Published
via OSV·04:55 AM
Data Sourced
via OSV·04:55 AM
DescriptionAffected Software

Frequently Asked Questions

1

Which deployments are exposed to the automatic WhatsApp channel follows?

Deployments that load the ESM entry point, lib/index.js, and create a socket are exposed. The CJS main, lib/index.cjs, does not contain the auto-follow behavior.

2

What conditions are required for the channel-follow behavior to run?

A socket must be created through the ESM entry point. The task is scheduled 120 seconds later and uses the authenticated WhatsApp session to follow channel IDs obtained from a remotely hosted, mutable JSON file.

3

Does installation itself carry risk?

Yes. The package declares a production dependency from a third-party Git repository without a commit SHA or tag pin, so npm install resolves whatever is at that repository's HEAD at installation time, including lifecycle scripts.

4

What can be done if the package cannot be removed immediately?

Avoid loading the ESM entry point and avoid creating sockets through it, since the described auto-follow path is in lib/index.js rather than lib/index.cjs. Installation risk remains because the unpinned Git dependency can change at any time.

5

How can I determine whether the affected behavior may have occurred?

Check whether your application imports or resolves lib/index.js and creates an authenticated socket. Review the affected WhatsApp account's followed newsletters, since errors from the follow mutations are swallowed.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203