EnZap

AI Security Review

Evidence context: threat category none; evidence quality moderate.

EnZap bills itself as a CRM for WhatsApp Web, and the file layout backs that up. The manifest declares no permissions and no host permissions, so the extension's reach comes from content scripts injected into the WhatsApp page. Those scripts sit under content/assets/js/ as versioned bundles named v_7_4_3_87_0a650f0a-57a6-4989-860e-3a9d8748d289*. A version string plus a build hash in every filename is what a bundler emits, and it explains why one directory produces so many separate findings.

The network findings describe what those bundles do. NET-SOCKET_IO fires in v_7_4_3_87_...28912.js and v_7_4_3_87_...289149.js, the realtime channel a shared inbox needs. NET-JQUERY_AJAX fires in v_7_4_3_87_...28923.js, a legacy XHR path. NET-FETCH fires in background.js:137 and across a dozen content bundles, the ordinary way an extension talks to its backend. None of these findings name a destination. They record that HTTP machinery exists, which a chat CRM cannot do without.

Two obfuscation findings deserve their own paragraph. OBFUSCATION-LARGE_BASE64 fires on funnil/assets/js/9cf42769-2ad5-4714-8614-9a2b4c455349.CgnacD38.js, and OBFUSCATION-FUNCTION_INDIRECT fires on content/assets/js/v_7_4_3_87_0a650f0a-57a6-4989-860e-3a9d8748d289260.js. A large base64 block inside a bundled asset is usually an inlined image, font or locale table. Indirect function calls are what every minifier produces when it rewrites direct references. Location is the part that matters: obfuscation is worth acting on when it shares a file with a malware match, and this scan recorded zero malware signatures. The CgnacD38.js blob would need a nearby decoder and an eval-style sink to be worth a second look. The file shows neither.

The remaining 432 IoCs and 754 code-smell hits are volume, and the endpoint list shows why. Alongside genuine hosts like app.wascript.com, api.statsigcdn.com and api.dev.atlassian.com, the extractor produced border.radius.circle, calls.function.arguments.delta, btn.glass, above.sm, below.sm and be.audio. Those are CSS fragments, object property chains and short strings lifted out of minified JavaScript. No registrar sells calls.function.arguments.delta. An extractor that turns property access into domains will also turn every fetch wrapper into a network finding, and this extension contains a lot of fetch wrappers.

A skeptic's case is straightforward: a tool that reads your WhatsApp conversations holds exactly the access a data thief wants, and an unreadable base64 blob is the obvious hiding place. That case is reasonable, and it is why this is not a clean bill of health. It is still not evidence. Nothing here targets a login domain, harvests cookies, or contacts a host outside the vendor's own stack and standard analytics. Closing the question would take one concrete step: decode the base64 region in funnil/assets/js/9cf42769-2ad5-4714-8614-9a2b4c455349.CgnacD38.js and read what comes out. Until then, the findings describe a chat tool doing chat-tool work, and the alarming totals come from a scanner counting minified libraries.

Key Reasons

• Zero malware signatures and zero malware findings across 1,211 total findings; the entire medium-severity tier is network plumbing (NET-FETCH, NET-SOCKET_IO, NET-JQUERY_AJAX) in versioned build output under content/assets/js/.
• OBFUSCATION-LARGE_BASE64 on funnil/assets/js/9cf42769-2ad5-4714-8614-9a2b4c455349.CgnacD38.js and OBFUSCATION-FUNCTION_INDIRECT on content/assets/js/v_7_4_3_87_...289260.js sit in minified bundles with no co-located malware match, decoder or eval sink.
• The endpoint list mixes real hosts (app.wascript.com, api.statsigcdn.com, api.dev.atlassian.com) with extractor artifacts that are not registrable domains: border.radius.circle, calls.function.arguments.delta, btn.glass, above.sm, below.sm, be.audio.
• 754 code-smell findings are generator noise on bundled JavaScript, and 432 IoCs follow from the same minified content.
• The extension's declared purpose (a WhatsApp Web CRM) accounts for reading the WhatsApp page and holding a realtime socket; the manifest requests no permissions or host permissions.

False Positive Considerations

• Minified/bundled JavaScript under content/assets/js/ producing multiplicative network and code-smell matches
• IoC extractor emitting property chains and CSS fragments (calls.function.arguments.delta, border.radius.circle, btn.glass) as domains
• Two obfuscation rules firing on build artifacts with no accompanying malware signature
• Code-smell rule volume (754) on a large dependency-heavy bundle

Reviewed 2026-10-12; recommended action: suppress false positive; model confidence 72%.