The pre-extracted bundle at is incomplete — it omits and, which hold essentially all logic, so I reviewed the stored package /[domain withheld] (manifest version 2.17.0, and 3149392+1417028+216052+48 = 4782520 bytes of JS, exactly the model's total_js_size_bytes). The code is a white-label WhatsApp Web CRM built on v4.6.0, React, SheetJS and Firebase FCM: exposes 113 CRM-only message actions (chat assignment, kanban, labels, quick messages, campaigns, transcription, backup) against its own backend [domain withheld], chrome.cookies is used solely to read/write one SSO cookie named auth-wl-7dccfe2014567a21f20f7cd58b156144 on its own [domain withheld], are filtered to *://[domain withheld] only, setUninstallURL points at [domain withheld], and every upload path (cloudBackup of the extension's own config JSON, transcribeAudio of a single voice note, chat-assignment templates) is user-initiated — there is no alarm, cron or auto-harvest of contacts or message history. Contradicting signals: the permhash cluster (91% flagged) and our Critical risk-engine score rest on the permission set, and the declarativeNetRequest rule in does replace WhatsApp Web's CSP with 'default-src * unsafe-inline unsafe-eval' — but that rule exists to let inject the locally bundled via chrome.runtime.getURL into the declared host, and I traced every sink in to React internals and Notiflix's static templates, with no server-supplied HTML path from, or whitelabelSettings, and no remote script source anywhere (jsdelivr hits are emoji-datasource PNG paths). Residual hygiene issues keep this at likely_benign rather than false_positive: the CSP strip, the postMessage bridge gate kn(e) (e) only checks type === 'plugin' so any script on [domain withheld] could invoke the CRM actions, 'none declared' CWS data collection understates a product that uploads CRM state and audio to its own server, and wa-js's upstream defaults send GA events to [domain withheld] (tracker G-MTQ4KY110F) and link-preview URLs to [domain withheld].