The signed file list confirms the complete bundle is 7 code files plus 3 icons, and all 4 JS files are unminified, commented, and contain zero network sinks: a grep for across popup, background, shared and premium returns exactly one hit,:231 opening the publisher's own [domain withheld] on a user click. The extension does exactly what its listing says::138-151 sets chrome.proxy to fixed_servers with a SOCKS5 host taken from the hard-coded SERVERS table in (all *.[domain withheld], matching the CWS privacy-policy domain), only in response to an explicit user CONNECT, with connectionEnabled defaulting to false (:116) and no PAC script or remote configuration anywhere. Contradicting the ML score: the malext-feed internal note self-describes its basis as 'not an independent code review', and chrome-stats cites permission-clipboard plus ' in the past month' for an extension that has neither the clipboard permission nor a recent creation date (214 days old), so that vendor's input is stale and self-inconsistent. Corroborating benign: publisher is malicious. Not raised to false_positive because a code review cannot audit the operator's SOCKS5 endpoints, and bypassList is empty so all regular-profile traffic traverses them unauthenticated; combined with an anonymous Gmail publisher and a [domain withheld] privacy policy, an unverifiable backdoor at the server side remains possible. Hygiene note (not a finding)::1-22 validates PRO tokens entirely client-side with a forgeable 32-bit djb2-style hash and a string-split 'secretKey', which is trivially bypassable licensing, not anti-analysis.