DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed11 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 11 filings

Dulcich, Inc. — June 2024 breach

Clustered 11 filings across 11 jurisdictions · filing window Oct 14, 2025 → Oct 20, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

40,066

First → last filing

Oct 14, 2025 → Oct 20, 2025

Merge confidence

100%

incident inc_6e2c39f77f664967 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Jun 24, 2024–Jun 25, 2024, discovered Jun 24, 2024 — the first regulatory filing landed 477 days later (flagged late). 40,066 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 6-day schedule across 11 filings beginning Oct 14, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
477days

Discovered → first regulatory filing

Discovery variance
462days

Range of discovered_at dates across filings

Filing span
6days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksWashington✗ WA AG >90dTexas✗ TX AG >30dMaine✓ ME AG ≤30d · 15dOregon✓ OR AG ≤45dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 24, 2024breach begins
Jun 24, 2024discovered · members disagree
notification delay · 477 days
Oct 14, 2025first filing
Oct 20, 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. OCT 14CA AGCA AG noticefirst filing · no count statedday 0
  2. OCT 14MT AGMT AG notice22 MT residentsday 0
  3. OCT 14NE AGNE AG noticeno count statedday 0
  4. OCT 14IN AGIN AG noticestates nationwide total 40,066day 0
  5. OCT 14ME AGME AG noticestates nationwide total 40,066day 0
  6. OCT 14OR AGOR AG noticestates nationwide total 40,066day 0
  7. OCT 14VT AGVT AG noticeno count statedday 0
  8. OCT 14WA AGWA AG notice10,761 WA residentsday 0
  9. OCT 15MA AGMA AG notice8 MA residents+1d
  10. OCT 16TX AGTX AG noticestates nationwide total 40,066+2d
  11. OCT 20NH AGNH AG noticemost recent · 4 NH residents+6d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 24, 2024 – Jun 25, 2024
CA AG
Discovered
Jun 24, 2024NE AG + WA AG + TX AG +1Sep 29, 2025ME AG + OR AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
CA AG + MT AG + NE AG +6
Attack vector
Unauthorized Access
MT 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)

40,066

Sum of filed state slices

12,792· 31.9% of stated

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

US40,066
WA10,761
TX1,977
MT22
IN17
MA8
NH4
ME3

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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing11 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 Jun 12, 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

6 days

Cadence

~1 / 0.6d

vs. multi-state median

1.3× faster

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.