On this page (9 sections)
The Google Threat Intelligence Group (GTIG) said it worked with industry partners to dismantle XCPE, a botnet of more than 1.3 million Android TV set-top boxes that shipped with a backdoor in the firmware. According to Infosecurity Magazine, GTIG published its blog post on November 2, and both that outlet and Krebs on Security describe the infected devices being used for ad fraud and rented out as residential proxies.
This matters to two groups: anyone who owns or manages Android-based TV boxes, signage or similar devices, and website owners who see account takeover, scraping or fraud traffic coming from ordinary home IP addresses. The research available for this story is press reporting only. We did not have the original GTIG post, so details below are attributed to how those outlets describe it.
At a glance
What happened
GTIG says Videostrong Technology, a Chinese Android ODM/OEM, was responsible for the XCPE backdoor, and that the malicious software was found built into many device models and brands over multiple years. Google said it has cut ties with the company and banned it from making devices with preloaded Google apps. Krebs adds that Google took legal action to take down the domains and servers used to control the botnet.
Per Infosecurity Magazine, Videostrong sold access to criminal affiliates and loaded their malware modules onto infected devices. Those modules were conducting ad fraud, silently enrolling devices into residential proxy networks and loading additional malware. The reports say the action disrupted command servers that affiliates used to install over a dozen malware families.
Although set-top boxes were the majority, both reports say the same malware was found in other Android-based products, including telehealth devices, karaoke machines and digital signage.
How the backdoor reportedly works
Infosecurity Magazine's summary of the GTIG findings describes the behavior below. We cannot verify these details independently.
- The backdoor, called x.cpe, runs at android.uid.system privilege level, which is very high on an Android device.
- It automatically reinstalls itself from the /oem/ partition on reboot if a user tries to get rid of it. This is the only persistence mechanism the reports describe.
- On startup it contacts a command server and uses the MQTT message broker for commands.
- Affiliates could remotely execute shell scripts, disable Google Play Protect and silently install additional apps.
Krebs reports that Google requires all Android device makers to pass compatibility and security tests, yet Videostrong found a way to load its malicious software right after a user first boots a device. Google says it has since addressed that weakness.
Why residential proxies matter to website owners
Residential proxy services let customers rent household IP addresses to anonymize traffic or spoof location, which makes abusive traffic look like ordinary visitors. Krebs describes these services as a major source of unwanted and often malicious traffic, including account takeover, advertising fraud and mass content scraping. Infosecurity Magazine lists account takeover, payment fraud, ad and click fraud, web scraping and DDoS.
Infosecurity Magazine names proxy providers whose malware modules were installed on infected devices: Linkfog, AppSalt/Honeygain, GaGaNode, NetNut and Traffmonetizer. Krebs says the GTIG report also names EarnFM, Jaguar and BMW/IPWeb. These are claims from the GTIG report as relayed by the press, and we have not seen the original wording.
Google cautioned that the underlying market is resilient: backdoor operators, ad-fraud rings and proxy providers operate as an interconnected supply chain and quickly pivot to new loaders or monetization SDKs when one part is disrupted. Expect proxy-sourced abuse to continue. For related basics on traffic floods, see our guide to DDoS protection for small businesses.
Who is exposed
- Home users and businesses running Android TV boxes. The reports do not publish a list of affected models or brands, and Google says the malware was found in many models and brands. The sources do not say that price or brand predicts infection.
- Organizations with Android-based telehealth devices, karaoke machines or digital signage, which the reports say were also affected.
- Website and store owners who defend login pages, checkout flows and APIs. This botnet does not compromise your site, but proxy traffic like it may hit you.
- Network administrators, because infected devices sit inside local networks. Krebs notes that earlier Synthient research on the separate Kimwolf botnet documented a widespread vulnerability in residential proxy services used to compromise other Android devices inside the local networks of TV box users.
How to check for exposure
You cannot reliably confirm infection from outside the device. The checks below are heuristics we derived from the behavior the reports describe. They are not confirmed indicators of compromise, and a clean result does not prove a device is safe.
- Inventory every Android-based box, sign, kiosk and IoT device on your networks, including ones nobody remembers installing. Record make, model and where it was bought, so you can compare against Google's and Synthient's published material.
- Review router or firewall logs for unexpected outbound connections from these devices. Because the reports say the backdoor uses MQTT to talk to a command server, persistent connections to unfamiliar hosts from devices with no reason to make them are worth investigating. Absence of such traffic proves nothing.
- Check whether Google Play Protect is enabled in the device settings. The reports say the backdoor can disable it, so if it is off and you did not turn it off, treat that as a reason to look closer, not as proof of infection.
- Do not assume a factory reset cleans a device. The sources do not say whether a reset removes the backdoor; the only persistence behavior reported is reinstalling itself from the /oem/ partition on reboot.
On the web server side, you can look for spikes of logins or scraping from many different residential IP addresses. This command counts requests per client IP in an nginx access log in the common log format. Run it on the web server and look for IPs with unusually high counts. Adjust the log path to your setup.
awk '{print $1}' /var/log/nginx/access.log | sort | uniq -c | sort -rn | head -20What to do now
- Keep any TV box or Android IoT device you suspect of carrying a preinstalled backdoor off business or sensitive networks. The reported reinstall-from-/oem/ behavior means user removal may not last.
- Put unmanaged IoT and media devices on a separate guest or IoT network segment, isolated from computers, servers and point-of-sale systems.
- Block or alert on outbound traffic from IoT segments except what the device genuinely needs.
- When you cannot confirm a device is clean, plan its replacement. Google says the malware was found across many models and brands, and that certification tests were bypassed, so neither brand nor certification proves a device is clean.
- Review the apps installed on Android devices you manage and remove any you did not deliberately install, including proxy or bandwidth-sharing software.
- Protect your own sites against proxy-sourced abuse: enforce multi-factor authentication, rate-limit login and checkout endpoints, and watch for credential stuffing spread across many IPs.
- Do not block traffic by IP reputation alone. Residential addresses belong to real households, so combine rate limits, behavior signals and a web application firewall (see what a WAF is).
Detection and monitoring
Proxy-sourced abuse is hard to spot because each address looks like an ordinary visitor. Useful signals are many failed logins spread across thousands of IPs, sudden scraping of catalog or content pages, and ad or click patterns that do not convert. Keep access logs long enough to compare week over week, and review them after any announced takedown, since Google warns operators quickly pivot to new tooling.
If you run an online store, also watch checkout pages for unexpected script changes, since fraud operators combine techniques. Webforta Monitor can track uptime, certificate, DNS and header changes, and the free security headers checker is a quick way to review your site's baseline. Neither detects this botnet; they help you notice changes on your own site.
Timeline and open questions
| When | Event |
|---|---|
| January 2026 | Synthient publishes research on the Kimwolf botnet, which infected millions of Android set-top boxes (per Krebs) |
| July 2026 | FBI and partners seize hundreds of domains associated with NetNut, saying it operated a separate botnet called Popa (per Krebs) |
| October 2026 | Oxylabs and Honeygain reorganized under an umbrella entity called Source (per Krebs) |
| November 2, 2026 | GTIG blog post on XCPE and the takedown (per Infosecurity Magazine) |
| November 3, 2026 | Krebs on Security and Infosecurity Magazine publish their reports |
Open questions remain. The over-10-million figure is Google's claim in Infosecurity Magazine and an expectation from involved experts in Krebs, not an independently verified count. The full list of affected models, and whether devices already in homes can be cleaned, is not covered in the material we reviewed. Krebs also mentions a Synthient report on a pre-infected MECOOL-brand box, but the text available to us was cut off, so we do not describe its findings. Check the GTIG post and Synthient's report directly for model lists.
For a broader checklist on keeping small sites safe, see website security for small business.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
