Cliente Flow

AI Security Review

Evidence context: threat category none; evidence quality moderate.

Cliente Flow is a Chrome store extension that presents itself as a CRM overlay for WhatsApp Web, letting users organize chats without leaving the tab. The scan produced 1,196 findings, and not one of them is rated critical or high. There are no malware signatures and no malware family matches at all. What is left is 755 code-smell entries, 416 extracted indicators, 22 network findings, and two obfuscation flags.

Look at what the network findings are. Every one is a library pattern inside a versioned bundle: NET-JQUERY_AJAX and NET-FETCH in content/assets/js/v_7_4_3_87_0a650f0a-57a6-4989-860e-3a9d8748d28923.js and ...28924.js, NET-SOCKET_IO at content/assets/js/...28912.js:15 and ...289149.js:64, plus one NET-FETCH in background.js:137. Socket.IO and jQuery Ajax are what a chat client uses to keep a WhatsApp conversation list in sync with the server. An overlay that never opened a live connection would not function. None of these findings name a destination host, so they describe technique, not a target.

The endpoint list is the clearest signal in the whole scan, and it points at the extraction pass. It includes "border.radius.circle", "btn.glass" and "color.border.accent.orange", which are CSS property and utility-class names. It includes "calls.function.arguments.delta", a JSON path from streamed API responses, and "above.sm" and "below.sm", Tailwind-style breakpoint labels. Alongside those sit api.atlassian.com and api.statsigcdn.com, documentation and feature-flag hosts that bundled libraries reference in comments and default configs. The one endpoint that reads like the product's own service is app.wascript.com, a name consistent with WhatsApp automation tooling.

The two obfuscation entries are equally thin. OBFUSCATION-LARGE_BASE64 fires on funnil/assets/js/9cf42769-2ad5-4714-8614-9a2b4c455349.CgnacD38.js, a content-hashed build artifact carrying an inlined base64 asset. OBFUSCATION-FUNCTION_INDIRECT fires at content/assets/js/...289260.js:1, line one of a minified file, which is where indirect-call helpers live in webpack and esbuild output. Neither is hand-written obfuscation.

A skeptic would point at two things. The manifest shows no host permissions, which is strange for something that has to read chat content, and a hashed file carrying a large base64 blob invites a closer look. Both are fair observations. The empty permission list is an absence of data more than a fact about the extension; manifest parsing is the thinnest part of this scan, and a manifest declaring alarming access would have generated a manifest finding. As for the base64 blob, every bundler inlines small images and fonts, and a real payload hidden there would have tripped the malware rules that came back empty. If a reanalysis with full manifest and permission parsing resolves those two gaps, that would settle it.

The verdict follows from what is missing. Hundreds of code-smell hits are the documented output of YARA rules that fire on any non-trivial JavaScript, and hundreds of indicators are the documented output of a string extractor running over minified bundles. The count is high. The nature is plumbing.

Key Reasons

• Zero malware signatures and zero malware family matches across 1,196 findings.
• All 22 network findings are library patterns (jQuery Ajax, Socket.IO, fetch) inside minified versioned bundles, and none names a destination host.
• Extracted indicators include CSS names like border.radius.circle and btn.glass and a JSON path like calls.function.arguments.delta, a documented extractor false-positive class.
• Both obfuscation flags are bundler artifacts: an inlined base64 asset in a content-hashed file and an indirect-call helper at line one of minified code.
• 755 code-smell entries are low-severity YARA noise that fires on ordinary JavaScript.

False Positive Considerations

• IoC extractor misreading CSS class names and streamed JSON paths as network domains
• Low-severity YARA code-smell rules firing on bundled and minified JavaScript
• Base64 asset inlining by the bundler classified as obfuscation
• Library network primitives (jQuery Ajax, Socket.IO, fetch) counted as suspicious network findings

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