DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed7 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedblackbytehigh sensitivity
Merged incident · 7 filings

San Fransisco 49ers — February 2022 breach

Clustered 7 filings across 7 jurisdictions · filing window Feb 12, 2022 → Sep 1, 2022. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 filings

States

6

Affected · reported

20,930

First → last filing

Feb 12, 2022 → Sep 1, 2022

Merge confidence

100%

incident inc_5220967c3002457b · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Feb 6, 2022–Feb 11, 2022, discovered Aug 9, 2022 — the first regulatory filing landed 23 days later (flagged late). 20,930 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 1 more. Notifications rolled out on a 201-day schedule across 6 filings beginning Feb 12, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
23days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
201days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
201days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 6, 2022breach begins
Aug 9, 2022discovered
notification delay · 23 days
Sep 1, 2022first filing
—watching for filings

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

Member cascade — every filing about this breach

  1. FEB 12Leak siteblackbyte postfirst filing · attacker claim · unverifiedday 0
  2. SEP 1NH AGNH AG notice15 NH residents+201d
  3. SEP 1CA AGCA AG noticeno count stated+201d
  4. SEP 1ME AGME AG noticestates nationwide total 20,930+201d
  5. SEP 1IN AGIN AG noticestates nationwide total 20,930+201d
  6. SEP 1MA AGMA AG notice90 MA residents+201d
  7. SEP 1MT AGMT AG noticemost recent · 80 MT residents+201d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 6, 2022 – Feb 11, 2022
NH AG
Discovered
Aug 9, 2022· 184d undetected
NH AG + ME AG
Data types
Financial account · Identity (basic) · Government ID · PII
NH AG + ME AG + MA AG +2
Attack vector
Unauthorized Access
NH 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)

20,930

Sum of filed state slices

549· 2.6% of stated

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

US20,930
IN357
MA90
MT80
NH15
ME7

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing6 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
Reviewed
operator-reviewed Aug 23, 2026 · at least one link edge was human-adjudicated
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

201 days

Cadence

~1 / 33.5d

vs. multi-state median

25.1× 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.