santana-baileys
This report shows the evidence for santana-baileys@2.0.1. 5 of 6 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.
OpenSSF/OSV Malicious Advisory
imported 2mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-13456 confirms this npm version as malicious.
Independent LPM AI assessment
Manual ReviewIndependent AI assessment: manual_review. LPM AI review remains unresolved.
The manifest's install hooks are inert, but the declared runtime source is missing from the extracted package. A maliciousness decision cannot be grounded in source facts.
Independent scan evidence
public snapshot- package.json declares runtime entrypoint lib/index.js, but no lib source is present in the extracted package.
- package.json preinstall and prepare scripts are empty strings.
- The only available package file is package.json; it contains no executable lifecycle command.
Source & flagged code
2 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to santana-baileys@2.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing santana-baileys@2.0.1. 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.