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

Barnhart Crane & Rigging Company, Inc. — April 2025 breach

Clustered 10 filings across 10 jurisdictions · filing window May 1, 2026 → May 26, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

22,822

First → last filing

May 1, 2026 → May 26, 2026

Merge confidence

100%

incident inc_6571109aaa9b4551 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe unauthorized access. Intrusion Apr 23, 2025–Apr 24, 2025, discovered Apr 23, 2025 — the first regulatory filing landed 373 days later (flagged late). 22,822 individuals reported across the linked filings. Data reported: Government ID, Financial account, Health (basic), and 3 more. Notifications rolled out on a 25-day schedule across 10 filings beginning May 1, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
373days

Discovered → first regulatory filing

Discovery variance
393days

Range of discovered_at dates across filings

Filing span
25days

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 >90dMaine✓ ME AG ≤30d · 30dOregon✓ OR AG ≤45dTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 23, 2025breach begins
Apr 23, 2025discovered · members disagree
notification delay · 373 days
May 1, 2026first filing
May 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. MAY 1IL AGIL AG noticefirst filing · no count statedday 0
  2. MAY 21IN AGIN AG noticestates nationwide total 22,822+20d
  3. MAY 21WA AGWA AG notice1,068 WA residents+20d
  4. MAY 21ME AGME AG noticestates nationwide total 22,822+20d
  5. MAY 21MA AGMA AG notice119 MA residents+20d
  6. MAY 21NE AGNE AG notice31 affected+20d
  7. MAY 21OR AGOR AG noticestates nationwide total 22,822+20d
  8. MAY 21VT AGVT AG notice4 VT residents+20d
  9. MAY 22TX AGTX AG noticestates nationwide total 22,822+21d
  10. MAY 26NH AGNH AG noticemost recent · 21 NH residents+25d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 23, 2025
IN AG
Discovered
Apr 23, 2025WA AG + NH AGApr 21, 2026IL AG + ME AG + OR AGMay 21, 2026TX AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
IL AG + WA AG + MA AG +5
Attack vector
Unauthorized Access
WA 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)

22,822

Sum of filed state slices

3,620· 15.9% of stated

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

US22,822
TX1,652
WA1,068
IN717
MA119
NE31
NH21
ME8
VT4

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

25 days

Cadence

~1 / 2.8d

vs. multi-state median

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