DisclosureLens
State AGConfirmed23 filings · 12 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 23 filings

NCB Management Services, Inc. — February 2023 breach

Clustered 23 filings across 12 jurisdictions · filing window Mar 24, 2023 → Jun 28, 2023. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

23 filings

States

12

Affected · reported

1,087,842

First → last filing

Mar 24, 2023 → Jun 28, 2023

Merge confidence

100%

incident inc_635c4e1325ce41e1 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 23 regulatory filings. Intrusion Feb 1, 2023–Feb 6, 2023, discovered Feb 4, 2023 — the first regulatory filing landed 48 days later (flagged late); 2 later filings were also flagged late. 1,087,842 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 6 more. Notifications rolled out on a 96-day schedule across 23 filings beginning Mar 24, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
48days

Discovered → first regulatory filing

Discovery variance
81days

Range of discovered_at dates across filings

Filing span
96days

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 clocksCalifornia✗ CA 60-day late · 76dOregon✗ OR AG >45dWashington✗ WA AG >90dMaine⏱ ME AG >30d · 48dHawaii✓ HI CRA notice dueMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 1, 2023breach begins
Feb 4, 2023discovered · members disagree
notification delay · 48 days
Mar 24, 2023first 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. MAR 24ME AGME AG noticefirst filing · states nationwide total 494,969day 0
  2. MAR 24CA AGCA AG noticeno count statedday 0
  3. MAR 24OR AGOR AG noticestates nationwide total 494,969day 0
  4. MAR 24WA AGWA AG notice12,510 WA residentsday 0
  5. MAR 28DE AGDE AG noticeno count stated+4d
  6. MAR 29NH AGNH AG notice2,210 NH residents+5d
  7. APR 19IN AGIN AG noticestates nationwide total 1,087,842+26d
  8. MAY 19DE AGDE AG noticeno count stated+56d
  9. MAY 22CA AGCA AG noticeno count stated+59d
  10. MAY 22OR AGOR AG noticestates nationwide total 1,087,842+59d
  11. MAY 22MT AGMT AG notice2,594 MT residents+59d
  12. MAY 22HI AGHI AG notice4,145 HI residents+59d
  13. MAY 22NH AGNH AG notice2,938 NH residents+59d
  14. MAY 22VT AGVT AG noticeno count stated+59d
  15. MAY 22WA AGWA AG notice15,899 WA residents+59d
  16. MAY 23ME AGME AG noticestates nationwide total 1,087,842+60d
  17. MAY 23MA AGMA AG notice9,893 MA residents+60d
  18. MAY 23SC AGSC AG notice31,484 SC residents+60d
  19. MAY 26WA AGWA AG notice605 WA residents+63d
  20. MAY 26ME AGME AG noticestates nationwide total 16,779+63d
  21. MAY 26MT AGMT AG notice215 MT residents+63d
  22. JUN 16DE AGDE AG noticeno count stated+84d
  23. JUN 28NH AGNH AG noticemost recent · 2,938 NH residents+96d
  24. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 1, 2023
ME AG
Discovered
Feb 4, 2023ME AG + CA AG + OR AG +5Apr 26, 2023ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID
ME AG + CA AG + WA AG +6
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)

1,087,842

Sum of filed state slices

87,828· 8.1% of stated

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

US1,087,842
SC31,484
IN17,614
WA15,899
MA9,893
HI4,145
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 filing23 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

96 days

Cadence

~1 / 4.4d

vs. multi-state median

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