DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed11 records · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcontihigh sensitivity
Merged incident · 11 records

ELEVATE SERVICES, INC. — March 2022 breach

Clustered 11 records across 7 jurisdictions: 10 filings and 1 leak-site claim · filing window Dec 28, 2022 → Aug 4, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 records

States

7

Affected · reported

3,950

First → last filing

Dec 28, 2022 → Aug 4, 2023

Merge confidence

100%

incident inc_e53c89af37174842 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 1 unverified claim. Intrusion Mar 5, 2022–Mar 15, 2022, discovered Mar 14, 2022 — the first regulatory filing landed 289 days later; 1 later filing was flagged late. 3,950 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 4 more. Notifications rolled out on a 219-day schedule across 10 filings beginning Dec 28, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
289days

Discovered → first regulatory filing

Discovery variance
431days

Range of discovered_at dates across filings

Leak precedence
258days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
219days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap✗ Leak >180dVermont✗ VT AG >45 bdayFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 5, 2022breach begins
Mar 14, 2022discovered · members disagree
notification delay · 289 days
Dec 28, 2022first filing
Aug 4, 2023most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

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

  1. APR 14Leak siteconti postfirst record · attacker claim · unverifiedday 0
  2. DEC 28CA AGCA AG noticeno count stated+258d
  3. FEB 8MT AGMT AG notice3 MT residents+300d
  4. FEB 27MA AGMA AG notice43 MA residents+319d
  5. MAR 2VT AGVT AG noticeno count stated+322d
  6. MAR 7CA AGCA AG noticeno count stated+327d
  7. APR 19MT AGMT AG notice4 MT residents+370d
  8. JUN 7ME AGME AG noticestates nationwide total 425+419d
  9. JUN 12NH AGNH AG notice1 NH residents+424d
  10. AUG 4IN AGIN AG noticestates nationwide total 3,950+477d
  11. AUG 4NH AGNH AG noticemost recent · 21 NH residents+477d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 5, 2022 – Mar 15, 2022
CA AG
Discovered
Mar 14, 2022CA AG + MT AG + VT AG +1May 19, 2023ME AGfilings disagree on discovery
Data types
Employment · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
CA AG + MT AG + VT AG +3
Attack vector
Ransomware
CA 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)

3,950

Sum of filed state slices

92· 2.3% of stated

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

US3,950
MA43
IN23
NH21
MT4
ME1

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 filing10 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 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

219 days

Cadence

~1 / 24.3d

vs. multi-state median

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