Reviewed the complete 1.0.37 artifact (323 files recovered from the CRX zip after the supplied bundle turned out to be missing, every img/ asset and the webfonts; JS sizes in the full set sum to exactly the 266197 bytes the model saw): it is a plain HTTPS-proxy VPN client that points chrome.proxy at a [domain withheld] node (:143), returns stored proxy credentials only when details.isProxy is true (:380), uses the 'privacy' permission solely for webRTCIPHandlingPolicy leak protection (:170), and sends nothing anywhere except the user's own popup-entered to [domain withheld] (:1123, 1138, 1306), matching the disclosed PII + authentication categories. The ML score, the risk-engine CRITICAL and the chrome-stats all derive from the <all_urls> manifest that this product category requires, so they corroborate nothing beyond the manifest, while the code contradicts the flag (no obfuscation, no remote code loading, no third-party endpoint, no access) and the listing's [domain withheld] WhatsApp-spamware note matches nothing in this codebase. The published MV3 manifest vs bundled MV2 1.0.37 difference is version drift to a newer build rather than delayed-malicious divergence inside 1.0.37, so this verdict is scoped to 1.0.37 and does not clear the current CWS version, which matters because the eSentire IoC tag on this listing concerns malicious updates pushed through hijacked publisher accounts.