<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Botnet on HackingPassion.com : root@HackingPassion.com-[~]</title><link>https://hackingpassion.com/tags/botnet/</link><description>Recent content in Botnet on HackingPassion.com : root@HackingPassion.com-[~]</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 07 Jun 2026 13:36:33 +0200</lastBuildDate><atom:link href="https://hackingpassion.com/tags/botnet/index.xml" rel="self" type="application/rss+xml"/><item><title>Google Leaked the Chrome Bug That Turns Your Browser Into a Botnet</title><link>https://hackingpassion.com/chromium-background-fetch-botnet/</link><pubDate>Sun, 07 Jun 2026 13:36:33 +0200</pubDate><guid>https://hackingpassion.com/chromium-background-fetch-botnet/</guid><description>&lt;p>A single visit to one website can quietly turn your browser into part of a botnet, and the working code to do it is now still sitting out in the open.&lt;/p>
&lt;p>It affects Chrome, Microsoft Edge, Brave, Opera, Vivaldi, and almost every browser built on Chromium. Someone flagged it to Google back in 2022. Google sat on it for almost four years, and then leaked the exploit code itself, by accident, on its own bug tracker.&lt;/p></description></item><item><title>Your Home Devices Are Being Turned Into Proxies for the AI Industry</title><link>https://hackingpassion.com/home-proxy-network/</link><pubDate>Sat, 06 Jun 2026 16:51:31 +0200</pubDate><guid>https://hackingpassion.com/home-proxy-network/</guid><description>&lt;p>Your phone, your TV, your router, anything in your home with an internet connection can be put to work crawling the web for the AI industry, and nothing on the device says it is happening. Some of that traffic is harmless scraping. Some of it is not, and it leaves under your IP address either way, so it traces back to you. It&amp;rsquo;s called a &lt;strong>residential proxy&lt;/strong>.&lt;/p>
&lt;p>I came across it through the smart TV story this morning. Researchers had taken apart the software inside some free smart TV apps and found it quietly turns the television into a relay, using the home connection to pull web pages for a data company that resells that access to the AI industry. One question stuck with me. What if it does not stop at one device. So I went digging, and it does not stop there, not by a long way.&lt;/p></description></item><item><title>How Botnets Hide in Plain Sight: Tor, I2P, and the C2 Networks You Can't See</title><link>https://hackingpassion.com/botnets-tor-i2p-c2/</link><pubDate>Sun, 24 May 2026 11:30:46 +0200</pubDate><guid>https://hackingpassion.com/botnets-tor-i2p-c2/</guid><description>&lt;p>The command server is a botnet&amp;rsquo;s one real weak point. Take it down and the bots go quiet. Operators figured this out early and built their infrastructure to survive exactly that.&lt;/p>
&lt;p>This article covers how they do it. How botnets hide their command infrastructure inside Tor and I2P, how they scan for new victims without exposing themselves, and what to look for to detect it. Technical and step by step.&lt;/p></description></item><item><title>Kimwolf Botnet: 2 Million Android TV Boxes Hacked via Proxy App Vulnerability</title><link>https://hackingpassion.com/kimwolf-botnet-android-tv-boxes-proxy-exploit/</link><pubDate>Sun, 04 Jan 2026 15:28:00 +0100</pubDate><guid>https://hackingpassion.com/kimwolf-botnet-android-tv-boxes-proxy-exploit/</guid><description>&lt;p>A botnet just fired 1.7 billion DDoS commands in 72 hours. Attack capacity: nearly 30 Terabits per second. 2 million Android TV boxes sitting in living rooms across 222 countries and regions. And now we know how the attackers built it so fast. 🧐&lt;/p>
&lt;p>The attackers didn&amp;rsquo;t send phishing emails. They didn&amp;rsquo;t trick anyone into downloading malware. They just bought access to a proxy service and walked right into home networks.&lt;/p></description></item><item><title>RondoDox Botnet: 56 Exploits, Gaming Traffic Disguise, and Self-Defense Against Recovery</title><link>https://hackingpassion.com/rondodox-botnet-react2shell-exploit-shotgun/</link><pubDate>Thu, 01 Jan 2026 15:17:00 +0100</pubDate><guid>https://hackingpassion.com/rondodox-botnet-react2shell-exploit-shotgun/</guid><description>&lt;p>RondoDox added React2Shell to its arsenal. 90,000+ servers. 56 vulnerabilities. 30+ vendors. They call it the &amp;ldquo;exploit-shotgun&amp;rdquo; approach. Fire everything, see what hits. 😱&lt;/p>
&lt;p>Once inside, RondoDox doesn&amp;rsquo;t just sit there. It launches DDoS attacks. Mines Monero. Turns infected devices into proxies to hide other attacks. And it breaks the tools needed to fight back.&lt;/p>
&lt;p>The botnet has been running for 9 months. Three distinct phases. March to April 2025 was reconnaissance. April to June was daily probing of WordPress, Drupal, Struts2, and IoT devices. July onward became hourly automated attacks at scale.&lt;/p></description></item><item><title>Your Router Just Failed: ASUS &amp; TP-Link Critical Vulnerabilities (CVE-2025-59367)</title><link>https://hackingpassion.com/asus-tplink-authentication-bypass-cve-2025/</link><pubDate>Sun, 16 Nov 2025 13:11:54 +0100</pubDate><guid>https://hackingpassion.com/asus-tplink-authentication-bypass-cve-2025/</guid><description>&lt;p>Your router protects your home network from the internet. Or it&amp;rsquo;s supposed to. Two major vendors just proved it doesn&amp;rsquo;t. 😅&lt;/p>
&lt;p>ASUS: CVE-2025-59367 (CVSS 9.3)
TP-Link: CVE-2025-7850 + CVE-2025-7851 (CVSS 9.3 + 8.7)&lt;/p>
&lt;p>Both disclosed November 2025. Both critical. Both letting attackers walk right in.&lt;/p>
&lt;h2 id="asus-routers-no-password-required">ASUS routers: No password required.&lt;/h2>
&lt;p>The vulnerability affects ASUS DSL-AC51, DSL-N16, and DSL-AC750 routers. Authentication bypass.&lt;/p>
&lt;p>If your router&amp;rsquo;s management interface is exposed to the internet, an attacker can connect remotely without any credentials. No username. No password. Direct admin access.&lt;/p></description></item></channel></rss>