Plex2Shell vulnerability chain exploited for miners and backdoors
Attackers are actively exploiting the Plex2Shell vulnerability chain in Plex Media Server to deploy cryptocurrency miners and Linux backdoors, starting a day after public proof-of-concept release.

Threat actors began exploiting the Plex2Shell vulnerability chain a day after its proof-of-concept was made public on October 16, 2026. The chain of four flaws enables unauthenticated remote code execution on exposed Plex Media Server instances, allowing attackers to run arbitrary code with the same privileges as the Plex service.
The Plex2Shell chain consists of four CVEs affecting Plex Media Server, disclosed in July and patched in early August 2026. Security researcher Zach Main reported the vulnerabilities to Plex on July 27, 2026. Plex confirmed the issues, awarded a bug bounty on August 4, and had already shipped fixes in version 1.43.3.10861 released on August 3. On September 1, Plex advised all server owners to install the newest release without delay. The four vulnerabilities can be chained to achieve unauthenticated remote code execution.
| CVE Identifier | CVSS Score | Description |
|---|---|---|
| CVE-2026-96652 | 5.3 | Unauthenticated SSRF via the '/player/timeline' endpoint due to unvalidated 'protocol' parameter. |
| CVE-2026-96654 | 6.9 | Improper neutralization of URL values in the 'searchOne' endpoint allowing theft of admin token. |
| CVE-2026-96655 | 5.3 | SSRF allowing authenticated users to request arbitrary addresses via '/video/:/transcode/universal' path parameter. |
| CVE-2026-96656 | 8.6 | Allows external control of file name or path to execute attacker-chosen ELF in the Codecs directory. |
Exploitation observed in the wild
After the proof-of-concept was released on October 16, 2026, attackers began exploiting the chain to deploy miner and proxy payloads. In-the-wild exploitation attempts were recorded on October 17. A researcher monitoring an internet-facing Plex honeypot running a vulnerable release caught the attacks. The attackers used the publicly released exploit, though they may have tweaked the code.
The attacks deployed a miner payload from the remote server 217.60.194[.]116. The XMRig miner process 'mylovelyminer' was deployed, pointing to mining server ota.proxystream[.]st. Later that day, a second program called 'myawesomeproxy' also appeared on the honeypot. This artifact was identified by VirusTotal as a stealthy Linux backdoor and reverse proxy. Running 'myawesomeproxy' displays a specific message. boredhackerblog said: "Running this software on any of your devices makes you agree to the potential external use of your internet traffic."
Observed attacker IP addresses include 91.92.40[.]202, 176.65.139[.]228, and 45.194.92[.]222. The subdomain global.relay.proxystream[.]st was flagged by Bitsight in August 2026 in connection with the AISURU DDoS and proxyware botnet. The researcher cautioned that the published indicators of compromise cover only activity seen on the honeypot.
Related activity and uncertainty
Reports of miner infections on Reddit and prior Plex advisories raise questions about the scope and timing of the threat. Reddit posts indicate multiple Plex users had instances compromised with 'mylovelyminer' payload, though it is not confirmed if this stems from Plex2Shell exploitation. Plex previously urged users to update after an update addressing unspecified security flaws, more than a month before the Plex2Shell exploitation was observed. It is unclear if the Plex2Shell vulnerabilities were part of that prior security update.
Users are advised to keep Plex installations up-to-date for optimal protection in light of active exploitation.





