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

Stevens & Lee, P.C. — June 2021 breach

Clustered 9 filings across 7 jurisdictions · filing window Dec 28, 2021 → Apr 11, 2022. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

7

Affected · reported

23,066

First → last filing

Dec 28, 2021 → Apr 11, 2022

Merge confidence

100%

incident inc_962d756e7b3545d3 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe unauthorized access. Intrusion Jun 28, 2021, discovered Jun 28, 2021 — the first regulatory filing landed 183 days later (flagged late). 23,066 individuals reported across the linked filings. Data reported: Government ID, Biometric, PII, and 5 more. Notifications rolled out on a 104-day schedule across 9 filings beginning Dec 28, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
183days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
104days

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 clocksMaine✗ ME AG >90d · 183dCalifornia✗ CA 60-day late · 283dWashington✗ WA AG >90dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

biometricfinancial_credentialsidentity_government

Incident timeline

Jun 28, 2021breach begins
Jun 28, 2021discovered
notification delay · 183 days
Dec 28, 2021first filing
Apr 11, 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. DEC 28ME AGME AG noticefirst filing · states nationwide total 344day 0
  2. DEC 30ME AGME AG noticestates nationwide total 344+2d
  3. JAN 3MA AGMA AG notice1,836 MA residents+6d
  4. APR 7IN AGIN AG noticestates nationwide total 23,066+100d
  5. APR 7MT AGMT AG notice14 MT residents+100d
  6. APR 8CA AGCA AG noticeno count stated+101d
  7. APR 8NH AGNH AG notice396 NH residents+101d
  8. APR 8WA AGWA AG notice1,028 WA residents+101d
  9. APR 11ME AGME AG noticemost recent · states nationwide total 23,066+104d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 28, 2021
ME AG
Discovered
Jun 28, 2021
ME AG + MT AG + CA AG +2
Data types
Biometric · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PHI · PII
ME AG + MT AG + MA AG +3
Attack vector
Unauthorized Access
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)

23,066

Sum of filed state slices

4,400· 19.1% of stated

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

US23,066
MA1,836
ME1,058
WA1,028
NH396
IN68
MT14

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

104 days

Cadence

~1 / 13d

vs. multi-state median

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