@lordmega/baileys
Enhanced Baileys v7 with fixes for newsletter media uploads, plus support for interactive messages, albums, and additional message types.
This report shows the evidence for @lordmega/baileys@0.3.40. 1 of 11 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
This package appears in our research on the malicious Baileys forks, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe benign engine check does not explain the obfuscated runtime mutation. Concealed third-party branding injected into user messages is concrete, non-consensual payload manipulation.
Decision evidence
public snapshot- lib/Utils/messages.js is deliberately obfuscated and initializes hidden brand constants at import.
- The obfuscated module constructs newsletter metadata in mediaAnnotation.
- Media-message preparation conditionally assigns mediaAnnotation to outgoing media.
- The package identity differs from embedded defaults identifying itsliaaa/baileys.
- The preinstall hook only enforces Node.js 20+ and performs no network or file mutation.
- Reviewed network code is WhatsApp/media functionality; no credential harvesting or shell payload execution was found.
Source & flagged code
8 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage contains a high-severity secret pattern.
lib/WABinary/constants.jsView on unpkg · L600Source file is highly similar to a previously finalized malicious package; route for source-aware review.
Findings
Affected versions and remediation
This report applies to @lordmega/baileys@0.3.40.
The versions list below shows the verdict for each recorded version.
- Avoid installing @lordmega/baileys@0.3.40. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.