registry / lordceaser-baileys / 2.0.39
lordceaser-baileys@2.0.39
CEASER v2.0.39 FINAL 406 files CJS - Pterodactyl fixed - Baileys v6.7.8 CommonJS no ESM error - Same as 2.0.22-2.0.26 perfect
AI Security Review
scanned 17d ago · by lpm-firewall-aiSource inspection found no malicious credential transfer or install-time behavior. The flagged AI request is invoked by an explicit command and sends the supplied prompt to its intended service.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
The user invokes the bot's !ai command or one of its download commands.
Impact
No confirmed malicious impact was identified.
Mechanism
The bot sends the provided AI prompt to OpenAI or the supplied media URL to its downloader service; inspected code does not send saved WhatsApp credentials to those endpoints.
AI rationale
Source inspection found no malicious credential transfer or install-time behavior. The flagged AI request is invoked by an explicit command and sends the supplied prompt to its intended service.
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest names index.js as its entrypoint and defines no install lifecycle script.
- The flagged runtime location formats a WhatsApp pairing code for display.
- The AI request sends the supplied prompt to OpenAI using AI_API_KEY, and the caller activates it only for an explicit !ai command.
- WAProto/index.js imports protobufjs and contains ordinary protobuf decoding logic.
Evidence against
- The inspected AI request contains no saved WhatsApp session credentials; it sends the caller-provided prompt to the intended AI service.
- The downloader requests are reached through explicit user commands and forward the supplied media URL to the downloader service.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
6 flaggedindex.jsView file
8const { Boom } = require("@hapi/boom");
L9: const axios = require("axios");
L10: const path = require("path");
...
L21: function getOwnerNumber() {
L22: return (process.env.OWNER_NUMBER || "").replace(/\D/g, "").replace(/^0+/, "");
L23: }
L24:
L25: const MENU_IMAGE = path.join(__dirname, "assets", "menu.jpg");
L26:
L27: // ---------- Access control ----------
L28: let privateMode = "public";
L29: const whitelist = new Set();
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
index.jsView on unpkg · L88Trigger-reachable chain: manifest.main -> index.js
L8: const { Boom } = require("@hapi/boom");
L9: const axios = require("axios");
L10: const path = require("path");
...
L21: function getOwnerNumber() {
L22: return (process.env.OWNER_NUMBER || "").replace(/\D/g, "").replace(/^0+/, "");
L23: }
L24:
L25: const MENU_IMAGE = path.join(__dirname, "assets", "menu.jpg");
L26:
L27: // ---------- Access control ----------
L28: let privateMode = "public";
L29: const whitelist = new Set();
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
index.jsView on unpkg · L8•matchType = previous_version_dangerous_delta
matchedPackage = lordceaser-baileys@2.0.50
matchedIdentity = npm:bG9yZGNlYXNlci1iYWlsZXlz:2.0.50
similarity = 0.868
summary = stored previous version shares package body but lacks this dangerous source file
Findings
3 Critical1 High5 Medium3 Low
CriticalCredential Exfiltrationindex.js
CriticalTrigger Reachable Dangerous Capabilityindex.js
CriticalPrevious Version Dangerous Deltaindex.js
HighTrigger Reachable Credential Exfiltrationindex.js
MediumNetwork
MediumEnvironment Vars
MediumShips Build HelperWAProto/GenerateStatics.sh
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to lordceaser-baileys@2.0.39.
See all versions of lordceaser-baileys for other recorded verdicts.
- Review the evidence and your use of lordceaser-baileys@2.0.39 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.