DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79
State AGConfirmed2 filings · 2 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Merged incident · 2 filings

Mitchell County, North Carolina — October 2025 breach

Clustered 2 filings across 2 jurisdictions · filing window May 1, 2026 → May 5, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

2 filings

States

2

Affected · reported

—

First → last filing

May 1, 2026 → May 5, 2026

Merge confidence

100%

incident inc_dd85db1bdb3a4098 · merged by deterministic · confidence 100%

Confirmed breach. One breach, 2 legal records. Intrusion Oct 16, 2025–Oct 20, 2025, discovered Oct 20, 2025 — the first regulatory filing landed 193 days later (flagged late). This page is the deduped roll-up; each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
193days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
4days

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 clocksMassachusetts✗ MA AG >90dFull clock table in Litigation Timeline

Incident timeline

Oct 16, 2025breach begins
Oct 20, 2025discovered
notification delay · 193 days
May 1, 2026first filing
May 5, 2026most 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 1NE AGNE AG noticefirst filing · no count statedday 0
  2. MAY 5MA AGMA AG noticemost recent · no count stated+4d
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 16, 2025 – Oct 20, 2025
NE AG
Discovered
Oct 20, 2025· 4d undetected
NE AG + MA AG
Data types
PII · PHI · Health (basic)
NE AG + MA AG
Attack vector
Ransomware
NE AG
Response
Reported this incident to federal law enforcement · Worked with nationally recognized third-party cybersecurity and data forensics consultants · Worked with the North Carolina Joint Cybersecurity Task Force and other state resources
NE AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

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

4 days

vs. multi-state median

1.3× faster

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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.