DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed6 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforceddragonforcehigh sensitivity
Merged incident · 6 filings

City of La Vergne — October 2025 breach

Clustered 6 filings across 5 jurisdictions · filing window Oct 17, 2025 → Jun 26, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 filings

States

4

Affected · reported

25,728

First → last filing

Oct 17, 2025 → Jun 26, 2026

Merge confidence

100%

incident inc_408f52f88c2e493f · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 2 unverified claims. The filings describe a ransomware attack. Intrusion Oct 11, 2025, discovered Oct 17, 2025 — the first regulatory filing landed 249 days later (flagged late). 25,728 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 252-day schedule across 4 filings beginning Oct 17, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
249days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
249days 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
252days

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 >180dMassachusetts✗ MA AG >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 11, 2025breach begins
Oct 17, 2025discovered
notification delay · 249 days
Jun 23, 2026first filing
Jun 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. OCT 17Leak sitedragonforce postfirst filing · attacker claim · unverifiedday 0
  2. DEC 8Leak sitedragonforce postattacker claim · unverified+53d
  3. JUN 23VT AGVT AG notice1 VT residents+249d
  4. JUN 26NE AGNE AG noticeno count stated+252d
  5. JUN 26IN AGIN AG noticestates nationwide total 25,728+252d
  6. JUN 26MA AGMA AG noticemost recent · 14 MA residents+252d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 11, 2025
IN AG
Discovered
Oct 17, 2025· 6d undetected
NE AG + MA AG
Data types
Financial account · Identity (basic) · Government ID
VT AG + NE AG + MA AG
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)

25,728

Sum of filed state slices

83· 0.3% of stated

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

US25,728
IN68
MA14
VT1

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 filing4 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 9, 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

252 days

Cadence

~1 / 50.4d

vs. multi-state median

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