DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed7 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcritical sensitivity
Merged incident · 7 filings

The North Highland Holding Company LLC — May 2022 breach

Clustered 7 filings across 5 jurisdictions · filing window Jul 28, 2022 → Sep 26, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 filings

States

5

Affected · reported

14,761

First → last filing

Jul 28, 2022 → Sep 26, 2022

Merge confidence

100%

incident inc_825a0c97642c49e8 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings. Intrusion May 26, 2022–Jun 6, 2022, discovered Jun 6, 2022 — the first regulatory filing landed 52 days later (flagged late). 14,761 individuals reported across the linked filings. Data reported: Government ID, Minor, Financial account, and 4 more. Notifications rolled out on a 60-day schedule across 7 filings beginning Jul 28, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
52days

Discovered → first regulatory filing

Discovery variance
22days

Range of discovered_at dates across filings

Filing span
60days

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 clocksOregon✗ OR AG >45dCalifornia✗ CA 60-day late · 109dMaine⏱ ME AG >30d · 90dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_governmentminor

Incident timeline

May 26, 2022breach begins
Jun 6, 2022discovered · members disagree
notification delay · 52 days
Jul 28, 2022first filing
Sep 26, 2022most 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. JUL 28MA AGMA AG noticefirst filing · 64 MA residentsday 0
  2. JUL 28ME AGME AG noticestates nationwide total 10,623day 0
  3. JUL 29OR AGOR AG noticestates nationwide total 10,632+1d
  4. SEP 23MT AGMT AG notice1 MT residents+57d
  5. SEP 26CA AGCA AG noticeno count stated+60d
  6. SEP 26ME AGME AG noticestates nationwide total 14,761+60d
  7. SEP 26OR AGOR AG noticemost recent · states nationwide total 14,761+60d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 26, 2022
ME AG
Discovered
Jun 6, 2022MT AG + CA AGJun 28, 2022ME AG + OR AGfilings disagree on discovery
Data types
Employment · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · Minor
MA AG + MT AG + CA AG +1
Attack vector
Ransomware
ME 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)

14,761

Sum of filed state slices

70· 0.5% of stated

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

US14,761
MA64
ME5
MT1

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

60 days

Cadence

~1 / 10d

vs. multi-state median

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