Threat Pulse: 71st Edition

Now Playing Plex2Shell

1. Exploitation Plex Media Server 1.43.3.10828 exposed to suspected Plex2Shell activity
2. Execution Plex Media Scanner launches repeated PowerShell processes
3. Discovery PowerShell collects host, domain, membership, and role information
4. SOC Stop Blackpoint isolates the affected device
5. Threat Potential persistence, lateral movement, and payload deployment

What We’re Seeing

  • The Blackpoint SOC alerted to suspicious PowerShell activity on a host, spawned directly by a Plex Media Server installation.
  • PowerShell collected the computer name, domain name, domain membership status, and domain role. It then attempted to send that information by HTTP POST to an external IP address flagged as malicious.
  • The server was running Plex Media Server 1.43.3.10828, a version vulnerable to the Plex2Shell exploit chain, which allows unauthenticated remote code execution.
  • The same command fired repeatedly, with dozens of PowerShell processes launched by the Plex Media Scanner process within seconds of each other, suggesting that code was planted in the Plex process’s execution path.

What the Blackpoint SOC Did

  • The Blackpoint SOC isolated the affected host and confirmed there were no signs of lateral movement.
  • Analysts reviewed process and network telemetry, identified the malicious outbound destination, and tied the activity to the vulnerable Plex version.
  • The SOC contacted the customer and provided remediation guidance, including rebuilding the host, patching Plex to the latest version, and inspecting the Plex Codecs directory and Preferences.xml for signs relevant to the published exploit chain.

Why This Matters

  • The chain does not require credentials or user interaction. It reaches code execution by stealing an admin token, forcing the server to fetch attacker-controlled content, and writing a malicious library into the Plex Codecs directory.
  • Reported payloads from the wider campaign include cryptocurrency miners and proxy malware that allow attackers to route traffic through the victim’s network, hiding their own infrastructure and potentially extending access into the business network.

What Blackpoint Is Doing

Blackpoint Cyber has detections in place for the behaviors observed in this attack chain, including a trusted application such as Plex launching PowerShell and sending host and domain details to an external address.

The SOC acted on this activity without waiting for a second confirmed second-stage payload, limiting the attacker’s opportunity to establish persistence or move laterally.

The Blackpoint SOC provides 24/7 monitoring and response, while the Adversary Pursuit Group tracks changes in adversary behavior, campaigns, and vulnerabilities to provide intelligence that supports detection, investigation, and response.

Together, these capabilities help identify and respond to malicious activity before it can escalate into broader operational or business impact.

Recommendations

  • Patch Plex Media Server to 1.43.3.10861 or later. Inventory Plex deployments across servers, NAS devices, VMs, and user workstations and verify the version directly. Plex confirms that versions before 1.43.3.10861 are affected by the Plex2Shell chain.
  • Remove internet exposure. Disable Plex Remote Access and port forwarding of TCP 32400 on business networks where remote access is not required.
  • Investigate before assuming a patch is enough. On any server that was exposed while vulnerable, inspect the Plex Codecs directory for unauthorized libraries, review Preferences.xml for unexpected transcoder settings, and look for miner or proxy processes and unusual outbound connections.

See Plex’s current security guidance for additional investigation and recovery recommendations.

BROC Weekly Snapshot

What changed. What didn’t. What matters.

Incidents Observed >80 ↓
Pre-Payload Disruptions 88%
Pre-Ransom Interruptions N/A

Campaign Statuses

Campaign Trend Status Share
Rogue RMM – Ongoing 31%
Fake CAPTCHA / ClickFix ↓ Ongoing 15%
SSL VPN Compromise ↓ Ongoing 2%
Trojanized Installers ↓ Ongoing 1%

In Case You Missed It

The Blackpoint APG sent a threat notice this week to raise awareness of a password authentication bypass affecting OpenSSH on musl-based Linux systems, particularly Alpine Linux.

OpenSSH | CVE-2026-123158 | Password Authentication Bypass

  • Potential action: An attacker with network access to the SSH port may be able to log in as an account with no password configured by submitting a password between 257 and 1,024 bytes.
  • Official Alpine Linux tiny-cloud images can include an alpine user with this account configuration and passwordless doas access, providing a potential path to root once the other exposure conditions are met.

Alpine Linux recommends updating OpenSSH and restarting sshd. If an immediate update is not possible, disabling password authentication and restarting sshd closes the vulnerable path.

Note: The November 5 threat notice initially listed this issue without a CVE because one had not yet been assigned. As of November 9, it is tracked as CVE-2026-123158.

DATE PUBLISHEDNovember 10, 2026
AUTHORBlackpoint Cyber

The Cost of Waiting

The Cost of Waiting: What Identity Attacks Cost the MSP ebook What Identity Attacks Cost the MSP Stolen credentials don't trip alarms. Once an attacker is authenticated, they look like anyone else, and most tools aren't watching what happens next. Learn what closing the identity response gap looks like: how identity attacks happen, where response slows down, and the questions to ask any ITDR vendor.
*Identity-based techniques play a role in nearly 90% of incident investigations

GET YOUR COPY