Our analysis confirmed the behaviour described in the threat library entry. Do not install it. Read the analysis and indicators →
Also reported by malext.io, reddit.com
ClickZap
Confirmed member of a tracked malicious supply-chain campaign.
Analysis record
- Analysed
- 2 days ago
- Version
- v7.4.3.87
- Artifact
- SHA256 6C4…EF3
- Source
- Findings (non-IoC)
Is ClickZap safe?
ClickZap describes itself as a customer relationship management tool for WhatsApp Web. It declares no special permissions. The bundle lists zero network endpoints and zero host permissions. This means the extension does not ask the browser for broad access to your data or specific websites.
The automated scanner flagged 21 network events. These include a fetch call at background.js:52:0 and socket connections in content/assets/js/v_7_4_3_85_81c9fdf6-5aa3-4e05-88c1-f94c9eaf692012.js:15:0. The scanner also flagged base64 encoding in funnil/assets/js/0c7a903c-6665-4db4-bec2-13ad7e8d3381.9ZuTaqvp.js:1:0. If these were malicious, they would indicate the extension is secretly sending your WhatsApp chats to an external server.
The evidence does not support that conclusion. Network flags simply detect that the code contains standard JavaScript functions for making web requests. A CRM needs these to sync data. The base64 flag is a common artifact of minified code used to shrink file sizes. The scanner found zero malware signatures and no suspicious domains. It tripped on normal web development patterns rather than actual threats.
Evidence ledger
Ranked by severity · findings with a source location link to the code viewer
Publisher Evidence
Limited evidencePublisher identity, store signals, distribution reach, and warning signals used for context. Treat this as supporting evidence, not a clean bill of health.
Chrome does not expose the same publisher verification data as IDE stores, so this score is deliberately conservative.
11 evidence rows available.
Finding Categories
Requested Permissions
5 permissionsAI Security Report
AI Security Review
Evidence context: threat category none; evidence quality moderate.
ClickZap presents itself as a customer relationship management tool for WhatsApp Web. The developer is listed as [email protected], and the extension currently has a very small user base of 31. The stated purpose is to organize chats and optimize business operations within the WhatsApp Web interface.
The scanner recorded 21 network findings, including NET-FETCH-background.js-52, NET-FETCH-background.js-63, and NET-SOCKET_IO-content/assets/js/v_7_4_3_85_81c9fdf6-5aa3-4e05-88c1-f94c9eaf692012.js-15. Additional jQuery AJAX calls were flagged in content/assets/js/v_7_4_3_85_81c9fdf6-5aa3-4e05-88c1-f94c9eaf692021.js-1. These flags indicate the presence of standard web request functions in the JavaScript. A CRM application requires network connectivity to synchronize chat data and manage customer interactions. The bundle lists zero actual network endpoints and zero host permissions. The scanner detected the mechanisms for network communication without identifying any hardcoded destinations.
Two obfuscation findings were also recorded. The first is OBFUSCATION-LARGE_BASE64-funnil/assets/js/0c7a903c-6665-4db4-bec2-13ad7e8d3381.9ZuTaqvp.js-1. The second is OBFUSCATION-FUNCTION_INDIRECT-content/assets/js/v_7_4_3_85_81c9fdf6-5aa3-4e05-88c1-f94c9eaf6920253.js-1. Large base64 strings and indirect function references are standard characteristics of minified or bundled JavaScript. Modern build tools like webpack or esbuild routinely produce this exact pattern when compiling frontend assets. The file path funnil/assets/js/ points to a bundled frontend asset, likely a marketing funnel script common in CRM software. These artifacts reflect build tool output rather than intentional payload hiding.
A skeptic might argue that WhatsApp CRM extensions are a frequent vector for session hijacking. They would point to the anonymous developer email and the low user count as warning signs. They might also claim the lack of declared permissions is suspicious, since a WhatsApp CRM inherently needs to read web content to function. However, the evidence bundle contains zero malware signatures and zero credential-stealing indicators. The network calls point to unnamed endpoints, and the obfuscation is standard minification. Without specific indicators of compromise or malicious payloads, the fear of what the extension might do does not outweigh the actual evidence of what it does in this snapshot.
Key Reasons
- No malware signatures or credential theft indicators found in the bundle
- Network findings are standard fetch and socket.io calls required for CRM synchronization
- Obfuscation flags are typical minification artifacts from bundled frontend assets
- Extension declares no special permissions and lists no suspicious network endpoints
False Positive Considerations
- Minified JavaScript triggering obfuscation rules
- Standard network functions triggering network event flags
- Bundled frontend assets producing base64 artifacts
Reviewed 2026-10-09; recommended action: suppress false positive; model confidence 85%.
Chrome version history
Risk trend by version
16 analyzed versions. Each point is the latest successful scan for that version; failed zero-score scans are hidden. Dates are based on first seen by risky plugins.
Pick any point on the chart to explore that version's code below.
Source Code Not Available
Source code is not available for this version of the extension.
About This Extension
Frequently Asked Questions
Similar Extensions
Related extensions from the same publisher or marketplace
waSuper
[email protected]
Wa Elo IA
[email protected]
Whapro – Automação, CRM e Vendas no WhatsApp Web
[email protected]
Vende+
[email protected]
WaListall | O Melhor CRM para WhatsApp Web – Teste Grátis
[email protected]
InfiChat
[email protected]