MULTIZAP CRM

AI Security Review

Evidence context: threat category none; evidence quality moderate.

MULTIZAP CRM adds CRM features to WhatsApp Web: chat organization, labels and contact handling, per its own description. Version 7.4.3.87 produced 23 findings, all medium severity, and each one traces to ordinary web plumbing rather than to hostile behavior.

Twenty-two of the findings are network detections. They are library signatures, not destinations. NET-JQUERY_AJAX fires in content/assets/js/v_7_4_3_87_0a650f0a-57a6-4989-860e-3a9d8748d28923.js, NET-SOCKET_IO fires in ...28912.js and ...289149.js, and NET-FETCH fires in ...289137.js, ...289179.js and background.js:137. Socket.io and jQuery's AJAX layer are how a chat tool maintains a live connection to a backend, and fetch is how background.js reaches whatever API it uses. A CRM layered over WhatsApp Web needs exactly those three things. No finding names a redirect template, a custom search domain, or a hardcoded host that isn't part of the extension's own service.

The two remaining hits are classed as obfuscation. OBFUSCATION-LARGE_BASE64 points at funnil/assets/js/9cf42769-2ad5-4714-8614-9a2b4c455349.CgnacD38.js, a vendor asset carrying a large base64 block. Blocks that size in a shipped asset are normally embedded images, icon sets or font data. OBFUSCATION-FUNCTION_INDIRECT fires on content/assets/js/v_7_4_3_87_0a650f0a-57a6-4989-860e-3a9d8748d289260.js, a minified bundle, where indirect calls are a byproduct of renaming and reordering functions. Neither is a malware signature, and the scan matched none of those. It also matched no known-bad domains, no cookie or token access, and no dependency or tool-poisoning indicators. The version string 7.4.3.87 indicates a product that has been through many release cycles, which fits a commercial tool rather than a throwaway payload.

A skeptic has a reasonable case. An extension that reads every WhatsApp conversation, holds an open socket to a remote server, ships an unexplained base64 asset, and comes from a publisher identified only as [email protected] with 24 users is the same shape as a session stealer. Third-party WhatsApp automation has a poor track record, and reading chat data is the first step in exfiltrating it. What separates this scan from a genuine hijack report is that nothing here targets a session. There is no cookie read, no request to a WhatsApp auth endpoint, no credential field scrape, and no unknown host captured in the findings. The same evidence would look very different if a single IoC pointed at a non-Google, non-CDN domain.

The gap worth naming: the scan recorded no endpoint list and no permission strings, so the destinations of the socket.io and fetch calls are unverified rather than proven clean. The base64 asset is likewise unopened. A runtime capture of the socket.io handshake and one decode of that blob would settle both questions. Everything the static scan did see is explained by the libraries the extension bundles.

Key Reasons

• Zero malware signatures, zero IoCs, zero credential-access or tool-poisoning findings; the scan's 22 network hits are framework detections (NET-JQUERY_AJAX, NET-SOCKET_IO, NET-FETCH) inside bundled content scripts and background.js:137.
• Socket.io and fetch calls are the expected mechanism for a WhatsApp Web CRM that syncs chat labels and contacts with a backend.
• The only obfuscation hits are a large base64 block in the vendor asset funnil/assets/js/9cf42769-2ad5-4714-8614-9a2b4c455349.CgnacD38.js and an indirect call in the minified bundle ...289260.js, both consistent with normal build output.
• No hijack artifacts (search templates, redirect endpoints) and no credential or session targets appear in any finding.

False Positive Considerations

• Framework-level network rules (NET-JQUERY_AJAX, NET-SOCKET_IO, NET-FETCH) fire on any bundled jQuery, socket.io or fetch usage in content scripts
• Minified vendor bundles named v_7_4_3_87_.js each contribute an identical detection, multiplying one library into many findings
• OBFUSCATION-LARGE_BASE64 matches an embedded asset blob in a vendor file rather than packed or encrypted code
• OBFUSCATION-FUNCTION_INDIRECT matches normal minifier output in a bundled file

Reviewed 2026-10-16; recommended action: monitor; model confidence 74%.