DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79
State AGConfirmed1 filing · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Incident · single filing

CORE Health — September 2022 breach

One linked filing — more sources may join as they report · filed Oct 5, 2022. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

1 filing

States

1

Affected · reported

4

First → last filing

Oct 5, 2022

incident inc_e8a89c3362044e1f · merged by deterministic

Confirmed breach. Intrusion Sep 29, 2022, discovered Sep 30, 2022 — the first regulatory filing landed 5 days later. 4 individuals reported across the linked filings.

Litigation Timing

Notification delay
5days

Discovered → first regulatory filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksWashington✓ WA AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 29, 2022breach begins
Sep 30, 2022discovered
notification delay · 5 days
Oct 5, 2022first & only filing
—watching for filings

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

Member cascade — every filing about this breach

  1. OCT 5WA AGWA AG noticeonly filing · states nationwide total 4day 0
  2. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 29, 2022
WA AG
Discovered
Sep 30, 2022· 1d undetected
WA AG
Data types
PII · Identity (basic) · Government ID · PHI · Health (basic)
WA AG
Response
Contained the threat by disabling all unauthorized access to our network via the laptop · Commenced a prompt and thorough investigation · Filed a police report
WA 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)

4

Sum of filed state slices

4· 100.0% of stated

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

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 filing1 member

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

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.