@crysnovax/baileys
Production-ready Baileys fork ⚉ with AI groups, Meta AI prompting, safe compositing fallbacks, rich responses, interactive messages, albums, newsletters, and communities — without antiban wrappers.
This report shows the evidence for @crysnovax/baileys@2.7.19. 17 of 20 known versions are 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 package performs concealed, unconsented external account mutation on every authenticated connection and combines it with vendor fingerprinting and remote feature revocation. The lifecycle hook itself is limited, but the runtime behavior is concrete and malicious.
Decision evidence
public snapshot- Every authenticated socket connection automatically follows package-selected newsletter channels.
- The channel-following policy is deliberately obfuscated and includes a hard-coded newsletter identifier.
- Runtime code fingerprints the host and sends it with package identity to a vendor endpoint.
- A vendor response can remotely revoke the installation and disable features.
- The preinstall hook only checks Node version and reads this package's manifest.
- The attestation request shown in source sends package name, version, and a truncated hash; no secret-file harvesting is present in the inspected code.
- The ffmpeg child process is a parameterized media-thumbnail helper.
Source & flagged code
14 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.
lib/WABinary/constants.jsView on unpkgGoogle API key in lib/WABinary/constants.js
lib/WABinary/constants.jsView on unpkg · L600Package source references child process execution.
lib/Utils/messages-media.jsView on unpkg · L1Source combines command execution, command-output handling, and outbound requests; review data flow before blocking.
lib/Utils/messages-media.jsView on unpkg · L1Source file is highly similar to a previously finalized malicious package; route for source-aware review.
lib/Utils/messages-media.jsView on unpkgPackage source references weak cryptographic algorithms.
lib/Utils/validate-connection.jsView on unpkg · L111Source contains an obfuscated payload loader that reconstructs and executes hidden code.
lib/Utils/channel-policy.jsView on unpkg · L1This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
lib/Utils/integrity.jsView on unpkgSource decodes a Base64-obscured HTTP endpoint at runtime.
lib/Utils/integrity.jsView on unpkg · L41Source file is highly similar to a previously finalized malicious package; route for source-aware review.
lib/Utils/integrity.jsView on unpkgPackage contains source files above the normal full-analysis size ceiling.
WAProto/index.jsView on unpkgA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
lib/Utils/business.jsView on unpkgFindings
Affected versions and remediation
This report applies to @crysnovax/baileys@2.7.19.
The versions list below shows the verdict for each recorded version.
- Avoid installing @crysnovax/baileys@2.7.19. 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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.