BotPlugin is a WhatsApp Web automation client: injects only its own web-accessible resources (,) via chrome.runtime.getURL, and is a React panel that authenticates against the first-party [domain withheld] (POST, token in localStorage key tokenBotPlugin) and drives WPP.chat.* message sending from a [domain withheld] room — exactly the advertised 'automating conversations' in category Social Networking, with PII collection disclosed and the destination matching the publisher's own [domain withheld] / multiweb.plus domains. The provided directory was incomplete (its lists,.LICENSE.txt and assets/*, none present), so — the 881 KB core, and the only file where real abuse could hide — was reviewed from the stored signed archive [domain withheld], whose JS byte total (881347+521297+49642+4078+2577+542 = 1,459,483) exactly matches the model's total_js_size_bytes and whose 18 files match total_file_count, confirming it is the artifact that was scored. Contradicting the ML critical score and the 'publisher flagged malicious ' signal: there is no cookie access, no chrome., no eval, no importScripts, no remote script URL anywhere, and every server-push message is handled by a fixed switch () with no computed dispatch, so the socket channel cannot be used as a command backdoor; the internal malext-feed note itself states it is 'not an independent code review', and the code does not corroborate it. Hygiene only (not findings): the [domain withheld] host permission and [domain withheld] content-script match are dev leftovers, the window-event bridge (sendMessageToBackground / chromeStorage) is callable by any script on [domain withheld], the bundled app constant still reports version 1.1.84 against manifest 1.1.95, and the upstream WA-JS library carries its own [domain withheld] tracker and third-party link-preview servers () which are library defaults the publisher did not add.