Security researchers at Palo Alto Networks Unit 42 have identified a significant and emerging threat vector: malicious browser extensions disguised as Generative AI (GenAI) productivity aids. At least 18 such extensions were discovered and reported to Google, which have since been removed or flagged. These extensions trick users into granting extensive permissions by promising AI-powered features. In reality, they deploy a range of malware including Remote Access Trojans (RATs), infostealers, and Attacker-in-the-Browser (AitB) tools. The primary goal is to steal sensitive data, such as credentials, proprietary information entered into AI prompts, and session cookies. This threat represents a critical risk for organizations, as compromised browsers can lead to the exfiltration of corporate data and provide a foothold for broader network intrusion.
Leveraging the widespread adoption of GenAI tools, threat actors are packaging established malware techniques into deceptive browser extensions. These extensions, marketed with names suggesting AI integration for email, browsing, and content creation, exploit the trust users place in productivity applications. Once installed, they abuse the browser's permission model to conduct malicious activities.
Unit 42 categorized the malicious behaviors into six main types: RATs, AitB, spyware, search hijackers, infostealers, and MitM proxies. A key finding is the targeting of data entered into AI service prompts. As employees increasingly use Large Language Models (LLMs) for work—drafting emails, writing code, and developing strategies—these prompts become a treasure trove of sensitive corporate information. By intercepting these prompts, attackers can steal intellectual property, internal communications, and strategic plans directly from the source. The research also noted that some of the malicious code itself appeared to be AI-generated, indicating that attackers are using LLMs to accelerate their own development cycles.
Malicious browser extensions operate within the browser's trusted security context, making them a powerful tool for attackers. They use legitimate browser APIs to perform malicious actions, often bypassing traditional network-based security controls.
The primary attack vector is social engineering, luring users to install the extension from the Chrome Web Store or other marketplaces. The extensions request broad permissions, such as access to <all_urls>, debugger, and webRequest, justifying them as necessary for their advertised AI functionality.
This extension, Chrome MCP Server - AI Browser Control, functions as a full-featured Remote Access Trojan. Despite its store description claiming "100% local processing," the extension contains a hardcoded WebSocket C2 address: wss[:]//mcp-browser.qubecare[.]ai/chrome.
new Function() pattern to execute arbitrary JavaScript received from the C2 server within the context of the user's active tab.T1059.007 - JavaScript.This extension, Supersonic AI, markets itself as an AI email assistant for Gmail and Outlook. It uses an Attacker-in-the-Browser (AitB) technique to steal data.
The observed behaviors map to the following MITRE ATT&CK techniques:
new Function() to execute arbitrary JavaScript from the C2 server.wss://) for persistent, bidirectional communication with its C2 server.The business impact of these malicious extensions is severe and multifaceted:
The following Indicator of Compromise was explicitly mentioned in the source article.
mcp-browser.qubecare.aiSecurity teams may want to hunt for the following patterns to detect related activity:
.ai domainswss:// (WebSocket) connections to non-standard domainschrome.exe or msedge.exe with command line flags enabling the debugging portdebugger, <all_urls>, and webRequestDetecting and responding to this threat requires a multi-layered approach focusing on the endpoint and network.
powershell.exe), or making suspicious network connections. For detection, D3FEND's Process Analysis can be applied to baseline normal browser behavior and flag anomalies.Organizations should implement a combination of technical controls and user awareness to mitigate this threat.
M1033 - Limit Software Installation.M1017 - User Training.M1047 - Audit.M1030 - Network Segmentation.Use enterprise browser management tools to create an allowlist of approved, vetted extensions and block all others. This is the most effective control against this threat.
Educate users on the dangers of browser extensions and how to scrutinize requested permissions before installation.
Implement a continuous process to audit installed extensions and their permissions across all corporate devices.
Use web filters and firewalls to block connections to known malicious domains and C2 servers identified through threat intelligence.
Mapped D3FEND Techniques:
To counter the threat of malicious AI browser extensions, organizations must implement strict control over what software can run within their browsers. Using enterprise browser management platforms like Chrome Browser Cloud Management or Microsoft Edge management services, administrators should configure a policy that blocks all extensions by default and only permits the installation of extensions on a pre-approved allowlist. This 'deny-all, permit-by-exception' approach is the most effective defense. The vetting process for an extension should include a review of the developer's reputation, a thorough analysis of the permissions it requests, and ideally, a static analysis of its code. This directly prevents the initial compromise vector described by Unit 42, as users would be unable to install the unvetted, malicious 'Chrome MCP Server' or 'Supersonic AI' extensions in the first place. This shifts the security burden from the end-user to the IT department, providing a consistent and enforceable security posture across the organization.
For detecting compromised systems where a malicious extension is already active, Network Traffic Analysis (NTA) is crucial. Security teams should configure monitoring tools to specifically scrutinize traffic originating from browser processes on endpoints. In the context of the 'Chrome MCP Server' RAT, this involves creating alerts for any WebSocket (WSS) connections to domains that are not part of a known-good list of corporate applications. Specifically, rules should be created to flag and block traffic to the IOC mcp-browser.qubecare.ai and other newly registered or uncategorized domains. Furthermore, NTA solutions can be used to baseline normal data transfer volumes for browser processes. A sudden spike in outbound data from a user's browser, especially to an unusual destination, could indicate data exfiltration by an infostealer or AitB extension like 'Supersonic AI'. This technique provides a critical detection layer that can identify an active compromise even if the extension itself evaded endpoint defenses.
On the endpoint, Process Analysis via an EDR solution is vital for detecting the malicious behaviors of these extensions post-installation. EDR policies should be configured to monitor for anomalous activities originating from the browser's process tree. For example, a rule should be created to alert if a browser process (chrome.exe, msedge.exe) attempts to spawn a command shell (cmd.exe, powershell.exe) or uses debugging protocols for non-development purposes. In the case of the 'Chrome MCP Server' RAT, its use of new Function() to execute arbitrary code is a high-fidelity indicator of compromise that advanced EDR tools may be able to hook and detect. By establishing a baseline of normal browser process behavior, security teams can create high-confidence alerts for deviations that suggest a malicious extension is active, such as unexpected file I/O, registry modifications, or inter-process communication attempts.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.