SutoflyCRM, WhatsApp Web organizado, automatizado e vendendo

AI Security Review

Evidence context: threat category none; evidence quality moderate.

SutoflyCRM is a Chrome extension that adds a sales dashboard, canned replies and automations on top of WhatsApp Web. The manifest as scanned declares no permissions and no host permissions, so nothing in the scan runs with privileged browser API access. That matters when reading the rest of the evidence, because the volume of findings comes from bundled third-party JavaScript rather than from the extension's own logic.

Twenty-two medium network findings are pattern matches on library calls, not on destinations. NET-SOCKET_IO fires on content/assets/js/v_7_4_3_87_0a650f0a-57a6-4989-860e-3a9d8748d28912.js, ...149.js and ...175.js, which is the socket.io client a chat tool uses to hold a live connection open. NET-JQUERY_AJAX fires twice on content/assets/js/v_7_4_3_87_0a650f0a-57a6-4989-860e-3a9d8748d28923.js, the jQuery ajax wrapper. The remaining NET-FETCH hits, including background.js:137, are plain fetch() calls with no destination attached. Not one of these findings names a malicious or monetization host.

The extracted endpoint list is mostly garbage. Entries like border.radius.circle, btn.glass and color.border.accent.orange are design-token strings lifted from a theme object or stylesheet. calls.function.arguments.delta is a field name from a streaming API response. The hosts that are real are ordinary for a commercial product: api.statsigcdn.com for feature flags, the Atlassian API hosts, and app.wascript.com, which is the vendor's WhatsApp automation backend and lines up with the product description.

Two medium obfuscation findings need a direct answer. OBFUSCATION-LARGE_BASE64 points at funnil/assets/js/9cf42769-2ad5-4714-8614-9a2b4c455349.CgnacD38.js, a file with a content hash in its name. Embedded base64 in a hashed build artifact is how bundlers inline images, fonts and worker scripts. OBFUSCATION-FUNCTION_INDIRECT in content/assets/js/v_7_4_3_87_0a650f0a-57a6-4989-860e-3a9d8748d289260.js is the call indirection minifiers produce. Neither sits beside a malware signature, and there are none: zero malware-signature hits, zero malware hits, zero secrets, zero tool-poisoning.

A skeptic has a reasonable case. The developer is listed only as [email protected] with no company name, the base64 blob sits in a directory called funnil under a random filename, and a CRM for WhatsApp reads conversation content and sends it to app.wascript.com. That last point is a real privacy trade-off. To do its job, this extension has to see the messages. Anyone who does not want an automation vendor processing their WhatsApp conversations should not install it. What the evidence does not show is code reaching a host unrelated to the product, a credential or cookie stealer, or a browser hijack. The 754 code-smell hits and 419 indicators are the usual side effect of scanning minified bundles; the extractor turned CSS values and property names into fake domains. With no payload, no suspicious destination and no hidden capability, the findings describe a chat automation tool doing what its listing says. A runtime capture of the socket.io connection would confirm which host the traffic actually reaches, and that is the only open question.

Key Reasons

• Zero malware-signature, malware, secret and tool-poisoning findings across 1198 total; the entire finding set is code-smell, IoC extractor output and library pattern matches.
• All 22 network findings are library call patterns (NET-SOCKET_IO, NET-JQUERY_AJAX, NET-FETCH) in bundled files such as content/assets/js/v_7_4_3_87_0a650f0a-57a6-4989-860e-3a9d8748d28912.js, with no malicious or monetization destination named.
• Extracted endpoints are dominated by design-token and property-name artifacts (border.radius.circle, btn.glass, calls.function.arguments.delta) that the IoC extractor misread as domains.
• The two obfuscation findings (OBFUSCATION-LARGE_BASE64 in a content-hashed build artifact, OBFUSCATION-FUNCTION_INDIRECT in a minified bundle file) are consistent with standard bundler output.
• Manifest declares no permissions and no host permissions, so the scanned code holds no privileged browser API access.

False Positive Considerations

• IoC extractor misreading CSS design tokens and minified property chains (border.radius.circle, btn.glass, color.border.accent.orange) as network domains
• Code-smell YARA rules firing 754 times on minified and bundled JavaScript
• Network rules (NET-FETCH, NET-JQUERY_AJAX, NET-SOCKET_IO) matching library call patterns with no destination context
• Base64 and indirect-call obfuscation heuristics firing on content-hashed webpack build artifacts

Reviewed 2026-10-13; recommended action: no action; model confidence 75%.