A Security Incident That May Involve Your Plex Account Information
Posted4 months agoActive4 months ago
forums.plex.tvTechstory
skepticalnegative
Debate
60/100
PlexSecurity IncidentData BreachPassword Management
Key topics
Plex
Security Incident
Data Breach
Password Management
Plex users are notified of a security incident potentially involving their account information, sparking concerns about password management and the company's transparency.
Snapshot generated from the HN discussion
Discussion Activity
Very active discussionFirst comment
3m
Peak period
23
0-2h
Avg / period
4.1
Comment distribution33 data points
Loading chart...
Based on 33 loaded comments
Key moments
- 01Story posted
Sep 10, 2025 at 3:00 AM EDT
4 months ago
Step 01 - 02First comment
Sep 10, 2025 at 3:02 AM EDT
3m after posting
Step 02 - 03Peak activity
23 comments in 0-2h
Hottest window of the conversation
Step 03 - 04Latest activity
Sep 10, 2025 at 9:25 PM EDT
4 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45194218Type: storyLast synced: 11/20/2025, 1:42:01 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
I’m getting increasingly frustrated at just how badly Plex behaves for home set ups. Which is the entire point of installing something like Plex.
Most annoying still, I’ve even paid for their premium products in the hope that it would make things behave better and it did not.
The only reason these security incidents happen is because Plex try to extort home users. There isn’t any other compelling reason to have your details on their database with credentials to active installs.
Thanks to the centralized Plex account, we can share our libraries with each other in a few clicks.
You can do the same if you don't have a server also, basically being a member of various Plex server and accessing everything through a single account and interface.
Sure, requiring an account if all you want to do is being the single user accessing your own instance is useless, and if it's your usecase, then Plex is not the right tool for you.
I tried Plex, Emby and Jellyfin, but I staid with Plex because of this easy sharing feature.
I use Emby, only because a few friends did and recommended it. I'd probably switch ti something more secure and/or open source given the right push.
I've been very happy with Jellyfin FWIW :)
> Even though all account passwords that could have been accessed were hashed (with bcrypt plus salted and peppered) and secured in accordance with best practices, out of an abundance of caution we are requiring all Plex accounts to have their password reset.
Whether that later changed for the worse is anyone's guess.
Unfortunately, Plex is a bit of a mess these days - constantly pushing Live TV on us, requiring internet access to access local media (this is a killer whenever internet goes down), overly complex, clunky remote access (altho this is much better these days). But it still isn't bad enough to make me try and migrate. I love my local setup (Sonarr and a custom app for movies as Radarr is OTT for the amount of movies we watch) and Plex is very polished (compared to the alternatives) but I do wonder how much longer it will be around.
Easy way for me to turn my brain off and find a good documentary/educational show at the end of the day
Good news! You can whitelist exceptions by IP/subnet
Go into Plex Settings, then Settings > Network (show advanced). Scroll down to "List of IP addresses and networks that are allowed without auth"
"Comma separated list of IP addresses or IP/netmask entries for networks that are allowed to access Plex Media Server without logging in. When the server is signed out and this value is set, only localhost and addresses on this list will be allowed."
Put your local subnet and netmask into that (e.g. "192.168.1.1/255.255.255.0") and you should be all good
FYI, I also have "Secure Connections" set to "Preferred", but I don't know if that makes a difference for this or not
So you'll have to get a new claim from https://www.plex.tv/claim and set it on your server; through the PLEX_CLAIM env var if your setup involves Docker.
They talk vaguely about it under _Common Issues_ but it wasn't on the original email, so I lost 15 minutes of my day because of this...
Another option is to do `ssh -L 32400:localhost:32400 <your-plex-address>` and connect to http://localhost:32400/web, it will let you claim the server as it detects the connection being local.
I roughly recall Plex is somewhat involved in the compromise. One of the Lastpass employees compromised via Plex that leads to Lastpass data breach if I'm not mistaken.
Vault is more or less Old Testament, though, so if you're serious about zero trust, Zanzibar paper is a must-read!
Relationships lend nicely to AI agent stuff, where RBAC is putting you at a disadvantage. It's hard to express both direct and indirect access patterns in RBAC. For example, whenever agents would act on your, or your user's behalf within a clearly-defined scope (sic!) This is where traditional RBAC breaks down, whilst ReBAC really shines for expressing relationships between user/agent/system identities, thus greatly simplifying checking, scoping, audit.
[1]: https://developer.hashicorp.com/vault
[2]: https://openbao.org/
[3]: https://www.ory.sh/keto
[4]: https://research.google/pubs/zanzibar-googles-consistent-glo...
[5]: https://edgebit.io/enclaver/docs/0.x/guide-vault/
https://news.ycombinator.com/item?id=45174684
(Or at least related, this submission has the plex.tv website breach notification, not just the text of the email.)