0.1% of Hola Browser users
A supply chain attack has compromised the Windows version of Hola Browser, a popular application with a large user base. The attack involved injecting a malicious cryptocurrency miner into the software's delivery pipeline, causing some users to unknowingly install the malware alongside the legitimate browser. The malware, identified as a Monero (XMR) miner based on XMRig, was designed to run stealthily when the infected computer was idle. Sophos and other security firms discovered the compromise during a routine certification test. Hola has confirmed the incident, stating it affected a small fraction of users (0.1%) and that they have since rebuilt their distribution infrastructure with enhanced security controls.
This incident is a classic software supply chain attack, where attackers compromise the process of software creation or distribution to infect downstream users.
me.exe into the installation package for Hola Browser version 1.251.91.0.me.exe was also installed. The malware would then:C:\Program Files\Hola\app\HolaMonitorService.exe.hola_monitor_svc to ensure persistence across reboots.While Hola claims only 0.1% of users were affected and no user data was stolen, the impact of a supply chain attack is significant:
me.exeHolaMonitorService.exehola_monitor_svcSecurity teams should hunt for signs of cryptojacking:
HolaMonitorService.exeHolaMonitorService.exeFor vendors, strictly enforcing that all distributed binaries are code-signed helps prevent the injection of malicious unsigned files.
For vendors, regularly scanning build and distribution servers for vulnerabilities is crucial to prevent the initial compromise that enables a supply chain attack.
For users, up-to-date antivirus and EDR solutions can detect known cryptominers and their behaviors, such as high CPU usage.
This supply chain attack succeeded because a malicious binary was added to a legitimate software package. For Hola, a key mitigation is to implement stringent verification throughout the build and release pipeline. This means automatically verifying the digital signature and hash of every single file included in the final installer. Any unsigned binary, like the me.exe file in this case, or any binary with a mismatched hash, should automatically fail the build process. This automated verification ensures that only approved and signed code makes it into the final product that is shipped to users, making it significantly harder for an attacker to inject malicious code.
On the victim's side, detecting cryptojacking relies on behavioral analysis. An EDR solution should be configured to monitor for processes exhibiting cryptominer-like behavior. This includes a process that has low or no network activity for a long time and then suddenly shows sustained high CPU usage when the user is idle (i.e., no keyboard or mouse input). In this specific case, an alert could be triggered for the process HolaMonitorService.exe consuming >80% CPU for more than 5 minutes while the machine is idle. This behavioral approach is effective at detecting cryptojacking regardless of the specific malware family, as they all share the common goal of hijacking CPU resources.
Security researchers report the discovery of a cryptominer being distributed by Hola Browser.

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.