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

Yazoo ValleyElectric Power Assosiation — August 2024 breach

Clustered 8 filings across 7 jurisdictions · filing window Aug 9, 2024 → Feb 3, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

8 filings

States

6

Affected · reported

20,997

First → last filing

Aug 9, 2024 → Feb 3, 2025

Merge confidence

100%

incident inc_a908eb96fd3b4d02 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Aug 23, 2024, discovered Aug 26, 2024 — the first regulatory filing landed 157 days later (flagged late). 20,997 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 178-day schedule across 6 filings beginning Aug 9, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
157days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
174days 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
178days

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 · 157dMaryland✗ MD AG >90dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 23, 2024breach begins
Aug 26, 2024discovered
notification delay · 157 days
Jan 30, 2025first filing
Feb 3, 2025most 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. AUG 9Leak siteakira postfirst filing · attacker claim · unverifiedday 0
  2. AUG 26Leak siteakira postattacker claim · unverified+17d
  3. JAN 30NE AGNE AG noticeno count stated+174d
  4. JAN 30IN AGIN AG noticestates nationwide total 20,997+174d
  5. JAN 30ME AGME AG noticestates nationwide total 20,997+174d
  6. JAN 30MD AGMD AG notice5 MD residents+174d
  7. JAN 31MA AGMA AG notice5 MA residents+175d
  8. FEB 3NH AGNH AG noticemost recent · 1 NH residents+178d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 23, 2024
IN AG
Discovered
Aug 26, 2024· 3d undetected
NE AG + ME AG + MD AG +1
Data types
Identity (basic) · Government ID · PII
NE AG + MD AG + MA AG +2
Attack vector
Unauthorized Access
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)

20,997

Sum of filed state slices

37· 0.2% of stated

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

US20,997
IN25
MD5
MA5
ME1
NH1

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 claim2 members

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

178 days

Cadence

~1 / 25.4d

vs. multi-state median

22.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.