Unit 42 Uncovers Malicious AI Browser Extensions Acting as RATs and Infostealers

That AI Extension Helping You Write? It's Actually a RAT Stealing Your Data

HIGH
May 1, 2026
13m read
MalwareThreat IntelligenceThreat Actor

Related Entities

Other

Google Chrome MCP Server - AI Browser ControlSupersonic AI

Full Report

Executive Summary

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.


Threat Overview

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.


Technical Analysis

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.

Attack Vector

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.

Case Study 1: Chrome MCP Server - AI Browser Control (RAT)

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.

  1. Connection: Upon user interaction, it establishes a persistent WebSocket connection to the C2 server.
  2. Command Execution: The extension can receive and execute over 30 remote commands. It uses the dangerous new Function() pattern to execute arbitrary JavaScript received from the C2 server within the context of the user's active tab.
  3. Impact: This allows the attacker to perform any action the user can, such as accessing authenticated corporate portals, online banking, or email accounts. This is a form of T1059.007 - JavaScript.

Case Study 2: Supersonic AI (Attacker-in-the-Browser)

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.

  1. Data Collection: A content script injected into the page reads the Document Object Model (DOM) of the user's email client.
  2. Exfiltration: It collects comprehensive email data—including sender, recipients, subject, and full body content—and exfiltrates it to an external server. This bypasses network security that might look for malicious attachments, as it steals data directly from the rendered page.

MITRE ATT&CK Techniques

The observed behaviors map to the following MITRE ATT&CK techniques:

Tactic
Initial Access
Name
Browser Extensions
Description
The primary entry vector is tricking users into installing a malicious browser extension.
Tactic
Execution
Name
JavaScript
Description
The RAT extension uses new Function() to execute arbitrary JavaScript from the C2 server.
Tactic
Collection
Name
Data from Local System
Description
Extensions read sensitive data from browser storage, cookies, and rendered page content (DOM).
Tactic
Collection
Name
Email Collection: Local Email Collection
Description
The AitB extension scrapes email content directly from the webmail interface.
Tactic
Credential Access
Name
Credentials from Web Browsers
Description
Extensions with broad permissions can access and exfiltrate saved passwords and session cookies.
Tactic
Command and Control
Name
Web Protocols
Description
The RAT uses a WebSocket (wss://) for persistent, bidirectional communication with its C2 server.
Tactic
Exfiltration
Name
Exfiltration Over C2 Channel
Description
Stolen data is sent back to the attacker-controlled server over the established C2 channel.

Impact Assessment

The business impact of these malicious extensions is severe and multifaceted:

  • Data Breach: Direct theft of sensitive corporate data, including intellectual property, financial records, customer lists, and strategic plans that are input into GenAI services.
  • Credential Compromise: Stolen credentials and session tokens can be used to gain unauthorized access to corporate networks, cloud environments, and other critical systems, leading to wider breaches.
  • Financial Loss: Unauthorized access to financial accounts or corporate systems can result in direct financial theft.
  • Compliance Violations: The exfiltration of customer or employee PII can lead to significant fines under regulations like GDPR and CCPA.
  • Reputational Damage: A public breach originating from employee use of unvetted tools can erode customer trust and damage the company's brand.

IOCs — Directly from Articles

The following Indicator of Compromise was explicitly mentioned in the source article.

Type
Domain
Value
mcp-browser.qubecare.ai
Description
C2 domain used by the 'Chrome MCP Server' RAT extension.

Cyber Observables — Hunting Hints

Security teams may want to hunt for the following patterns to detect related activity:

Type
Network Traffic
Value / Pattern
Connections to unknown or newly registered .ai domains
Context / Where to Look
Egress traffic logs from endpoint browser processes.
Type
Network Traffic
Value / Pattern
wss:// (WebSocket) connections to non-standard domains
Context / Where to Look
Firewall, proxy, and NetFlow logs.
Type
Endpoint Process
Value / Pattern
chrome.exe or msedge.exe with command line flags enabling the debugging port
Context / Where to Look
EDR logs, Windows Event ID 4688.
Type
Endpoint Behavior
Value / Pattern
Browser extensions making outbound connections with large data payloads
Context / Where to Look
EDR telemetry, Network Data Loss Prevention (DLP) systems.
Type
Configuration
Value / Pattern
Browser extensions with permissions like debugger, <all_urls>, and webRequest
Context / Where to Look
Browser management consoles (e.g., Chrome Browser Cloud Management), endpoint scripts.

Detection & Response

Detecting and responding to this threat requires a multi-layered approach focusing on the endpoint and network.

  • Endpoint Detection (EDR): Deploy EDR solutions to monitor browser processes for suspicious behavior. Create rules to alert on browser helper objects or extensions writing to disk, spawning new processes (like powershell.exe), or making suspicious network connections. For detection, D3FEND's Process Analysis can be applied to baseline normal browser behavior and flag anomalies.
  • Network Monitoring: Implement Network Traffic Analysis (D3-NTA). Monitor for and alert on WebSocket connections to untrusted or newly registered domains. Use SSL/TLS inspection to gain visibility into encrypted traffic where possible, and block known malicious domains and IPs at the network perimeter.
  • Browser Auditing: Regularly audit installed browser extensions across the enterprise. Use enterprise browser management tools to query for extensions with high-risk permissions. Cross-reference installed extension IDs against threat intelligence feeds.
  • Incident Response: If a malicious extension is found, the response plan should include: isolating the affected host, revoking all user credentials and active sessions, preserving the endpoint for forensics, and analyzing proxy/firewall logs to determine the scope of data exfiltration.

Mitigation

Organizations should implement a combination of technical controls and user awareness to mitigate this threat.

  1. Restrict Extension Installation: Use enterprise browser management policies (e.g., Chrome Browser Cloud Management, Microsoft Edge policies) to enforce an allowlist of approved extensions. This is the most effective technical control. This corresponds to MITRE ATT&CK Mitigation M1033 - Limit Software Installation.
  2. User Education and Training: Train users to be skeptical of extensions, especially those requesting broad permissions. Teach them to scrutinize permissions dialogues and understand the risks of granting access to 'all website data'. This aligns with M1017 - User Training.
  3. Principle of Least Privilege: Apply the principle of least privilege to user accounts to limit the impact of a compromise. Avoid having users operate with local administrator rights.
  4. Regular Audits: Implement a process to regularly audit and review installed browser extensions and their permissions across the organization. This aligns with M1047 - Audit.
  5. Network Segmentation: Segment networks to prevent lateral movement from a compromised user workstation to critical servers. This aligns with M1030 - Network Segmentation.

Timeline of Events

1
May 1, 2026
This article was published

MITRE ATT&CK Mitigations

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.

Mapped D3FEND Techniques:

Educate users on the dangers of browser extensions and how to scrutinize requested permissions before installation.

Audit

M1047enterprise

Implement a continuous process to audit installed extensions and their permissions across all corporate devices.

Mapped D3FEND Techniques:

Use web filters and firewalls to block connections to known malicious domains and C2 servers identified through threat intelligence.

Mapped D3FEND Techniques:

Leverage security tools to analyze and filter web content, including the code within browser extensions, to identify and block malicious components before they execute.

D3FEND Defensive Countermeasures

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.

Sources & References

That AI Extension Helping You Write Emails? It’s Reading Them First
Unit 42 (unit42.paloaltonetworks.com) April 30, 2026

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

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.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Tags

AI SecurityBrowser ExtensionMalwareInfostealerRATGenAIThreat ResearchAttacker-in-the-BrowserUnit 42

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

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.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

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 Generator

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.