<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>IOT Security &#8211; First Hackers News</title>
	<atom:link href="https://firsthackersnews.com/category/iot-security/feed/" rel="self" type="application/rss+xml" />
	<link>https://firsthackersnews.com</link>
	<description>Latest cybersecurity news, real attacks, and practical IOCs—made simple and actionable.</description>
	<lastBuildDate>Tue, 03 Nov 2026 06:08:29 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.9</generator>

<image>
	<url>https://firsthackersnews.com/wp-content/uploads/2026/03/cropped-FHN_512x512-32x32.png</url>
	<title>IOT Security &#8211; First Hackers News</title>
	<link>https://firsthackersnews.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Google Disrupts Android Botnet Infecting 1.3 Million Devices</title>
		<link>https://firsthackersnews.com/google-disrupts-android-botnet-infecting-1-3-million-devices/</link>
					<comments>https://firsthackersnews.com/google-disrupts-android-botnet-infecting-1-3-million-devices/#respond</comments>
		
		<dc:creator><![CDATA[FHN]]></dc:creator>
		<pubDate>Tue, 03 Nov 2026 06:08:27 +0000</pubDate>
				<category><![CDATA[Cybersecurity]]></category>
		<category><![CDATA[IOT Security]]></category>
		<category><![CDATA[Malware]]></category>
		<category><![CDATA[Network Security]]></category>
		<category><![CDATA[Threat Intelligence]]></category>
		<category><![CDATA[#Cybercrime]]></category>
		<category><![CDATA[#DeviceSecurity]]></category>
		<category><![CDATA[#FirmwareSecurity]]></category>
		<category><![CDATA[#IoTSecurity]]></category>
		<category><![CDATA[#ThreatIntelligence]]></category>
		<category><![CDATA[AndroidBotnet]]></category>
		<guid isPermaLink="false">https://firsthackersnews.com/?p=12671</guid>

					<description><![CDATA[<p>Google and its cybersecurity partners have disrupted a massive Android botnet involving more than 1.3 million devices, primarily</p>
<p>The post <a rel="nofollow" href="https://firsthackersnews.com/google-disrupts-android-botnet-infecting-1-3-million-devices/">Google Disrupts Android Botnet Infecting 1.3 Million Devices</a> appeared first on <a rel="nofollow" href="https://firsthackersnews.com">First Hackers News</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p>Google and its cybersecurity partners have disrupted a massive <strong>Android botnet</strong> involving more than 1.3 million devices, primarily Android TV set-top boxes. The investigation revealed that Chinese device manufacturer Videostrong allegedly embedded a backdoor into multiple device models and sold access to cybercriminals.</p>



<p>The operation, announced on November 2, 2026, targeted the XCPE botnet, which allowed attackers to remotely control infected devices and use them for various criminal activities.</p>



<h2 class="wp-block-heading"><strong>How the XCPE Botnet Worked</strong></h2>



<p>The x.cpe backdoor operated as a system application with elevated privileges, allowing attackers to remotely control infected devices.</p>



<p>Through the malware, operators could:</p>



<ul class="wp-block-list">
<li>Install applications without users&#8217; knowledge.</li>



<li>Disable Google Play Protect.</li>



<li>Execute remote commands and capture screenshots.</li>



<li>Collect account details, device information and system logs.</li>



<li>Turn infected devices into residential proxies.</li>



<li>Generate fraudulent advertising traffic.</li>
</ul>



<p>Although most affected devices were Android TV boxes, the backdoor was also identified in telehealth equipment, karaoke machines and digital signage devices.</p>



<h2 class="wp-block-heading"><strong>Google Takes Action Against Videostrong</strong></h2>



<p>Google used legal action to shut down domains and servers responsible for controlling the XCPE botnet and distributing additional malware modules.</p>



<p>The operation involved Japan&#8217;s National Police Agency and cybersecurity organizations including Lumen, HUMAN Security, Plume, Synthient and TrendAI.</p>



<p>Google also banned Videostrong and its future subsidiaries or affiliates from manufacturing certified Android devices or supplying software to other certified manufacturers.</p>



<p>The disruption is expected to cut off criminal access to at least 10 million additional compromised devices associated with other malware families.</p>



<h2 class="wp-block-heading"><strong>Infected Devices Remain at Risk</strong></h2>



<p>The backdoor is embedded in device firmware and can reinstall itself after a restart. Consequently, simply deleting the malicious application may not permanently remove the infection.</p>



<p>Synthient has published a list of 182 device model names identified during its investigation, although a model appearing on the list does not automatically confirm infection.</p>



<p>Organizations are advised to identify potentially affected devices, block associated malicious infrastructure and isolate unmanaged smart devices from sensitive corporate networks.</p>



<p>Google has also modified its Android device certification review process to strengthen firmware security checks and prevent similar techniques from bypassing testing.</p>
<p>The post <a rel="nofollow" href="https://firsthackersnews.com/google-disrupts-android-botnet-infecting-1-3-million-devices/">Google Disrupts Android Botnet Infecting 1.3 Million Devices</a> appeared first on <a rel="nofollow" href="https://firsthackersnews.com">First Hackers News</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://firsthackersnews.com/google-disrupts-android-botnet-infecting-1-3-million-devices/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
