DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed18 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 18 filings

NCB Management Services, Inc. — February 2023 breach

Clustered 18 filings across 8 jurisdictions · filing window May 22, 2020 → Jun 28, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

18 filings

States

8

Affected · reported

1,087,842

First → last filing

May 22, 2020 → Jun 28, 2023

Merge confidence

100%

incident inc_57db4e2f801d4517 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 18 regulatory filings. Intrusion Feb 1, 2023–Feb 6, 2023, discovered Feb 4, 2023. 1,087,842 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 5 more. Notifications rolled out on a 1132-day schedule across 18 filings beginning May 22, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
81days

Range of discovered_at dates across filings

Filing span
1132days

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 · 108dCalifornia✗ CA 60-day late · 76dOregon✗ OR AG >45dWashington✗ WA AG >90dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Feb 1, 2023breach begins
Feb 4, 2023discovered · members disagree
May 22, 2020first filing
Jun 28, 2023most 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. MAY 22VT AGVT AG noticefirst filing · no count statedday 0
  2. MAR 24ME AGME AG noticestates nationwide total 494,969+1036d
  3. MAR 24CA AGCA AG noticeno count stated+1036d
  4. MAR 24OR AGOR AG noticestates nationwide total 494,969+1036d
  5. MAR 28DE AGDE AG noticeno count stated+1040d
  6. MAR 29NH AGNH AG notice2,210 NH residents+1041d
  7. MAY 19DE AGDE AG noticeno count stated+1092d
  8. MAY 22WA AGWA AG notice15,899 WA residents+1095d
  9. MAY 22OR AGOR AG noticestates nationwide total 1,087,842+1095d
  10. MAY 22MT AGMT AG notice2,594 MT residents+1095d
  11. MAY 22NH AGNH AG notice2,938 NH residents+1095d
  12. MAY 22CA AGCA AG noticeno count stated+1095d
  13. MAY 23ME AGME AG noticestates nationwide total 1,087,842+1096d
  14. MAY 26MT AGMT AG notice215 MT residents+1099d
  15. MAY 26ME AGME AG noticestates nationwide total 16,779+1099d
  16. MAY 26NH AGNH AG notice53 NH residents+1099d
  17. JUN 16DE AGDE AG noticeno count stated+1120d
  18. JUN 28NH AGNH AG noticemost recent · 2,938 NH residents+1132d
  19. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 1, 2023
VT AG
Discovered
Feb 4, 2023ME AG + CA AG + OR AG +4Apr 26, 2023ME AGfilings disagree on discovery
Data types
Employment · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PHI · PII
VT AG + CA AG + DE AG +4
Attack vector
Unauthorized Access
VT 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)

1,087,842

Sum of filed state slices

24,692· 2.3% of stated

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

US1,087,842
WA15,899
ME3,261
NH2,938
MT2,594

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 filing18 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 Aug 10, 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

1132 days

Cadence

~1 / 66.6d

vs. multi-state median

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