PokerStars has been named in a malware attack affecting 178 organisations, according to security researcher Report URI. For players, the immediate question is whether their bankroll was exposed. The published evidence concerns website scripts, and does not establish that the poker client was compromised or that PokerStars customers lost money.

The incident comes shortly after the separate GGPoker breach involving player aliases and cashier balances. Putting both under the heading “poker sites hacked” misses the detail players need before deciding what to do next.
What happened in the PokerStars malware incident?
Report URI’s Scott Helme identified 188 infected Optimizely scripts across 178 organisations on 16 November. His list includes PokerStars’ .com, .de, .fr and .pt websites, alongside gambling brands Betsson, tombola and Betfred.
Optimizely supplies tools for testing website variations. Its 17 November incident report says attackers exploited a signup flaw to impersonate administrator users and insert code into customer projects. That code then ran in visitors’ browsers.
“This was not a credentials breach,” Optimizely said. That statement concerns access to its platform; it is not a blanket assurance about every visitor’s information.
What is confirmed, and what is still missing?
| Question | What the evidence establishes |
|---|---|
| Why is PokerStars named? | Report URI lists its web properties among affected organisations. |
| Was the poker client compromised? | The material reviewed does not establish that. |
| Did PokerStars players lose money? | No PokerStars-specific loss figure was found in the sources reviewed. |
| Has Optimizely contained the incident? | The company says it closed the flaw at 16:10 UTC and removed injected code by 22:24 UTC on 16 November. |
| Was every visitor affected equally? | Optimizely says exposure depended on the affected pages and their security protections. |
A domain appearing on a list is a reason to investigate. It does not tell an individual player which page they loaded, whether the malicious code executed or whether any information left their browser.
Equally, removing the code does not answer every question about earlier visits. Players need the operator’s assessment of their particular exposure, rather than having to piece together a hand history from several different reports.
What was the malware trying to steal?
Helme describes code capable of changing cryptocurrency addresses, capturing card details, collecting readable cookies and screenshots, and targeting Apple mobile devices. His warning is straightforward: “trusted JavaScript doesn’t always remain trustworthy.”
Optimizely says card details entered directly into affected pages were at risk, while hosted payment iframes were outside the recovered script’s reach. That is a technical distinction, not something a player should be expected to identify from a familiar-looking cashier screen.
This is also a different allegation from the superuser malware investigation involving exposed hole cards. Nothing reviewed here establishes that someone could see PokerStars players’ hands, influence the deal or access the game servers.
What should players check?
Start with what you actually did on 16 November. A browser visit, a card payment and a session played through downloaded software are different activities; give support those details instead of asking only whether your account is “safe”.
- Check your records. Review account transactions and card statements for activity you do not recognise. Keep the date, amount and transaction reference for anything questionable.
- Contact support through a route you already trust. Ask whether the specific website and pages you used were affected, and whether any action is required on your account.
- Keep devices and browsers updated. Use their built-in update settings. Do not install a supposed security fix sent by an unfamiliar account or unsolicited message.
- Preserve evidence. Save relevant messages and transaction details. Do not send passwords, authentication codes or full card details to someone claiming to investigate.
These are precautionary checks, not a finding that your money has gone missing. If an unfamiliar transaction appears, report that specific transaction promptly to the relevant operator or payment provider.
The answers PokerStars players still need
The useful follow-up is an operator-specific account of affected pages, exposure times and customer impact. Did any cashier pages load the script? Were logged-in sessions involved? Will affected visitors receive individual notices?
Players have already seen restrictions on third-party poker tools introduced in the name of security. This incident raises a related question for operators: what checks cover the outside services their own websites load?
You can choose your games carefully and manage your bankroll properly, yet still depend on systems you cannot inspect. Players deserve a clear account of that risk, with confirmed facts separated from possibilities.
Reporting checked on 19 November 2026 against Report URI’s investigation and Optimizely’s incident report and public status updates. No PokerStars-specific public response or confirmed player-loss total was located during this review.