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
Betmichat
Confirmed member of a tracked malicious supply-chain campaign.
Analysis record
- Analysed
- Yesterday
- Version
- v7.4.3.86
- Artifact
- SHA256 DC0…28B
- Source
- Findings (non-IoC)
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.
12 evidence rows available.
Finding Categories
Requested Permissions
6 permissionsAI Security Report
AI Security Review
Evidence context: threat category none; evidence quality moderate.
The extension Betmichat is described as a WhatsApp Web business optimization tool, likely functioning as a lightweight CRM or chat organizer. The 21 network findings located in background.js and the content/assets/js/ directory are almost entirely NET-SOCKET_IO, NET-JQUERY_AJAX, and NET-FETCH calls. These are standard mechanisms for a web-based business tool to maintain a real-time connection with its backend servers and handle asynchronous data updates. The file paths, which include versioned hashes like v_7_4_3_85_81c9fdf6, are characteristic of modern JavaScript bundlers splitting a large single-page application into multiple chunks.
The two obfuscation findings are also artifacts of standard web development toolchains. The OBFUSCATION-FUNCTION_INDIRECT finding in content/assets/js/v_7_4_3_85_...253.js matches the pattern of minifiers rewriting function calls to preserve execution context or reduce bundle size, instead of hiding a malicious payload. The OBFUSCATION-LARGE_BASE64 finding in funnil/assets/js/0c7a903c...9ZuTaqvp.js points to a file in a funnil directory, which typically contains marketing, analytics, or onboarding scripts. Large base64 strings in these files are routinely embedded fonts, tracking pixels, or inline SVG assets.
There are zero malware signatures, zero indicators of compromise, and zero code-smell findings in the entire bundle. The developer is identified by a specific contact email ([email protected]), and the low user count of 87 suggests it is a niche or newly published business tool instead of a mass-market lure. The absence of host permissions in the metadata indicates the extension may rely on standard content script injection or user-initiated actions instead of broad network access. This limited permission scope further reduces the risk of unauthorized data collection outside the intended WhatsApp Web environment.
A skeptic might point to the 21 network findings and the use of Socket.IO as a potential data exfiltration channel, especially since the extension interacts with WhatsApp Web. However, a business optimization tool for WhatsApp inherently requires a backend server to sync chat organization, message templates, or CRM data across devices. The network calls are explicitly identified as Socket.IO and jQuery AJAX, which are the expected protocols for this architecture. Without any malicious signatures, suspicious external domains, or credential-harvesting behavior, the findings reflect the normal operation of a bundled web application.
Key Reasons
- Network findings are standard Socket.IO and jQuery AJAX calls from a bundled web application
- Obfuscation findings match minification patterns and base64 encoded assets
- No malware signatures, IoCs, or code-smell findings are present
- Extension description aligns with a CRM business tool requiring real-time backend communication
False Positive Considerations
- Bundled web application with Socket.IO and jQuery triggering network findings
- Minified JavaScript triggering indirect function call obfuscation rules
- Base64 encoded assets in funnel tracking scripts triggering large base64 obfuscation rules
Reviewed 2026-10-10; recommended action: suppress false positive; model confidence 85%.
Chrome version history
Risk trend by version
13 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
Ocultalo
[email protected]
种草星球-TikTok爆单神器,商品自动提报采集邀评【永久免费】
[email protected]
Kindredly - A safer, private web for families
[email protected]
Open Headers
[email protected]
100xBot
[email protected]
Rook
[email protected]