Cases › security breach › LR-2026-0673
Cloned voices used in vishing attacks on Citadel, Point72 and Two Sigma
Preliminary Why: Only a republished copy: Yahoo Finance · subject to change
Status: no action reported
No source states: loss or records, developer and model, agent tool, could do, deployer, industry.
Severity minor: Test applied: minor (contained to one deployer or evaluation, no third party touched). Fact: the sources report attempts with no stated impact on data or systems; Two Sigma says it has no indication of any impact to its data or systems, and Point72's initial review found no client information stolen.
Attackers ran a coordinated wave of AI-powered voice-phishing attempts against Point72, Millennium, Two Sigma and Citadel in recent days. The calls used cloned or mimicked voices to pressure employees into surrendering credentials or granting system access. Point72 told investors it had been attacked, but its initial review found no client information was stolen, and it was still reviewing the incident. Two Sigma said its security team responded quickly and blocked the attempt, with no indication of impact to its data or systems. Citadel, Point72 and Millennium declined to comment, and FINRA has been in contact with member firms about the attempted breaches.
What happened
What was done
No source states an action or fix.
Risks
Primary96 incidents
Rising: 24 vs 4.0 a week
Read from the sources; not yet reviewed by a person.
Controls
Not yet read for controls. Controls that mitigate the primary risk:
ModelSafety 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
Infrastructure / targetKnown flaws patched · Multi-factor sign-in and password policy · Network segmentation · Intrusion and endpoint detection · Backups and recovery · Phishing and fraud filters
Evidence
No source states: what the AI was doing, what went wrong, when it happened, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case, the cause, what set it off, what was done.
Show the full account: 4 items from the primary sources
What happened, in order
Not dated in the sources:
- Point72 informed investors it had been attacked; its initial review found no client information was stolen.
- Point72 told investors it was still reviewing the incident.
- Two Sigma said it successfully blocked the attempt.
- FINRA has been in contact with member firms about the attempted breaches.
Show every field, with its source and grade
What happened
Impact
Notes on gaps
Point72 said its initial review found no client information stolen but was still reviewing. Citadel and Millennium declined to comment, so their status is unknown. No remediation is reported. The Google blog, water-system attacks, and other firms' breaches in the source are other incidents and were excluded.
LR-2026-0673 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON