DisclosureLens
State AGConfirmed1 filing · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Incident · single filing

The Craneware Group — July 2026 breach

One linked filing — more sources may join as they report · filed Sep 14, 2026. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

1 filing

States

1

Affected · reported

1

First → last filing

Sep 14, 2026

incident inc_858cb53823904876 · merged by deterministic

Confirmed breach. Intrusion Jul 7, 2026–Jul 20, 2026, discovered Jul 20, 2026 — the first regulatory filing landed 56 days later (flagged late). 1 individual reported across the linked filings.

Litigation Timing

Notification delay
56days

Discovered → first regulatory filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing spanno leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksOregon OR AG >45dFull clock table in Litigation Timeline

Incident timeline

Jul 7, 2026breach begins
Jul 20, 2026discovered
notification delay · 56 days
Sep 14, 2026first & only 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

  1. SEP 14OR AGOR AG noticeonly filing · states nationwide total 1day 0
  2. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 7, 2026Jul 20, 2026
OR AG
Discovered
Jul 20, 2026· 13d undetected
OR AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

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

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

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.