lordceaser-baileys@3.3.9
CEASER v3.3.9 MEGA FINAL - CLONED not packed - WHISKY + PLOGME + PLAGUE - FORCED JS BRIDGE INSIDE BELLY - FIXED md5 + LTHashAntiTampering + proto + hkdf + ALL 15 DEPS + REST - WILL LINK ONCE AND FOR ALL
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe postinstall hook and unusual pairing-code wrapper merit inspection, but source shows conditional local fallback setup and a caller-invoked pairing operation, with no confirmed attack behavior. The inspected dependency sources provide database and cache functionality.
Decision evidence
public snapshot- The install hook invokes the package entrypoint, whose fallback writes occur only when a dependency directory is absent; the entrypoint then attempts to load the package library.
- The inspected keyed database dependency provides in-memory storage and has no install lifecycle hook.
- The inspected cache dependencies expose cache implementations through their declared entrypoints.
- The package runs its entrypoint during postinstall and can create fallback dependency files when their directories are missing.
- The entrypoint changes the pairing-code function when callers invoke it, using a fixed default code; the inspected code does not establish an automatic pairing or an unrelated recipient.
Source & flagged code
7 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe install hook invokes the package entrypoint, whose fallback writes occur only when a dependency directory is absent; the entrypoint then attempts to load the package library.
package.jsonView on unpkg · L7Findings
Affected versions and remediation
This report applies to lordceaser-baileys@3.3.9.
See all versions of lordceaser-baileys for other recorded verdicts.
- Review the evidence and your use of lordceaser-baileys@3.3.9 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.