Cybersecurity
Google disrupts XCPE botnet and bans Videostrong
Google said it and partners disrupted the XCPE botnet, linked it to Videostrong Technology Co, and cut off infrastructure tied to additional malware families and compromised devices.
- Google said it and industry partners disrupted XCPE, which it said covered more than 1.3 million Android TV boxes.
- Google attributed the operation with high confidence to Videostrong Technology Co and said the company had put a persistent backdoor into devices it made.
- Google said it took down command servers linked to more than a dozen related malware families and at least 10 million other compromised devices.
- Google said it ended its relationship with Videostrong, revoked its Android TV manufacturing licence and barred the company and future affiliates from certified Android work.
- Synthient said it traced the backdoor to Videostrong after finding the malware preinstalled on a MECOOL KM9PRO Max box and linking company infrastructure to the operator.
Google said it and its partners had broken up XCPE, which it described as a botnet spanning more than 1.3 million Android TV streaming boxes. It said the operation was linked with high confidence to Videostrong Technology Co, which it accused of planting the backdoor in devices it manufactured and selling access to criminal affiliates.
According to Google, those affiliates used the infected boxes for ad fraud, residential proxy services and delivery of further malware. The company also said it cut off command servers connected to more than a dozen associated malware families, affecting at least 10 million additional compromised devices, some of which were not Android boxes.
Google said the backdoor had been built into firmware during manufacturing and that the main components, tracked as x.cpe and com.oemservice, ran with system privileges. It said infected devices contacted anyevonline[.]com for connection details before using an MQTT broker to receive commands.
Google said the malware could install apps, disable Play Protect, run shell commands, take screenshots, record keystrokes and collect device information. It said the operators later used com.abc.nexus as a loader and, from August 2026, began switching to smaller droppers disguised as Android system applications.
Synthient said it tied the campaign to Videostrong after buying a MECOOL KM9PRO Max Android TV box in late 2025 and finding the malware already present. It said it found an open directory on the operators' server, a shared IP address with Videostrong's domain and company email addresses used on the backdoors; Google said it had changed its certification review process and that the malware could reinstall itself from the /oem/ partition.
Named in this story
Companies
- said it and partners disrupted the botnet and moved against Videostrong
- Videostrong Technology Co
- was accused of building and distributing the backdoored devices
- Lumen
- helped analyse the malicious infrastructure
- HUMAN Security
- helped analyse the malicious infrastructure
- Plume
- helped analyse the malicious infrastructure
- Synthient
- published a coordinated report tracing the backdoor to Videostrong
- TrendAI
- helped analyse the malicious infrastructure
Organisations
- Google's Threat Intelligence Group
- published the assessment that blamed Videostrong with high confidence
Governments and agencies
- Japan's National Police Agency
- helped coordinate the disruption
Products and systems
- XCPE
- was the botnet and backdoor Google said it disrupted
- x.cpe and com.oemservice
- were the main backdoor components Google tracked
- MECOOL KM9PRO Max
- was the Android TV box Synthient found infected
- com.abc.nexus
- was the loader Google said appeared in late 2024
- Linkfog
- was one of the residential proxy modules used by the botnet
- AppSalt/Honeygain
- was one of the residential proxy modules used by the botnet
- GaGaNode
- was one of the residential proxy modules used by the botnet
- NetNut
- was one of the residential proxy modules used by the botnet
- Traffmonetizer
- was one of the residential proxy modules used by the botnet
How the source tells it
The article reads as a straight security report, with its emphasis coming from Google's attributed claims and the scale of the device counts rather than from editorial colour.
No emotive framing was found in the original.