@lekzsync/baileys@1.0.5
Malicious code in @lekzsync/baileys (npm)
Analysis
@lekzsync/baileys is a repackaged fork of Baileys (the WhatsApp Web library) published under a scope other than the upstream project's. It carries behaviour absent from upstream: - Silent channel enrolment: lib/Socket/newsletter.js hardcodes a base64-encoded WhatsApp channel JID ("MTIwMzYzNDExMDE4NTUxNzU0QG5ld3NsZXR0ZXI=" = 120363411018551754@newsletter) and, as soon as the socket is created, schedules a delayed executeWMexQuery({newsletter_id}, QueryIds.FOLLOW, "xwa2_newsletter_follow") call. Every account using the library is enrolled as a follower of that channel without any action, option or notification from the user; errors are swallowed. - Third-party phone-number egress: lib/Socket/socket.js defines and exports a checkBan() helper that sends phone numbers supplied by the caller to hxxps://kyuux-r[.]indevs[.]in/api/check-whatsapp?phone=<number> and returns the remote response merged with {creator: "t[.]me/luyatiem"}. - Forged/deceptive message metadata: lib/Socket/luxu.js (class "imup") tags outgoing album media with the channel JID 120363421563597486@newsletter ("D | 7eppeli-Exloration", senderName "7-Yuukey") and sets spoofed forwarding scores, "verification"/business-owner fields and an is_ai_message support payload. - Declares a dependency on cache-manager ^7.2.8 (resolving to the known-malicious 7.2.10). - preinstall runs node ./engine-requirements.js, which only checks the Node major version (>=20). Domains: kyuux-r.indevs.in, t[.]me/luyatiem, whatsapp[.]com/channel/0029Vb863rSLtOjDrDNHqq3o.
- analyzed by
- Leitwacht
- first seen
- Nov 11, 2026, 05:05 AM
- analyzed
- Nov 11, 2026, 05:08 AM
Related advisories
- @zlynzee/baileys@1.0.4
- @sakataa/baileys@4.0.1
- @sakataa/baileys@4.0.0
- template-pictogram@9.1.1
- @memtensor/memos-cloud-openclaw-plugin@0.1.22
- neun-by-neun@0.1.0
- @wanzforme/bails@1.0.0
- @monze1239/baileys@1.0.0
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.