DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed15 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 15 filings

Morley Companies, Incorporated — July 2021 breach

Clustered 15 filings across 11 jurisdictions · filing window Jan 1, 2022 → Mar 21, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

15 filings

States

11

Affected · reported

659,339

First → last filing

Jan 1, 2022 → Mar 21, 2022

Merge confidence

100%

incident inc_0a076e4b03374ce2 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 15 regulatory filings. Intrusion Jul 2, 2021–Sep 2, 2021, discovered Aug 1, 2021 — the first regulatory filing landed 153 days later (flagged late). 659,339 individuals reported across the linked filings. Data reported: Government ID, Financial account, Identity (basic), and 4 more. Notifications rolled out on a 79-day schedule across 15 filings beginning Jan 1, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
153days

Discovered → first regulatory filing

Discovery variance
178days

Range of discovered_at dates across filings

Filing span
79days

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 · 35dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueHIPAA✓ HHS notifiedOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Jul 2, 2021breach begins
Aug 1, 2021discovered · members disagree
notification delay · 153 days
Jan 1, 2022first filing
Mar 21, 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JAN 26MA AGMA AG notice756 MA residents+25d
  3. JAN 26NH AGNH AG notice2 NH residents+25d
  4. JAN 26MT AGMT AG notice148 MT residents+25d
  5. JAN 26IN AGIN AG noticestates nationwide total 659,339+25d
  6. JAN 26ME AGME AG noticestates nationwide total 13,630+25d
  7. JAN 27SC AGSC AG notice2,234 SC residents+26d
  8. FEB 1NH AGNH AG notice35 NH residents+31d
  9. FEB 1HHS OCRHHS OCR noticestates nationwide total 659,194+31d
  10. FEB 1CA AGCA AG noticeno count stated+31d
  11. FEB 1ME AGME AG noticestates nationwide total 521,046+31d
  12. FEB 8OR AGOR AG noticestates nationwide total 590,785+38d
  13. MAR 21CA AGCA AG noticeno count stated+79d
  14. MAR 21WA AGWA AG notice42,633 WA residents+79d
  15. MAR 21NH AGNH AG noticemost recent · 30 affected+79d
  16. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 1, 2021
NH AG
Discovered
Aug 1, 2021IL AG + NH AG + WA AGDec 22, 2021MT AG + ME AGJan 20, 2022OR AGJan 26, 2022ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PHI · PII
MA AG + NH AG + MT AG +5
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)

659,339

Sum of filed state slices

70,024· 10.6% of stated

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

US659,339
WA42,633
IN24,156
SC2,234
MA756
MT148
ME62
NH35

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

79 days

Cadence

~1 / 5.6d

vs. multi-state median

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