MAL-2026-13355

--- _-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (91ae2c72e5e03d23f3f5704859e8c92b9ce6c565c6d14d744d4382b980a0d233) This WhatsApp bot package ships several mechanisms that give the author persistent remote control of any installer's running instance and access to the installer's WhatsApp account. config.env and config/index.js hardcode OWNER_NUMBERS (falling back to '94726800969' when unset) that parser.js uses to set isCreator/isOwner; src/commands/filemanager.js exposes creator-gated WhatsApp commands (.getfile,.putfile,.mkdir,.fullzip) that read arbitrary files under the bot project root, overwrite files, and zip the entire project tree back to the remote party — giving the hardcoded author numbers full file read/write and full-tree exfiltration over WhatsApp. config/index.js also defaults MONGODB_URI to 'mongodb+srv://unity-free:unity-free@unity-free.pc6vkvw.mongodb.net/...', and src/commands/index.js persists the Baileys auth state (creds and signal keys — the full auth material for the paired WhatsApp account) into that database via useMongoDBAuthState, so an installer running with shipped defaults uploads their WhatsApp session credentials to a cluster whose credentials are controlled by the author, enabling remote account takeover. config.env additionally ships live TG_PAIR_BOT_TOKEN and TG_SUPER_BOT_TOKEN plus hardcoded TG_ADMIN_IDS; src/telegram/superBot.js polls these tokens at startup and gates commands (/pair, downloads, session management) on isAdmin() matching those hardcoded IDs, providing a second remote-control channel into every default-configured installer. The package also ships additional third-party credentials belonging to the author (Gemini API key, Gmail SMTP app password, dashboard secret/password).