DisclosureLens
Leak SiteState AGConfirmed5 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforceddunghillhigh sensitivity
Merged incident · 5 filings

The Robins & Morton Group — October 2022 breach

Clustered 5 filings across 5 jurisdictions · filing window Dec 22, 2022 Sep 26, 2023. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

5 filings

States

4

Affected · reported

15,032

First → last filing

Dec 22, 2022 Sep 26, 2023

Merge confidence

100%

incident inc_20f9f1eb4b1d4fe2 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Oct 16, 2022–Oct 17, 2022, discovered Oct 17, 2022 — the first regulatory filing landed 66 days later. 15,032 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 278-day schedule across 4 filings beginning Dec 22, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
66days

Discovered → first regulatory filing

Discovery variance
50days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 278d

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

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delayno SEC 8-K in this cluster.

Regulatory clocksMassachusetts MA credit monitoring dueMaine ME AG ≤30d · 16dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 16, 2022breach begins
Oct 17, 2022discovered · members disagree
notification delay · 66 days
Dec 22, 2022first 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. DEC 22MA AGMA AG noticefirst filing · 22 MA residentsday 0
  2. DEC 22IN AGIN AG noticestates nationwide total 15,032day 0
  3. DEC 22MT AGMT AG notice2 MT residentsday 0
  4. DEC 22ME AGME AG notice171 affectedday 0
  5. SEP 26Leak sitedunghill postmost recent · attacker claim · unverified+278d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 16, 2022
IN AG
Discovered
Oct 17, 2022MT AGDec 6, 2022ME AGfilings disagree on discovery
Data types
Identity (basic) · Government ID
MA AG + MT AG + ME AG
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)

15,032

Sum of filed state slices

375· 2.5% of stated

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

US15,032
IN180
ME171
MA22
MT2

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

278 days

Cadence

~1 / 69.5d

vs. multi-state median

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