DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed13 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedransomhousehigh sensitivity
Merged incident · 13 filings

First Financial Security — October 2023 breach

Clustered 13 filings across 10 jurisdictions · filing window Oct 19, 2023 → Feb 2, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

13 filings

States

9

Affected · reported

105,764

First → last filing

Oct 19, 2023 → Feb 2, 2024

Merge confidence

100%

incident inc_118691064fe247d1 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings and 1 unverified claim. Intrusion Oct 17, 2023, discovered Oct 17, 2023 — the first regulatory filing landed 78 days later (flagged late). 105,764 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 1 more. Notifications rolled out on a 106-day schedule across 12 filings beginning Oct 19, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
78days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
76days 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
106days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksMaine✗ ME AG >90d · 97dCalifornia✗ CA 60-day late · 94dOregon✗ OR AG >45dWashington⏱ WA AG >30dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 17, 2023breach begins
Oct 17, 2023discovered
notification delay · 78 days
Jan 3, 2024first filing
Feb 2, 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 19Leak siteransomhouse postfirst filing · attacker claim · unverifiedday 0
  2. JAN 3WA AGWA AG notice2,328 WA residents+76d
  3. JAN 19CA AGCA AG noticeno count stated+92d
  4. JAN 19IN AGIN AG noticestates nationwide total 105,764+92d
  5. JAN 22ME AGME AG noticestates nationwide total 105,764+95d
  6. JAN 22CA AGCA AG noticeno count stated+95d
  7. JAN 22NH AGNH AG noticestates nationwide total 6,842+95d
  8. JAN 23MA AGMA AG notice1,129 MA residents+96d
  9. JAN 23OR AGOR AG noticestates nationwide total 105,764+96d
  10. JAN 23MT AGMT AG notice40 MT residents+96d
  11. JAN 23SC AGSC AG notice718 SC residents+96d
  12. FEB 1NH AGNH AG notice33 NH residents+105d
  13. FEB 2MA AGMA AG noticemost recent · 1,129 MA residents+106d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 17, 2023
WA AG
Discovered
Oct 17, 2023
WA AG + CA AG + ME AG +4
Data types
Financial account · Identity (basic) · Government ID · PII
WA AG + CA AG + ME AG +4
Attack vector
Ransomware
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)

105,764

Sum of filed state slices

4,525· 4.3% of stated

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

US105,764
WA2,328
MA1,129
SC718
IN259
MT40
NH33
ME18

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 filing12 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

106 days

Cadence

~1 / 8.8d

vs. multi-state median

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