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

Hertz Farm Management — June 2025 breach

Clustered 10 filings across 9 jurisdictions · filing window Jun 25, 2025 → Dec 15, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

8

Affected · reported

1,596

First → last filing

Jun 25, 2025 → Dec 15, 2025

Merge confidence

100%

incident inc_0afa6267007b4002 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Jun 29, 2025–Jul 3, 2025, discovered Jun 29, 2025 — the first regulatory filing landed 163 days later (flagged late). 1,596 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 173-day schedule across 8 filings beginning Jun 25, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
163days

Discovered → first regulatory filing

Discovery variance
131days

Range of discovered_at dates across filings

Leak precedence
167days 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
173days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont✗ VT AG >45 bdayLeak gap⏱ Leak >90dMaine⏱ ME AG >30d · 32dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 29, 2025breach begins
Jun 29, 2025discovered · members disagree
notification delay · 163 days
Dec 9, 2025first filing
Dec 15, 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. JUN 25Leak siteakira postfirst filing · attacker claim · unverifiedday 0
  2. JUN 29Leak siteakira postattacker claim · unverified+4d
  3. DEC 9IA AGIA AG notice615 IA residents+167d
  4. DEC 9ME AGME AG noticestates nationwide total 1,596+167d
  5. DEC 9NE AGNE AG notice123 NE residents+167d
  6. DEC 9MT AGMT AG notice6 MT residents+167d
  7. DEC 9IN AGIN AG noticestates nationwide total 1,596+167d
  8. DEC 9VT AGVT AG noticeno count stated+167d
  9. DEC 10MA AGMA AG notice13 MA residents+168d
  10. DEC 15NH AGNH AG noticemost recent · 3 NH residents+173d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 29, 2025
IA AG
Discovered
Jun 29, 2025IA AG + NE AG + MT AG +1Nov 7, 2025ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
IA AG + ME AG + NE AG +4
Attack vector
Unauthorized Access
IA 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)

1,596

Sum of filed state slices

780· 48.9% of stated

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

US1,596
IA615
NE123
IN15
MA13
MT6
ME5
NH3

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

173 days

Cadence

~1 / 19.2d

vs. multi-state median

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