{"id":942,"date":"2026-11-05T08:28:45","date_gmt":"2026-11-05T08:28:45","guid":{"rendered":"https:\/\/managedt.com\/blog\/shutting-the-door-on-the-xcpe-botnet\/"},"modified":"2026-11-05T08:28:46","modified_gmt":"2026-11-05T08:28:46","slug":"shutting-the-door-on-the-xcpe-botnet","status":"publish","type":"post","link":"https:\/\/managedt.com\/blog\/shutting-the-door-on-the-xcpe-botnet\/","title":{"rendered":"Shutting the Door on the XCPE Botnet"},"content":{"rendered":"<div class=\"post-updated\"><em>Updated November 5, 2026 at 3:28 AM ET<\/em><\/div>\n<p>Google and industry partners dismantled the XCPE backdoor and botnet, giving small-business IT teams a chance to review set-top boxes and other Android devices for signs of compromise. The campaign enrolled more than 1.3 million set-top boxes and was tied to ad fraud, residential proxy networks, data theft, remote commands and other malicious activity.<\/p>\n<h2>What Happened<\/h2>\n<p>According to <a href=\"https:\/\/cloud.google.com\/blog\/topics\/threat-intelligence\/shutting-the-door-on-the-xcpe-botnet\/\" target=\"_blank\" rel=\"noopener\">Google Threat Intelligence<\/a>, Google and industry partners dismantled the XCPE backdoor and botnet, which had enrolled more than 1.3 million set-top boxes. Google assesses with high confidence that Videostrong Technology Co. intentionally developed, deployed and operated the backdoor for financial gain, selling access to criminal affiliates that loaded malware modules onto infected devices.<\/p>\n<p>Google said the modules conducted ad fraud, enrolled devices into residential proxy networks and installed additional malware. The disruption also targeted command-and-control domains used by more than a dozen malware families, which Google assessed could sever access to at least 10 million additional compromised devices.<\/p>\n<h2>Are You Affected?<\/h2>\n<p>The compromise affected Android set-top boxes and related devices with malicious software built into the firmware. Google identified preinstalled packages named <code>x.cpe<\/code> or <code>com.oemservice<\/code>, with some builds also containing <code>com.abc.nexus<\/code> or newer droppers.<\/p>\n<p>Google has not published a complete list of affected models and brands, so businesses cannot determine exposure from the model list alone. An IT team can check managed Android TV devices for the package names, unexpected system applications, Google Play Protect verification changes, unexplained installs, residential proxy traffic, screen-capture activity or signs of unauthorized shell commands. The source describes a system preload that can reinstall itself after removal and a bypass that disables Play Protect app verification.<\/p>\n<p>Devices connected through the compromised set-top boxes or other affected Android equipment may also warrant review. The activity included account information, device information, package inventories, system logs, live screenshots and injected keystrokes.<\/p>\n<h2>What to Do Now<\/h2>\n<ol>\n<li><strong>Inventory every Android TV device and set-top box.<\/strong> Record the model, firmware version, owner, location and network connection, and include devices used for reception, streaming, conferencing or employee access.<\/li>\n<li><strong>Check for the identified packages.<\/strong> Have IT personnel look for <code>x.cpe<\/code>, <code>com.oemservice<\/code> and <code>com.abc.nexus<\/code>, along with unfamiliar system applications, newly installed APKs or security settings that have been changed without approval.<\/li>\n<li><strong>Separate affected equipment from business systems.<\/strong> Place suspected devices on an isolated network segment until they are reviewed. Examine DNS logs, proxy logs, firewall records and outbound traffic for unexpected connections, unusual traffic volume or access to command-and-control domains associated with the campaign.<\/li>\n<li><strong>Reset or replace confirmed compromised devices.<\/strong> A normal application uninstall may not remove the system preload because it can return after reboot. Follow the device maker&#8217;s remediation process, factory reset where appropriate and reimage the device before returning it to service.<\/li>\n<li><strong>Review accounts and business data exposed through connected devices.<\/strong> Change affected credentials, review recent account activity and examine logs for unauthorized installations, screenshots, data transfers, reverse shells or other commands.<\/li>\n<\/ol>\n<h2>How the XCPE Botnet Worked<\/h2>\n<p>Videostrong developed the malware in at least three stages. The primary backdoor ran with the <code>android.uid.system<\/code> privilege and communicated with command-and-control infrastructure. A separate loader and execution engine received instructions through inter-process communication and initialized the monetization modules.<\/p>\n<p>The modules could turn infected devices into residential proxy exit nodes, run ad-fraud engines, install other backdoors and load more malicious software. Identified examples included Linkfog, AppSalt, NetNut, CBOXTV, HiddenView, Moyu and Spirit. The source also lists TitanService, BwmService, AdtimeService, lb102Service and LinkfogService, also known as AgentService, among common modules.<\/p>\n<h2>What Could the Botnet Do?<\/h2>\n<p>After retrieving configuration data over HTTP, affected devices opened a persistent MQTT connection to receive instructions. The capabilities included silently installing remote APKs, disabling Google Play Protect app verification, running shell commands and scripts, capturing screens, injecting keystrokes and performing network reconnaissance.<\/p>\n<p>Google said operators could collect account information, device details, installed package inventories and system logs. They could also establish reverse shells and send captured screenshots to the command-and-control system. These capabilities give attackers a potential path from an infected set-top box into any business credentials or services accessed through that device.<\/p>\n<h2>Why Does This Matter for Small Businesses?<\/h2>\n<p>A managed set-top box can become a persistent entry point into the network used for staff, reception systems or shared displays. Because the malware runs with system privileges and can restore itself after uninstallation, ordinary application removal is not enough.<\/p>\n<p>Small-business IT teams should include these devices in asset inventories, firmware review, network monitoring and incident response. Any suspected device should be treated as a privileged endpoint rather than a simple television accessory.<\/p>\n<h2>What Changed After the XCPE Disruption?<\/h2>\n<p>Google said it took legal action to remove domains and servers used to control the botnet and install malware modules. It also banned Videostrong and any future subsidiaries or affiliates from building and selling certified Android devices or supplying software to certified vendors.<\/p>\n<p>Google has also changed its review process for certified Android TV devices and implemented improvements intended to verify firmware integrity. The company said Videostrong used obfuscation to load malicious code after a device&#8217;s first boot, taking advantage of a gap in the review process.<\/p>\n<h2>FAQ<\/h2>\n<h3>What Is the XCPE Botnet?<\/h3>\n<p>XCPE is a backdoor and botnet that Google says was built into many device models and brands over several years. It enrolled more than 1.3 million set-top boxes and provided infrastructure for ad fraud, residential proxy activity and additional malware.<\/p>\n<h3>Which Devices Are Affected by XCPE?<\/h3>\n<p>The affected equipment includes Android set-top boxes and related devices containing preloaded XCPE malware. Google has not published a complete list of affected models and brands. Package names, device behavior and network activity can help an IT team identify suspected systems.<\/p>\n<h3>Can XCPE Be Removed by Uninstalling the App?<\/h3>\n<p>Not reliably. The source says the backdoor is preloaded in firmware, can run with system-level privileges and automatically reinstalls from the <code>\/oem\/<\/code> partition after a reboot. Confirmed compromised devices should follow the maker&#8217;s remediation process or be replaced.<\/p>\n<p><script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"FAQPage\",\"mainEntity\":[{\"@type\":\"Question\",\"name\":\"What Is the XCPE Botnet?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"XCPE is a backdoor and botnet that Google says was built into many device models and brands over several years. It enrolled more than 1.3 million set-top boxes and provided infrastructure for ad fraud, residential proxy activity and additional malware.\"}},{\"@type\":\"Question\",\"name\":\"Which Devices Are Affected by XCPE?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"The affected equipment includes Android set-top boxes and related devices containing preloaded XCPE malware. Google has not published a complete list of affected models and brands. Package names, device behavior and network activity can help an IT team identify suspected systems.\"}},{\"@type\":\"Question\",\"name\":\"Can XCPE Be Removed by Uninstalling the App?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Not reliably. The source says the backdoor is preloaded in firmware, can run with system-level privileges and automatically reinstalls from the \/oem\/ partition after a reboot. Confirmed compromised devices should follow the maker's remediation process or be replaced.\"}}]}]}<\/script><\/p>\n<div class=\"source-disclaimer\"><em>This article reports on publicly available information from the sources listed below. We have no reason to believe it is inaccurate, but we have not independently verified every claim, and details may change as the story develops.<\/em><\/div>\n<section class=\"post-sources\">\n<h2>Sources<\/h2>\n<ul>\n<li><a href=\"https:\/\/cloud.google.com\/blog\/topics\/threat-intelligence\/shutting-the-door-on-the-xcpe-botnet\/\" target=\"_blank\" rel=\"noopener nofollow\">cloud.google.com<\/a><\/li>\n<li><a href=\"https:\/\/github.com\/GoogleCloudPlatform\/professional-services\" target=\"_blank\" rel=\"noopener nofollow\">github.com<\/a><\/li>\n<li><a href=\"https:\/\/blog.google\/security\/\" target=\"_blank\" rel=\"noopener nofollow\">blog.google<\/a><\/li>\n<li><a href=\"https:\/\/www.adobe.com\/trust\/security\/bulletins-and-advisories.html\" target=\"_blank\" rel=\"noopener nofollow\">adobe.com<\/a><\/li>\n<\/ul>\n<\/section>\n","protected":false},"excerpt":{"rendered":"<p>Google and industry partners disrupted the XCPE botnet after it enrolled more than 1.3 million set-top boxes for ad fraud and proxy activity.<\/p>\n","protected":false},"author":3,"featured_media":941,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-942","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/posts\/942","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/comments?post=942"}],"version-history":[{"count":1,"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/posts\/942\/revisions"}],"predecessor-version":[{"id":943,"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/posts\/942\/revisions\/943"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/media\/941"}],"wp:attachment":[{"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/media?parent=942"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/categories?post=942"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/managedt.com\/blog\/wp-json\/wp\/v2\/tags?post=942"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}