The entire extension is 5 hand-written, unminified files that implement exactly one behaviour: a user-toggled SOCKS5 proxy to the publisher's own host [domain withheld] (:14-19), set only on an explicit popup click (:124-142), cleared on disable (:64-73), and re-applied at startup only if the user left it on (:149-156); there is no fetch, XMLHttpRequest, WebSocket, eval, Function(), atob, sendBeacon, executeScript, content script, host permission, or chrome. handler anywhere in the bundle, and the only URL in any file is the publisher's own [domain withheld] (:71), the same apex domain as the proxy host. Contradicting the ML score: chrome-stats cites a clipboard permission that appears in neither the bundled nor the published manifest (both are exactly ["proxy","storage"], so they match), the malext-feed note explicitly describes itself as 'not an independent code review… No affected version supplied', the permhash cluster is simply the minimal permission set every proxy VPN needs, and the publisher is malicious. Residual risk that source cannot rule out and that keeps this at likely_benign rather than false_positive: SOCKS5 means Chrome resolves DNS through the proxy, so the [domain withheld] operator sees every hostname visited over an unencrypted browser-to-proxy hop, while CWS data collection is declared as 'none' — but that is server-side, inherent to a proxy's core function in the Privacy & Security category, and not a code-level finding.