Executive Summary
In October 2026, cybersecurity researchers discovered 16 malicious Mozilla Firefox extensions masquerading as legitimate Rabby and OKX cryptocurrency wallets. These extensions specifically targeted cryptocurrency users by intercepting wallet recovery phrases and private keys during import flows, then exfiltrating the stolen credentials to attacker-controlled Cloudflare Workers infrastructure. The campaign represents a continuation of earlier attacks documented in August 2026, with threat actors rotating package names and extension identifiers while reusing the same credential-harvesting logic and network infrastructure. All identified extensions have been removed from the Firefox add-on store as of October 5, 2026.
This incident highlights the growing sophistication of cryptocurrency-focused malware campaigns and the increasing abuse of browser extension ecosystems for credential theft. The attack demonstrates how threat actors are systematically targeting the expanding cryptocurrency user base through trusted distribution channels, making extension security and wallet hygiene critical priorities for organizations and individuals managing digital assets.
Why This Matters Now
Cryptocurrency theft via malicious browser extensions is surging as digital asset adoption accelerates. With over $3.8 billion stolen through crypto-related attacks in 2024, organizations must prioritize browser security and employee education to protect against wallet compromise and corporate asset theft.
Attack Path Analysis
Attackers distributed 16 malicious Firefox extensions masquerading as legitimate cryptocurrency wallets (Rabby and OKX) through browser extension stores. Once installed, the extensions intercepted wallet recovery phrases and private keys during import flows, then exfiltrated this sensitive data to attacker-controlled Cloudflare Workers infrastructure. The attack leveraged social engineering and application impersonation to compromise user credentials without requiring traditional network-based lateral movement.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
Malicious Firefox extensions distributed through browser stores, masquerading as legitimate Rabby and OKX wallet interfaces to deceive users into installation
MITRE ATT&CK® Techniques
Spearphishing Link
Browser Extensions
Keylogging
Steal Web Session Cookie
Exfiltration Over C2 Channel
Match Legitimate Name or Location
Exfiltration to Cloud Storage
Credentials from Web Browsers
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Security Awareness Program
Control ID: 12.6.2
NYDFS 23 NYCRR 500 – Penetration Testing and Vulnerability Assessments
Control ID: 500.15
CISA ZTMM 2.0 – Asset Management and Visibility
Control ID: ZT.AM-1
DORA – Identification and Classification of ICT Risk
Control ID: Article 8
NIS2 Directive – Cybersecurity Risk Management Measures
Control ID: Article 21
ISO 27001:2022 – Web Filtering
Control ID: A.8.23
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Financial Services
Malicious Firefox extensions stealing cryptocurrency wallet recovery phrases directly threaten digital asset security, customer trust, and regulatory compliance requirements.
Investment Management/Hedge Fund/Private Equity
Infostealer malware targeting crypto wallets poses significant asset protection risks for firms managing digital investments and client cryptocurrency portfolios.
Computer/Network Security
Browser extension threats demonstrate sophisticated attack vectors requiring enhanced egress security, threat detection, and client protection strategies for security providers.
Information Technology/IT
Malicious extensions bypassing browser security controls highlight critical vulnerabilities in enterprise IT infrastructure requiring immediate extension auditing and monitoring.
Sources
- 16 Malicious Firefox Extensions Pose as Rabby and OKX Wallets to Steal Recovery Phraseshttps://thehackernews.com/2026/10/16-malicious-firefox-extensions-pose-as.htmlVerified
- Firefox Crypto Wallet Stealershttps://socket.dev/blog/firefox-crypto-wallet-stealersVerified
- 40 Malicious Firefox Extensions Pose as Crypto Walletshttps://thehackernews.com/2026/08/40-malicious-firefox-extensions-pose-as.htmlVerified
- Firefox Google Account Takeover Extensionhttps://socket.dev/blog/firefox-google-account-takeoverVerified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.
Aviatrix Zero Trust CNSF would reduce the scope and impact of this browser extension cryptocurrency theft campaign by constraining network communications and limiting lateral access across cloud infrastructure. While the initial browser compromise would still occur, segmentation controls would likely contain the attack's reach and reduce the blast radius of credential exfiltration.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: While the initial browser extension installation would likely still succeed through social engineering, CNSF network visibility could detect subsequent anomalous communication patterns and unauthorized outbound connections to reduce operational scope.
Control: Zero Trust Segmentation
Mitigation: Zero Trust segmentation policies would likely constrain the extension's network reach and limit cross-domain access paths, reducing the scope of accessible wallet services and cryptocurrency platforms during privilege expansion activities.
Control: East-West Traffic Security
Mitigation: East-west traffic controls would likely limit the extension's ability to move between different cryptocurrency service environments and constrain access to wallet management platforms, reducing the overall scope of credential harvesting operations.
Control: Multicloud Visibility & Control
Mitigation: Multicloud visibility controls would likely detect and constrain unauthorized communications to suspicious Cloudflare Workers domains, potentially disrupting command coordination and limiting the attacker's ability to maintain persistent control channels.
Control: Egress Security & Policy Enforcement
Mitigation: Egress security policies would likely constrain unauthorized outbound data transmissions to suspicious external domains, potentially blocking or limiting the volume of wallet credential exfiltration to attacker-controlled infrastructure.
Despite segmentation controls, victims would likely still face exposure to cryptocurrency asset theft from already exfiltrated wallet credentials, though the overall scope and number of compromised accounts would be reduced compared to an unconstrained attack.
Impact at a Glance
Affected Business Functions
- Cryptocurrency Wallet Management
- Digital Asset Security
- Browser Extension Security
- User Authentication Systems
Estimated downtime: N/A
Estimated loss: N/A
Cryptocurrency wallet recovery phrases, private keys, and mnemonic phrases from users who installed malicious Firefox extensions impersonating Rabby and OKX wallets. The exposed credentials could lead to complete compromise of cryptocurrency holdings and digital assets.
Recommended Actions
Key Takeaways & Next Steps
- • Implement Egress Security & Policy Enforcement to block unauthorized outbound connections to suspicious domains like Cloudflare Workers endpoints used for data exfiltration
- • Deploy Multicloud Visibility & Control capabilities to detect anomalous browser extension communications and repeated malformed requests to external infrastructure
- • Establish Zero Trust Segmentation policies to limit browser extension privileges and prevent access to sensitive credential storage locations
- • Enable Threat Detection & Anomaly Response monitoring to identify suspicious browser behavior patterns and credential harvesting activities
- • Utilize Cloud Firewall (ACF) with URL filtering to block known malicious domains and prevent communication with attacker-controlled infrastructure



