lordceaser-baileys@2.0.45
CEASER - Premium WhatsApp engine v2.0.35 PERFECT RESTORED 180 files - Same as 2.0.22-2.0.26 perfect - All button types + ping media + group responding + Pterodactyl fixed
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe source establishes a reachable server-side request forgery risk and surprising import-time bot behavior, but it does not establish concrete malicious intent or install-time abuse. This warrants a warning rather than a publication block.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Importing index.js, then pairing a WhatsApp account and receiving a download command.
Impact
An attacker who can interact with the paired bot may be able to induce network requests to attacker-chosen destinations returned by the downloader service.
Mechanism
Import-time bot startup with unvalidated remote download URLs.
AI rationale
The source establishes a reachable server-side request forgery risk and surprising import-time bot behavior, but it does not establish concrete malicious intent or install-time abuse. This warrants a warning rather than a publication block.
Evidence
index.jsauth_info
Network endpoints2
api.openai.comapi.ryzendesu.vip
Decision evidence
public snapshotAI called this Suspicious at 83.0% confidence as Critical Vulnerability with low false-positive risk.
Evidence for warning
- The main entrypoint starts a WhatsApp bot immediately when imported.
- The bot creates local authentication state and requests a WhatsApp pairing code.
- Public message commands obtain a URL from a third-party downloader service, then fetch the returned URL without validation; this creates a server-side request forgery risk.
- The bot forwards supplied AI prompts to the OpenAI API using an environment API key.
Evidence against
- package.json contains no lifecycle scripts, so this behavior does not run during npm installation.
- The inspected code contains no secret harvesting, shell execution, persistence, or destructive file operation.
- The API key is sent only as authorization to the OpenAI endpoint for the explicit AI command.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStrings
Source & flagged code
11 flaggedlordceaser-baileys/src/WABinary/constants.tsView file
601patternName = google_api_key
severity = high
line = 601
High
High Secret
Package contains a high-severity secret pattern.
lordceaser-baileys/src/WABinary/constants.tsView on unpkg · L601601patternName = google_api_key
severity = high
line = 601
High
Secret Pattern
Google API key in lordceaser-baileys/src/WABinary/constants.ts
lordceaser-baileys/src/WABinary/constants.tsView on unpkg · L601index.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();
Findings
3 Critical5 High6 Medium3 Low
CriticalCredential Exfiltrationindex.js
CriticalTrigger Reachable Dangerous Capabilityindex.js
CriticalPrevious Version Dangerous Deltaindex.js
HighHigh Secretlordceaser-baileys/src/WABinary/constants.ts
HighTrigger Reachable Credential Exfiltrationindex.js
HighShips High Entropy Blob.npm/_cacache/content-v2/sha512/57/cf/309075d2cb07d593b16e2a3b23c2363cadfd229f427d85c045f3acc02b2b7da77cd140c4f7d57ae6a2b5919735ed66edd399b092a945f5b980b8a63fcbd9
HighPayload In Excluded Dir.npm/_cacache/content-v2/sha512/57/cf/309075d2cb07d593b16e2a3b23c2363cadfd229f427d85c045f3acc02b2b7da77cd140c4f7d57ae6a2b5919735ed66edd399b092a945f5b980b8a63fcbd9
HighSecret Patternlordceaser-baileys/src/WABinary/constants.ts
MediumNetwork
Affected versions and remediation
This report applies to lordceaser-baileys@2.0.45.
See all versions of lordceaser-baileys for other recorded verdicts.
- Review the evidence and your use of lordceaser-baileys@2.0.45 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.