<?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>Botnet &#8211; Gig City Geek</title>
	<atom:link href="https://gigcitygeek.com/tag/botnet/feed/" rel="self" type="application/rss+xml" />
	<link>https://gigcitygeek.com</link>
	<description>Gig powered, curiosity driven...</description>
	<lastBuildDate>Fri, 04 Sep 2026 03:09:42 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1</generator>

<image>
	<url>https://gigcitygeek.com/wp-content/uploads/2026/01/cropped-GigCityGeek_Logo-32x32.png</url>
	<title>Botnet &#8211; Gig City Geek</title>
	<link>https://gigcitygeek.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Home Lab Threats: Plex Security Vulnerability</title>
		<link>https://gigcitygeek.com/2026/09/03/plex-security-nightmare/</link>
					<comments>https://gigcitygeek.com/2026/09/03/plex-security-nightmare/#respond</comments>
		
		<dc:creator><![CDATA[Laronski]]></dc:creator>
		<pubDate>Fri, 04 Sep 2026 03:08:21 +0000</pubDate>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Botnet]]></category>
		<category><![CDATA[plex]]></category>
		<category><![CDATA[Scanning]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[server]]></category>
		<guid isPermaLink="false">https://gigcitygeek.com/?p=4741</guid>

					<description><![CDATA[A security breach on a Plex server can be devastating.  Automated scanning reveals malicious traffic – SSH, HTTP, and more. Leaving ports open is a huge risk.]]></description>
										<content:encoded><![CDATA[Back when running a home server meant setting up a dedicated box, mapping a port, and trusting that the software listening on the other end was built like a fortress. Browsing the forums today, I ran into a thread where someone’s security software started throwing fits over their Plex server. The logs showed incoming scanning traffic hitting their exposed port with everything from raw SSH strings to HTTP headers—and their antivirus flagging outbound connections to shady IPs. Half the comments were telling them their rig was infected with botnet malware, while the other half insisted it was just normal internet noise hitting an open port. Sitting at my desk looking over the log snippets, I’m telling you that, to say this: if you leave a service exposed to the open web without a buffer, you’re practically rolling out a welcome mat for trouble. What happens when you leave the front door unlocked When you open a port on your router so you can stream music or movies while traveling, you aren&#8217;t just opening it for yourself. Automated port scanners script their way through IPv4 ranges every single minute of the day. They hit your open port, try default credentials, throw malformed HTTP requests, and probe for known exploits. If your media server application handles those requests poorly or has a bug in its network stack, those probes can cause strange behavior or worse. And if you let a piece of media metadata point to a hijacked domain, your server will dutifully reach out to grab it, triggering every alarm on your desktop security software. We keep repeating the same mistake This isn&#8217;t a new problem. Cast your mind back to the early days of unpatched Windows XP connected straight to a broadband modem—it would get infected in under five minutes without the user touching a single button. We saw the same pattern with early FTP servers, home routers with remote management enabled, and exposed NAS devices that got hit with ransomware. The tech industry learned long ago that public-facing services need isolation, yet home server enthusiasts keep raw-dogging port forwards onto their local networks because it&#8217;s convenient.And look, I get the appeal of convenience. My wife just wants to open an app on her phone and have her media play without toggling three different overlay networks or logging into a perimeter gateway first. But convenience without isolation is a trap. Stop exposing raw ports to the open web If you insist on running self-hosted apps, stop forwarding raw ports on your home router. You don&#8217;t need to expose your server directly to the wild west of the public internet just to access your files on the go. Put your applications behind a secure mesh overlay like Tailscale, or run them inside sandboxed containers where a compromised application can&#8217;t touch the underlying host. When you containerize your setup, even if an app takes a bad request or tries to reach out to a dodgy IP, the blast radius is trapped inside an isolated environment.Exposing raw services to the public web is a habit from fifteen years ago that needs to die. The internet is far too noisy, and the automated scanners are far too fast. Do yourself a favor: close those open ports, throw your media stack inside a proper container, and secure your access route.]]></content:encoded>
					
					<wfw:commentRss>https://gigcitygeek.com/2026/09/03/plex-security-nightmare/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
