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

Georgia Heritage Federal Credit Union — January 2025 breach

Clustered 10 filings across 8 jurisdictions · filing window Jan 15, 2026 → May 26, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

8

Affected · reported

43,077

First → last filing

Jan 15, 2026 → May 26, 2026

Merge confidence

100%

incident inc_8a16e59b62d843ae · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe a ransomware attack. Intrusion Jan 25, 2025, discovered Jan 25, 2025 — the first regulatory filing landed 355 days later (flagged late). 43,077 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 4 more. Notifications rolled out on a 131-day schedule across 10 filings beginning Jan 15, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
355days

Discovered → first regulatory filing

Discovery variance
16days

Range of discovered_at dates across filings

Filing span
131days

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 clocksLeak gap✗ Leak >180dMaine✗ ME AG >90d · 431dTexas✗ TX AG >30dMassachusetts✗ MA AG >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 25, 2025breach begins
Jan 25, 2025discovered · members disagree
notification delay · 355 days
Jan 15, 2026first filing
May 26, 2026most 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. JAN 15IN AGIN AG noticefirst filing · states nationwide total 43,077day 0
  2. JAN 15NE AGNE AG noticeno count statedday 0
  3. APR 17ME AGME AG noticestates nationwide total 43,077+92d
  4. APR 17NH AGNH AG notice12 NH residents+92d
  5. APR 17VT AGVT AG notice4 VT residents+92d
  6. APR 20SC AGSC AG notice1,945 SC residents+95d
  7. APR 22TX AGTX AG noticestates nationwide total 43,077+97d
  8. APR 27NH AGNH AG notice12 NH residents+102d
  9. APR 28MA AGMA AG notice36 MA residents+103d
  10. MAY 26NH AGNH AG noticemost recent · no count stated+131d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 25, 2025
IN AG
Discovered
Jan 25, 2025NE AG + SC AG + MA AG +1Feb 10, 2025ME AG + NH AG + TX AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · Financial account · Health (basic) · Employment
NE AG + ME AG + NH AG +4
Attack vector
Ransomware
NE 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)

43,077

Sum of filed state slices

2,359· 5.5% of stated

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

US43,077
SC1,945
TX294
IN50
MA36
ME18
NH12
VT4

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

131 days

Cadence

~1 / 14.6d

vs. multi-state median

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