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

Everside Health — December 2025 breach

Clustered 3 filings across 3 jurisdictions · filing window Jul 1, 2026 → Aug 4, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

3 filings

States

3

Affected · reported

1,389,758

First → last filing

Jul 1, 2026 → Aug 4, 2026

Merge confidence

100%

incident inc_17445896afaa48a6 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. The filing describes unauthorized access. Intrusion Dec 2, 2025–Dec 18, 2025, discovered Jun 26, 2026 — the first regulatory filing landed 5 days later. 1,389,758 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Identity (basic), and 1 more. Notifications rolled out on a 34-day schedule across 3 filings beginning Jul 1, 2026. Each member filing remains the legal record for its jurisdiction.

What the filings say

WA AG

Everside Health, a healthcare provider, was notified by its business associate Aesto, LLC on June 26, 2026, of a security incident involving Aesto's AWS infrastructure. Between Dec 2-18, 2025, an unauthorized actor accessed PHI of ~21,308 Washington residents, including names, SSNs, DOBs, and medical record numbers. Aesto contained the incident, engaged forensic investigators, and began mailing notification letters on July 31, 2026, offering 12 months of credit monitoring.

AI-generated summary of the linked filing — not the filing's own words, and not independently verified.

Litigation Timing

Supplemental
Notification delay
5days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
34days

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 clocksWashington⏱ WA AG >30dTexas✓ TX CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 2, 2025breach begins
Jun 26, 2026discovered
notification delay · 5 days
Jul 1, 2026first filing
Aug 4, 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. JUL 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JUL 31WA AGWA AG notice21,308 WA residents+30d
  3. AUG 4TX AGTX AG noticemost recent · states nationwide total 1,389,758+34d
  4. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 2, 2025 – Dec 18, 2025
WA AG
Discovered
Jun 26, 2026· 206d undetected
IL AG + WA AG + TX AG
Data types
Government ID · PHI · PII
IL AG + WA AG + TX AG
Attack vector
Unauthorized Access
WA AG
Response
Commenced an investigation with support from cybersecurity professionals · Took steps to contain the incident · Notified the healthcare provider (Everside) on June 26, 2026
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)

1,389,758

Sum of filed state slices

43,518· 3.1% of stated

97% 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 filing3 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

34 days

Cadence

~1 / 17d

vs. multi-state median

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

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.