- Google and partners dismantled XCPE after it enrolled more than 1.3 million set-top boxes into a botnet.
- Google observed Videostrong operators capturing screenshots, injecting keystrokes, exfiltrating sensitive data and executing shell commands on devices.
- Google banned Videostrong and its future subsidiaries and affiliates from building or selling certified Android devices or supplying software to certified vendors.
Google and industry partners dismantled the XCPE backdoor after it enrolled more than 1.3 million set-top boxes into a botnet, Google said. The operation also led Google to ban Videostrong and its future subsidiaries and affiliates from building or selling certified Android devices or supplying software to certified vendors.
Google observed operators capturing live screenshots, injecting keystrokes, exfiltrating account and device information, and executing shell commands, including commands used to establish reverse shells.
TrendAI counted 1,472,554 infected devices across 206 models between Jun 3 and Oct 1.
On this page
XCPE was preloaded in firmware and used HTTP and MQTT control
Google said Videostrong used obfuscation techniques to exploit a testing gap and load malicious code after devices completed their first boot. The company said the software had been built directly into many device models and brands over multiple years.
The secondary modules conducted ad fraud, silently enrolled devices in residential proxy networks and loaded additional malware. TrendAI said the operator scheduled proxy and ad-fraud modules onto about 1.33 million devices.
TrendAI saw proxy sales, silent installs and Play Protect changes
TrendAI reported more than 3.8 million distinct home and mobile IP addresses over four months. It said access through infected TV set-top boxes was sold as residential proxy and AI gateway services.
TrendAI observed silent install commands reaching more than 187,000 devices and saw a script that turned off Google Play Protect on a large number of devices. The company said owners cannot remove the implant themselves because it runs as a system app signed with the manufacturer’s key.
Google said it assessed with high confidence that Videostrong intentionally developed, deployed and operated the backdoor and botnet for financial gain. It said Videostrong monetized the operation by selling access to criminal affiliates and loading their malware modules onto infected devices.
Google worked with six partners to disrupt the operation
Google said it worked with Japan’s National Police Agency, Lumen, HUMAN Security, Plume, Synthient and TrendAI to analyze the malware ecosystem and disrupt its operations.
TrendAI said the botnet spanned more than 170 countries. It said the United States, Germany, the United Kingdom, Australia and Canada each had about 26,000 to 42,000 infected devices.
Plume said the botnet included both Google-certified devices and devices running the Android Open Source Project version. The Hacker News said Google’s report did not state how many certified devices were affected.
Google said it took legal action to take down the domains and servers Videostrong used to control the botnet and install malware modules. The company also said the disruption seriously impacted more than a dozen malicious actors.
Google changed its review process and is improving firmware checks for certified Android TV devices. TrendAI said owners cannot remove the implant themselves because it runs as a system app signed with the manufacturer’s key, leaving vendor action, platform protection or device replacement as the stated cleanup options.
What to do now
- Avoid unbranded or uncertified Android TV boxes and apps that pay for shared bandwidth.
- Treat unmanaged consumer devices on home networks as part of your exposure and keep corporate access behind managed endpoints.
- Use published indicators to find MECOOL or similar devices on the network, disconnect and discard any that appear, block the listed control domains and IP addresses, and keep other smart devices on separate network segments away from sensitive systems.
FAQ
What happened to the XCPE Android botnet?
Google and industry partners dismantled the XCPE backdoor after it enrolled more than 1.3 million set-top boxes into a botnet. Google also took legal action against the domains and servers used to control it.
Which devices were affected by XCPE?
TrendAI counted 1,472,554 infected devices across 206 models between Jun 3 and Oct 1.
What could the XCPE backdoor do?
Google observed operators capturing screenshots, injecting keystrokes, exfiltrating sensitive data and executing shell commands.
Who was behind the XCPE botnet?
Google assessed with high confidence that Videostrong intentionally developed, deployed and operated the backdoor and botnet for financial gain. Google said Videostrong sold access to criminal affiliates and loaded their modules onto infected devices.
Can owners remove the XCPE backdoor themselves?
TrendAI said owners cannot remove the implant themselves because it runs as a system app signed with the manufacturer’s key. It said cleanup needs vendor action, platform protection or device replacement.
What did Google do after finding XCPE?
Google banned Videostrong and its future subsidiaries and affiliates from building or selling certified Android devices or supplying software to certified vendors. It also implemented improvements to protect certified Android TV firmware integrity.
Sources
- Shutting the Door on the XCPE Botnet | Google Cloud Blog, Google CloudPrimary
- public-research/2026/11/Videostrong/README.md at main · synthient/public-research, GitHubPrimary
- TrendAI™ Research Helps Disrupt Botnet of More Than 1.3 Million Pre-Infected Set-Top Boxes, TrendAIPrimary
- Google Disrupts 1.3 Million-Device Android Botnet, Says TV Box Maker Sold Criminal Access, The Hacker News
- Google shuts down global botnet running on certified Android devices, CyberScoop
- One of Google’s Android partners turned 1.3 million set-top boxes into a botnet, The Verge
- Google disrupts XCPE botnet, bans the company behind it, Help Net Security
How we checked this story
| Claim | Source | Status |
|---|---|---|
| Google and industry partners dismantled the XCPE backdoor after it enrolled more than 1.3 million set-top boxes. | Google, via Google Cloud | Attributed |
| Google assesses with high confidence that Videostrong intentionally developed, deployed, and operated the backdoor and botnet for financial gain. | Google, via Google Cloud | Attributed |
| Google said videostrong monetized the backdoor by selling access to criminal affiliates and loading their malware modules onto infected devices. | Google, via Google Cloud | Attributed |
| Google said the malicious software was built into many device models and brands over multiple years and used infrastructure designed to evade detection. | Google, via Google Cloud | Attributed |
| Google said videostrong used obfuscation techniques to exploit a testing gap and load malicious code after devices’ first boot. | Google, via Google Cloud | Attributed |
| Google banned Videostrong and its future subsidiaries and affiliates from building or selling certified Android devices or supplying software to certified vendors. | Google, via Google Cloud | Confirmed |
| Google implemented improvements to protect the firmware integrity of certified Android TV devices. | Google, via Google Cloud | Confirmed |
| The botnet used HTTP and MQTT communications to receive configuration, commands, and module download instructions. | Google, via Google Cloud | Confirmed |
| Google observed Videostrong operators capturing screenshots, injecting keystrokes, exfiltrating sensitive data, and executing shell commands. | Google, via Google Cloud | Confirmed |
| TrendAI said the operator scheduled proxy and ad-fraud modules onto about 1.33 million devices. | TrendAI | Confirmed |
| TrendAI reported more than 3.8 million distinct home and mobile IP addresses over four months. | TrendAI | Confirmed |
| TrendAI observed silent install commands reaching more than 187,000 devices and a script disabling Google Play Protect on many devices. | TrendAI | Confirmed |
| TrendAI said owners cannot remove the implant themselves and recommended vendor action, platform protection, or device replacement. | TrendAI | Confirmed |
| TrendAI said access through the infected devices was sold as residential proxy and AI gateway services. | TrendAI | Confirmed |
| Google’s disruption seriously impacted more than a dozen malicious actors, according to the company. | Google, via CyberScoop | Attributed |
| Help Net Security reported that the backdoor reinstalls from a protected partition after reboot and disables Google Play Protect by rewriting its verification setting. | Help Net Security | Attributed |
| Help Net Security said since August 2026, operators have installed droppers disguised as system packages that use a privilege escalation exploit to write into the system partition. | Help Net Security | Attributed |
| Google’s operation involved Japan’s National Police Agency, Lumen, HUMAN Security, Plume, Synthient, and TrendAI. | Google, via Google Cloud | Confirmed |
| Synthient’s research device was a MECOOL device, but a model name alone does not confirm compromise. | Synthient, via GitHub | Confirmed |
| The Hacker News said the botnet lost control of its servers in late October in a Google-led takedown. | The Hacker News | Attributed |
| Google said it was highly confident that Videostrong intentionally put a backdoor in the boxes and sold access to criminals. | Google, via The Hacker News | Attributed |
| The Hacker News said the backdoor remains on the boxes, and owners cannot remove it themselves. | The Hacker News | Attributed |
| The Hacker News said videostrong is based in Shenzhen and makes Android TV boxes and other devices under its own name and for other brands. | The Hacker News | Attributed |
| The backdoor was built into many device models and brands over several years, and Google did not believe a rogue insider or mistake caused it. | Google, via The Hacker News | Attributed |
| The Hacker News said the backdoor enabled operators to install apps silently, run commands, capture screens, and map networks without owners’ knowledge. | The Hacker News | Attributed |
| Google said Videostrong operators took screenshots, sent keystrokes, copied account details and opened reverse shells. | Google, via The Hacker News | Attributed |
| TrendAI counted 1,472,554 infected devices across 206 models between June 3 and October 1. | TrendAI, via The Hacker News | Attributed |
| TrendAI said the United States, Germany, the United Kingdom, Australia and Canada each had about 26,000 to 42,000 infected devices. | TrendAI, via The Hacker News | Attributed |
| Synthient published a list of 182 device model names observed in the campaign. | Synthient, via The Hacker News | Attributed |
| Synthient bought a MECOOL KM9PRO Max and found the backdoor preinstalled. | Synthient, via The Hacker News | Attributed |
| The Hacker News said the backdoor reinstalls itself when the box restarts because it is part of the firmware. | The Hacker News | Attributed |
| TrendAI said cleanup requires vendor action, platform protection, or device replacement. | TrendAI, via The Hacker News | Attributed |
| Synthient recommends that consumers permanently discard affected boxes because they pose a high malware risk. | Synthient, via The Hacker News | Attributed |
| Google changed its review process and is improving firmware checks for certified Android TV devices. | Google, via The Hacker News | Attributed |
| Google said Videostrong hid its code to bypass certification tests and loaded malicious code after first boot. | Google, via The Hacker News | Attributed |
| The Hacker News said as of November 2, Videostrong’s website listed products called Google Certified Android TV Box and Google Certified Android TV Stick. | The Hacker News | Attributed |
| Plume found that the botnet included Google-certified devices and devices running Android Open Source Project. | Plume, via The Hacker News | Attributed |
| The Hacker News said google’s report did not state how many certified devices were affected. | The Hacker News | Attributed |
| The Hacker News said when Google sued over BadBox 2.0 in July 2025, more than 10 million involved devices were uncertified. | The Hacker News | Attributed |
| Google said Videostrong monetized the backdoor by selling access to criminal affiliates and loading their malware modules. | Google, via The Verge | Attributed |
| Google said the infected devices conducted ad fraud, joined residential proxy networks, and loaded additional malware. | Google, via The Verge | Attributed |
| Google said the malware was built directly into many device models and brands over multiple years. | Google, via The Verge | Attributed |
| Google said Videostrong used obfuscation techniques to load malware after users first booted their devices. | Google, via The Verge | Attributed |
| Google Cloud published its report on Nov 2, 2026. | Google Cloud | Confirmed |
Could not verify
- Whether the botnet was exploited by specific criminal buyers is not established.
- How many certified Android devices were infected is not established.
- Whether a factory reset removes the x.cpe backdoor is not established.
- Whether any nation-state actor used the fleet is not established.



