All incidents View linkage analytics →Get the evidence package — $7.99 what’s inside →

Confirmed7 filings · 6 statesUnverified claimConfirmedEnforcedembargohigh sensitivity

Merged incident · 7 filings

Diligent Delivery Systems — July 2024 breach

Clustered 7 filings across 7 jurisdictions · filing window Jul 11, 2024 → Nov 5, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 filings

States

Affected · reported

10,545

First → last filing

Jul 11, 2024 → Nov 5, 2024

Merge confidence

100%

incident inc_ad953b1a3fa94729 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jul 8, 2024–Jul 9, 2024, discovered Jul 11, 2024 — the first regulatory filing landed 117 days later (flagged late). 10,545 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 117-day schedule across 6 filings beginning Jul 11, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

117days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Leak precedence

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

117days

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 bdayMaine✗ ME AG >90d · 117dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 8, 2024breach begins

Jul 11, 2024discovered

notification delay · 117 days

Nov 5, 2024first filing

—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

JUL 11Leak siteembargo postfirst filing · attacker claim · unverifiedoperator-confirmedday 0
NOV 5VT AGVT AG noticeno count statedauto-linked+117d
NOV 5MA AGMA AG notice65 MA residentsoperator-confirmed+117d
NOV 5NH AGNH AG notice8 NH residentsauto-linked+117d
NOV 5ME AGME AG noticestates nationwide total 10,545auto-linked+117d
NOV 5CA AGCA AG noticeno count statedauto-linked+117d
NOV 5IN AGIN AG noticemost recent · states nationwide total 10,545+117d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Jul 8, 2024 – Jul 9, 2024
Discovered: Jul 11, 2024· 3d undetected
Data types: Identity (basic) · Government ID
Attack vector: Unauthorized Access

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)

10,545

Sum of filed state slices

91· 0.9% of stated

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

US10,545

MA65

ME11

NH8

IN7

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

117 days

Cadence

~1 / 19.5d

vs. multi-state median

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