CLINICHAT

AI Security Review

Evidence context: threat category none; evidence quality moderate.

CLINICHAT bills itself as a CRM for WhatsApp Web, and the code behaves like one. Its content scripts carry jQuery AJAX and Socket.IO calls (content/assets/js/v_7_4_3_87_0a650f0a-57a6-4989-860e-3a9d8748d28924.js at line 181, v_7_4_3_87_0a650f0a-57a6-4989-860e-3a9d8748d28912.js at line 15), and background.js opens a fetch at line 137. A tool that organizes chats into pipelines has to read the thread and sync it with a server, so those network findings describe the product's stated job.

The manifest ships no Chrome permissions and no host permissions. That restraint matters: nothing here asks for cookies, tabs, history, downloads or a search-engine override, and there is no mechanism in the permission set to swap the new tab page or redirect searches. Zero malware signatures matched anything, and no finding names a login page, wallet or bank.

Most of the flagged volume comes from noise. The endpoint list reads like an extractor that mistook JavaScript property chains and CSS tokens for hostnames: border.radius.circle, btn.glass, color.border.accent.orange, calls.function.arguments.delta and ae.jobs cannot resolve as domains. The entries that do resolve belong to bundled dependencies and the vendor. app.wascript.com carries the CRM backend, api.statsigcdn.com serves feature flags, and the api.atlassian.com and api.stg.atlassian.com entries arrive with a bundled SDK. The 754 code-smell hits and 414 low-severity indicators follow the same pattern: minified, bundled JavaScript trips broad rules on fetch, exec and environment access without doing anything unusual.

Two obfuscation findings deserve a direct answer. OBFUSCATION-LARGE_BASE64 points at funnil/assets/js/9cf42769-2ad5-4714-8614-9a2b4c455349.CgnacD38.js, and OBFUSCATION-FUNCTION_INDIRECT points at content/assets/js/v_7_4_3_87_0a650f0a-57a6-4989-860e-3a9d8748d289260.js. Both sit inside hashed build output, where webpack and esbuild inline images, fonts and config as base64 and route exports through indirection helpers. Neither file carries a malware signature alongside it, which is the combination that points at deliberate hiding.

A skeptic has two fair objections. A CRM for WhatsApp reads every message in every thread, and anything it reads can leave the machine; the destination for that data is the vendor's backend at app.wascript.com. The publisher shows only the address [email protected] and a user count of 8, so there is no track record to weigh. Both objections concern what the code could do, not what the findings show it doing. Nothing here reveals a second destination, a credential target or a hijack, and the base64 block is exactly where such a thing would hide if it existed.

Decoding funnil/assets/js/9cf42769-2ad5-4714-8614-9a2b4c455349.CgnacD38.js and watching live socket traffic during a test session would settle the one open question.

Key Reasons

• Zero malware signatures across the whole scan; volume comes from 754 code-smell hits and 414 low-severity indicators on bundled JavaScript.
• Manifest declares no Chrome permissions and no host permissions, which rules out cookie, history, tab and search-engine abuse.
• Endpoint list contains artifacts that cannot resolve as domains, such as border.radius.circle, btn.glass and color.border.accent.orange.
• Network findings (NET-FETCH at background.js:137, NET-SOCKET_IO and NET-JQUERY_AJAX in content scripts) match the stated CRM function of syncing WhatsApp chats.
• Both obfuscation findings sit in hashed build artifacts (funnil/assets/js/9cf42769-2ad5-4714-8614-9a2b4c455349.CgnacD38.js), consistent with webpack output rather than hand-written obfuscation.

False Positive Considerations

• Broad code-smell rules firing on minified bundled JavaScript (fetch, exec, environment access)
• IoC extractor reading CSS tokens and property chains such as border.radius.circle and btn.glass as hostnames
• Hashed build artifacts (v_7_4_3_87_.js, .CgnacD38.js) counted as obfuscation
• Third-party and dependency domains (api.statsigcdn.com, api.atlassian.com) listed as extension endpoints

Reviewed 2026-10-13; recommended action: suppress false positive; model confidence 70%.