DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed8 records · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedtermitehigh sensitivity
Merged incident · 8 records

ROLAND MACHINERY COMPANY — May 2026 breach

Clustered 8 records across 6 jurisdictions: 7 filings and 1 leak-site claim · filing window Jul 7, 2026 → Jul 15, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 records

States

6

Affected · reported

10,376

First → last dated filing

Jul 7, 2026 → Jul 15, 2026

Merge confidence

100%

incident inc_27d072181b0146c1 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion May 28, 2026–May 29, 2026, discovered May 29, 2026. 10,376 individuals reported across the linked filings. Data reported: Government ID, Financial account, Identity (basic), and 1 more. Notifications rolled out on a 8-day schedule across 5 dated filings beginning Jul 7, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
11days

Range of discovered_at dates across filings

Filing span
8days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 28, 2026breach begins
May 29, 2026discovered · members disagree
Jul 7, 2026first dated filing
Jul 15, 2026most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. JUN 8Leak sitetermite postfirst record · attacker claim · unverifiedday 0
  2. JUL 1IL AGIL AG noticefiling day not on record · no count stated—
  3. JUL 7MA AGMA AG notice19 MA residents+29d
  4. JUL 7VT AGVT AG notice5 VT residents+29d
  5. JUL 8IN AGIN AG noticestates nationwide total 10,376+30d
  6. JUL 8NH AGNH AG notice4 NH residents+30d
  7. JUL 8NE AGNE AG noticefiling day not on record · no count stated—
  8. JUL 15NH AGNH AG noticemost recent · 4 NH residents+37d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 28, 2026
IN AG
Discovered
May 29, 2026IL AG + NH AGJun 9, 2026NE AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PCI
IL AG + MA AG + VT AG +2
Attack vector
Unauthorized Access
MA 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)

10,376

Sum of filed state slices

274· 2.6% of stated

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

US10,376
IN246
MA19
VT5
NH4

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 filing7 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 16, 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

8 days

Cadence

~1 / 2d

vs. multi-state median

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