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

Maritz Holdings Inc. — August 2025 breach

Clustered 11 filings across 9 jurisdictions · filing window Nov 13, 2025 → Apr 6, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

8

Affected · reported

4,906

First → last filing

Nov 13, 2025 → Apr 6, 2026

Merge confidence

100%

incident inc_0e2deb7bd0374362 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Aug 10, 2025–Aug 13, 2025, discovered Nov 1, 2025 — the first regulatory filing landed 118 days later (flagged late). 4,906 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 1 more. Notifications rolled out on a 143-day schedule across 10 filings beginning Nov 13, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
118days

Discovered → first regulatory filing

Discovery variance
12days

Range of discovered_at dates across filings

Leak precedence
105days 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
143days

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 · 106dVermont✗ VT AG >45 bdayCalifornia✗ CA 60-day late · 153dTexas✗ TX AG >30dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 10, 2025breach begins
Nov 1, 2025discovered · members disagree
notification delay · 118 days
Feb 27, 2026first filing
Apr 6, 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. NOV 13Leak sitecl0p postfirst filing · attacker claim · unverifiedday 0
  2. FEB 27CA AGCA AG noticeno count stated+105d
  3. FEB 27IN AGIN AG noticestates nationwide total 4,906+105d
  4. FEB 27NH AGNH AG notice3 NH residents+105d
  5. FEB 27NE AGNE AG noticeno count stated+105d
  6. FEB 27ME AGME AG notice4 ME residents+105d
  7. FEB 27VT AGVT AG noticeno count stated+105d
  8. FEB 27MA AGMA AG notice6 MA residents+105d
  9. APR 3NH AGNH AG notice11 NH residents+140d
  10. APR 3CA AGCA AG noticeno count stated+140d
  11. APR 6TX AGTX AG noticemost recent · states nationwide total 4,906+143d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 10, 2025 – Aug 13, 2025
CA AG
Discovered
Nov 1, 2025CA AG + NH AG + NE AG +2Nov 13, 2025ME AG + TX AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
CA AG + NH AG + NE AG +4
Attack vector
Unauthorized Access
NH 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)

4,906

Sum of filed state slices

416· 8.5% of stated

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

US4,906
TX320
IN75
NH11
MA6
ME4

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

143 days

Cadence

~1 / 14.3d

vs. multi-state median

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