Cases › security breach › LR-2026-0301
Claude agent detects MeshAgent screen-capture malware on high-stakes poker player's machine
Preliminary Why: 1 report: Risky Business · subject to change · 1 independent report
Severity moderate: a stated loss of around $30,000 falls in the 10k-100k USD band.
Happened 2026-09-25 · Earliest source we hold 2026-10-29, 34 days later · Captured by AI Risk Wire 2026-11-01 00:47 UTC
On September 25, 2026, professional online poker player Alex was using his Claude AI agent to review play statistics when his SQL database crashed and needed to be reset. The Claude agent noticed a program called MeshAgent running in the background, apparently able to capture his screen and control his machine. The agent reported that the program had been installed on April 24, not by Alex, and identified 11 time-stamped screen-capture events, all during sessions on Americas Cardroom. Alex then found the same opponent, handle OxOO, at his table in 10 of those 11 sessions. Alex says he lost around $30,000; he was reportedly one of hundreds of players targeted over multiple years.
Risks this incident falls under
| Risk | Role | NIST AI 600-1 | Incidents | Last 6 quarters |
|---|---|---|---|---|
| AI used to run a cyber attack | Primary | Information Security | 38 | |
| AI system attacked or breached | Also | Information Security | 1 |
Sorted by rule from the case's fields; not yet read from the sources.
Control failure chain
L1 · ModelAnthropicModel provider
Sources not yet read for controls.
Model version not linked to a model card.
Other controls for this risk at this layer, not yet read for: Safety training and refusal, Cyber and weapons safeguards, Abuse monitoring and account enforcement, Staged or restricted release, Dangerous-capability testing before release, Outside red-teaming, Content safety classifiers, Safeguards kept on in testing, Reasoning monitoring.
L2 · HarnessHarness not namedAgent framework vendor
Sources not yet read for controls.
L3 · ApplicationDeployer not namedDeployer
Sources not yet read for controls.
L4 · Infrastructure / targetOrganisation hit
Sources not yet read for controls.
Other controls for this risk at this layer, not yet read for: Known flaws patched, Multi-factor sign-in and password policy, Network segmentation, Intrusion and endpoint detection, Backups and recovery, Phishing and fraud filters.
HeldFailedGot aroundMissingNot mentionedNot read yetAttacker's ownOrder: model · harness · application · target
The same controls in other incidents of this risk
| Control | Layer | Here | Held elsewhere | Did not hold elsewhere |
|---|---|---|---|---|
| Content safety classifiers | L1 Model | Not read yet | ||
| Safety training and refusal | L1 Model | Not read yet | 1 | |
| Cyber and weapons safeguards | L1 Model | Not read yet | ||
| Dangerous-capability testing before release | L1 Model | Not read yet | ||
| Outside red-teaming | L1 Model | Not read yet | ||
| Staged or restricted release | L1 Model | Not read yet | ||
| Abuse monitoring and account enforcement | L1 Model | Not read yet | ||
| Reasoning monitoring | L1 Model | Not read yet | 1 | |
| Safeguards kept on in testing | L1 Model | Not read yet | ||
| Known flaws patched | L4 Infrastructure / target | Not read yet | ||
| Multi-factor sign-in and password policy | L4 Infrastructure / target | Not read yet | ||
| Network segmentation | L4 Infrastructure / target | Not read yet | ||
| Intrusion and endpoint detection | L4 Infrastructure / target | Not read yet | ||
| Backups and recovery | L4 Infrastructure / target | Not read yet | ||
| Phishing and fraud filters | L4 Infrastructure / target | Not read yet |
Risk grouping: Not yet classified
No source we hold states: who caused it, intended or not, before or after release, the ai's part.
What the sources state
- When it was found 2026-09-25
- Direct loss $30,000
No source states: a step-by-step account, how many records were exposed, a count of the other parties affected, any court case, the cause, what set it off, what was done.
Others like this
Anthropic Claude model develops working Linux kernel MPTCP root exploit (CVE-2026-98432) 2026-10-29
Jailbroken Claude used to breach Mexican government networks and steal taxpayer and voter records 2026-03-02
Anthropic Claude models gained unauthorized access to real third-party systems during evaluations 2026-10-22
AI agent (ARTEX with Claude) used in cyberattacks targeting South Korean banks 2026-10-05
Show every field, with its source and grade
The AI system
What happened
Impact
Context
Notes on gaps
Alex's ~$30,000 loss is his own stated figure; the wider alleged theft of $1.5m-$4m across GGPoker and ACR is attributed to the scheme, not to this incident, so it is not recorded here. The article also describes earlier, separate superuser incidents (Absolute Poker/Ultimate Bet, the 2013 Barcelona laptop, Mike Postle) and the broader MeshAgent campaign; these are not AI-agent incidents and are not extracted. Extractor proposed values without quotes; dropped: . The document is a security newsletter; the only AI-related concrete event is the poker malware discovery, in which a Claude AI agent was the detector rather than the cause of loss. No date of occurrence, player count, jurisdiction, or remediation is stated. Other AI mentions in the document (ESET on APT AI use, tokenmaxxing at Amazon, Gemini 4 Carbon, Google stock, NIK C2, Aur0ra, PHP2Shell campaign) are not concrete AI-caused incidents and were excluded. Extractor proposed values without quotes; dropped: .
LR-2026-0301 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON