Is "chromePlugin" on Chrome Web Store Safe to Install?
The Doctor AI Assistant Chrome plugin is an intelligent tool designed specifically for healthcare professionals to improve work efficiency and patient care quality. Double click input in the webpage to activate the AI Q&A window, ask the AI for the answer to the question, and use the application button to fill in the Q&A content in the current page input box, greatly reducing the workload of personnel.
Risk Assessment
Analyzed13829 security findings detected across all analyzers
Severity Breakdown
Finding Categories
YARA Rules Matched
18 rules(1000 hits)About This Extension
Detailed Findings
1000 totalYARA Rule Matches
18 rulesAI Security Report
AI Security Analysis: chromePlugin
Analysis generated: 2025-12-11T15:48:39+13:00
Model: gemini-3-pro-preview
Quick Facts
| Property | Value |
|---|---|
| UUID | 934af163-5ad0-5a48-b9eb-f63714f05f71 |
| Type | chrome |
| Version | |
| Users | 0 |
| Risk Score | 100.0/100 (CRITICAL) |
| Malware Detected | ⚠️ Yes |
| Secrets Exposed | ✅ No |
| Critical Vulns | ✅ No |
AI Analysis
Executive Summary
The extension "chromePlugin" represents a CRITICAL security threat and should be blocked immediately. Despite claiming to be a tool for healthcare professionals, the extension has zero users, an unverified publisher, and contains over 13,000 security findings. The analysis indicates the presence of severe malware capabilities, including arbitrary system command execution, file manipulation, and persistence mechanisms. The discrepancy between its generic name and its targeted description suggests a social engineering attempt aimed at the healthcare sector.
Threat Assessment
The security posture of this extension is non-existent; it appears to be a dedicated malicious payload rather than a functional tool.
- Malware Capabilities: The analysis detected 2,964 high-severity malware signatures. The recurring "postinstall" tags (e.g.,
postinstall_system_command,postinstall_file_download) strongly suggest the extension acts as a dropper or downloader. It is designed to execute scripts immediately upon installation to compromise the host system. - Behavioral Analysis:
- Remote Code Execution (RCE): Multiple findings for
system_commandindicate the extension attempts to run shell commands on the host OS. - Persistence: The
postinstall_persistence_mechanismfindings indicate attempts to modify system settings to ensure the malware survives restarts. - Obfuscation: The presence of
postinstall_obfuscationsuggests the code is intentionally hidden to evade traditional antivirus detection. - Data Exfiltration/Crypto: Findings related to
crypto_operationsandcredential_env_filessuggest capabilities to steal credentials or perform unauthorized cryptographic operations (potentially ransomware or cryptojacking).
- Remote Code Execution (RCE): Multiple findings for
- Targeting: The description ("tools designed specifically for healthcare professionals") combined with the malicious payload indicates a targeted attack against the healthcare sector, likely to harvest sensitive patient data (PHI) or credentials.
Risk Justification
The Risk Score of 100.0/100 is fully justified and accurate.
- Severity of Findings: The presence of nearly 3,000 HIGH severity findings is catastrophic. A typical "risky" extension might have 5-10; this volume indicates the codebase is fundamentally malicious.
- Zero Trust: The extension has a Trust Score of 0.0, 0 users, and no verified publisher. There are no mitigating factors such as community reputation or developer history.
- Active Threat: The combination of network communication (
postinstall_network_communication) and file downloading (postinstall_file_download) indicates this is an active threat capable of fetching secondary payloads.
Key Findings
- Arbitrary Command Execution: (Findings 1, 4, 7, 10, etc.) The extension contains code to execute system-level commands, bypassing the browser sandbox.
- Dropper Functionality: (Findings 2, 11, 18, 24) Signatures for
file_downloadindicate the extension is designed to fetch and install additional files (likely malware) from external servers. - Persistence Mechanisms: (Findings 17, 23, 30) The code attempts to establish persistence, ensuring the malicious activity continues even after the browser is closed.
- Credential Harvesting: (Finding 15) The
credential_env_filessignature suggests specific targeting of environment variables and configuration files where developers and systems often store secrets. - Code Obfuscation: (Findings 14, 21) The use of obfuscation techniques confirms malicious intent, as the developer is actively trying to hide the code's logic from analysis.
Recommendations
- IMMEDIATE BLOCK: Blacklist this extension UUID (
934af163-5ad0-5a48-b9eb-f63714f05f71) across the organization immediately. - Forensic Investigation: If this extension was found installed on any endpoint, that machine must be considered fully compromised. Isolate the device and initiate incident response procedures.
- Network Blocking: Review the 22
networkfindings (not detailed in the summary but present in the aggregate data) to identify and block the Command & Control (C2) domains associated with this extension. - Credential Rotation: If any user installed this, force a reset of all credentials used on that machine, specifically focusing on healthcare portal logins and environment variables.
Mitigation Strategies
There is no safe way to use this extension.
- Remediation: The only valid mitigation is complete removal.
- Future Prevention: Implement a "Deny by Default" policy for browser extensions, allowing only those that have been vetted and approved. Given the healthcare targeting, ensure staff are trained on the risks of installing unverified "productivity tools."
Confidence Assessment
Confidence Level: High (95%)
While the automated report states 80% confidence, the convergence of evidence raises the certainty level. The combination of a generic name, zero users, unverified publisher, and thousands of specific malware signatures (RCE, Persistence, Obfuscation) leaves virtually no room for this to be a false positive. The "postinstall" naming convention in the signatures strongly suggests this is a malicious package (likely from the NPM ecosystem) wrapped into a Chrome extension format.
Disclaimer
This analysis was generated by an AI model and should be reviewed by security professionals. The findings are based on automated security scanning and may include false positives. Always verify critical findings manually before taking action.
Source Code Not Available
Source code is not available for this version of the extension.
Frequently Asked Questions
Similar Extensions
Related extensions from the same publisher or marketplace
ZD Quick Messages
[email protected]
mmbl Voice Notes
[email protected]
Strong HR
[email protected]
PomodoroPro
[email protected]
Upload File
[email protected]
VK Attachments Gallery
[email protected]