Attackers are breaking into Plex servers that were never updated and using them to mine cryptocurrency.

The fix is simple: update Plex Media Server to version 1.43.3 or newer.
If your server has been running slow, hot and loud lately, read on - it may already be working for someone else.
Here is what is going on, how to check your own server, and what to do if it looks infected.
What Happened
A security researcher found four bugs in Plex Media Server that can be chained together, nicknamed "Plex2Shell". Used together, they let an attacker on the internet run their own code on your server without a password.
Plex fixed them in version 1.43.3 and asked everyone to update in early September. The full technical details went public on 16 October, and attacks started the next day, The Hacker News reports.
Attackers are installing two things on servers they break into:
- A cryptominer. It uses your processor to earn cryptocurrency for someone else, which is why the machine runs hot.
- Proxy software. It quietly rents out your internet connection to strangers.
Who is at risk:
Any Plex Media Server on version 1.43.2 or older that can be reached from the internet - which is the case if you use Plex's Remote Access to watch away from home. The attacks seen so far hit Linux and Docker servers, but Plex's warning covers every server, so Windows and NAS owners should update too.
Signs Your Plex Server Is Infected
A miner wants as much processing power as it can get, so it is rarely subtle. Watch for:
- High CPU use when nobody is watching. Your fans spin up and the machine stays warm with nothing playing.
- A slow server. Streams buffer or transcoding struggles on hardware that used to cope fine.
- Strange processes. Users have reported names like mylovelyminer and myawesomeproxy.
On Windows, press Ctrl + Shift + Esc to open Task Manager and sort by CPU. Anything you do not recognise near the top, while Plex is idle, is worth a closer look.
How to Check Your Plex Version and Update
- Check your version. Open Plex in your browser, go to Settings and look under General for your server - the version number is shown there.
- Update if it is older than 1.43.3. On Windows, right-click the Plex icon in the taskbar tray and check for updates, or grab the installer from the official Plex downloads page.
- On a NAS or in Docker, update by hand. NAS app stores can lag behind, and a Docker container keeps its old version until you pull the new image and recreate it.
- Turn off Remote Access if you do not need it. It is under Settings, Remote Access - a server that is not open to the internet cannot be reached by these attacks.
If Your Server Looks Infected
Updating closes the door, but it does not remove anything already inside. The attack plants its file in Plex's Codecs folder, so stopping the miner process alone may not be enough.
- Update first, then delete the Codecs folder. On Windows it is at %LOCALAPPDATA%\Plex Media Server\Codecs by default - Plex downloads fresh codecs on its own.
- Change your Plex password. Then use "sign out of all devices" in your Plex account settings.
- Scan the whole machine. Run a full Microsoft Defender scan on Windows.
- When in doubt, rebuild. A clean reinstall, or a fresh Docker container, is the only way to be completely sure.
Only download Plex from plex.tv.
News like this brings out fake "Plex security fix" downloads. Our guide on how to tell if a download is safe shows the warning signs.
Thinking About Leaving Plex?
If this is the push you needed, Jellyfin Server is free and open source, and Emby works much like Plex. Just remember that any media server you open to the internet needs the same care - keep it updated.
And if you only watch on one PC or TV box, you may not need a server at all. VLC media player and Kodi play your files directly, with nothing exposed to the internet.
Quick questions
Which Plex versions are affected by Plex2Shell?
Plex Media Server 1.43.2 and older. Version 1.43.3 and newer are fixed, and Plex Desktop users should be on 1.115.0 or newer.
Is Plex on Windows affected?
The attacks confirmed so far hit Linux and Docker servers. Plex's security warning covers every server, though, so update a Windows install too.
Why is my Plex server using so much CPU?
Transcoding a video can use a lot of CPU, which is normal. High CPU use when nothing is playing, together with unfamiliar processes, is a sign of a miner.
Does turning off Remote Access protect me?
It lowers the risk a lot, because these attacks come in from the internet. It is not a substitute for updating.
Is my Plex account hacked too?
The attack targets the server, not your account. Changing your password and signing out of all devices is still a sensible step if your server was infected.
Update to Plex Media Server 1.43.3 or newer today, and your server works for you again.
Ready for a change? Try Jellyfin Server, or tell us whether your server was hit.
Latest news comments
AllThe Vega OS shift is the biggest Firestick story of 2026. Anyone buying now needs to know: 4K Max = sideloading works, plain 4K = ...
News: The New Fire TV Stick 4K Can't Run Kodi - Here's Which Fire Stick Still Can 3 commentsBrave just enabled it by default for stable users yesterday (1.97). Not specified is chromeOS will be passively gaining decode capability too, and ...
News: JPEG XL Is Back in Chrome: What It Means and How to Open JXL Files 2 commentsI didn't know it was EU, AND france. That doesn't sound like a good idea. Related to coding or privacy.
News: Meet Qwant: The Private, EU-Built Alternative to Google 1 comment