DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed10 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 10 filings

Fidelity Investments — August 2024 breach

Clustered 10 filings across 10 jurisdictions · filing window Oct 1, 2024 → Oct 14, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

77,099

First → last filing

Oct 1, 2024 → Oct 14, 2024

Merge confidence

100%

incident inc_fd4834d91e854d5b · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe hacking. Intrusion Aug 17, 2024–Aug 19, 2024, discovered Aug 17, 2024 — the first regulatory filing landed 45 days later (flagged late). 77,099 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 4 more. Notifications rolled out on a 13-day schedule across 10 filings beginning Oct 1, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
45days

Discovered → first regulatory filing

Discovery variance
2days

Range of discovered_at dates across filings

Filing span
13days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksOregon✗ OR AG >45dWashington⏱ WA AG >30dMaine⏱ ME AG >30d · 51dCalifornia✓ CA 60-day OK · 51dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 17, 2024breach begins
Aug 17, 2024discovered · members disagree
notification delay · 45 days
Oct 1, 2024first filing
Oct 14, 2024most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. OCT 1IL AGIL AG noticefirst filing · no count statedday 0
  2. OCT 9WA AGWA AG notice2,731 WA residents+8d
  3. OCT 9OR AGOR AG noticestates nationwide total 77,099+8d
  4. OCT 9NH AGNH AG noticeno count stated+8d
  5. OCT 9CA AGCA AG noticeno count stated+8d
  6. OCT 9MA AGMA AG notice2,768 MA residents+8d
  7. OCT 9ME AGME AG noticestates nationwide total 77,099+8d
  8. OCT 9IN AGIN AG noticestates nationwide total 77,099+8d
  9. OCT 9MT AGMT AG notice160 MT residents+8d
  10. OCT 14SC AGSC AG noticemost recent · 903 SC residents+13d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 17, 2024 – Aug 19, 2024
WA AG
Discovered
Aug 17, 2024IL AGAug 19, 2024WA AG + OR AG + NH AG +4filings disagree on discovery
Data types
Financial · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
WA AG + NH AG + CA AG +4
Attack vector
Unauthorized Access
WA AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

77,099

Sum of filed state slices

7,956· 10.3% of stated

90% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US77,099
MA2,768
WA2,731
IN1,057
SC903
ME337
MT160

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing10 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

13 days

Cadence

~1 / 1.4d

vs. multi-state median

1.6× slower

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.