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

American Association of Critical-Care Nurses — March 2025 breach

Clustered 12 filings across 12 jurisdictions · filing window Aug 29, 2025 → Sep 4, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

12 filings

States

12

Affected · reported

57,526

First → last dated filing

Aug 29, 2025 → Sep 4, 2025

Merge confidence

100%

incident inc_237b009b7e724476 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. The filings describe unauthorized access. Intrusion Mar 8, 2025–Aug 1, 2025, discovered Jul 31, 2025. 57,526 individuals reported across the linked filings. Data reported: Financial account, Financial credentials, Identity (basic), and 2 more. Notifications rolled out on a 6-day schedule across 10 dated filings beginning Aug 29, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
0days

Range of discovered_at dates across filings

Filing span
6days

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 clocksVermont⏱ VT AG >14 bdayDate basis✓ Clock withheld · confirmation dateWashington✓ WA AG ≤30dFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Mar 8, 2025breach begins
Jul 31, 2025discovered
Aug 29, 2025first dated filing
Sep 4, 2025most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. AUG 1IL AGIL AG noticefiling day not on record · no count stated—
  2. AUG 29CA AGCA AG noticefirst filing · no count statedday 0
  3. AUG 29WA AGWA AG notice1,371 WA residentsday 0
  4. AUG 29OR AGOR AG noticestates nationwide total 57,526day 0
  5. AUG 29NE AGNE AG noticefiling day not on record · 219 NE residents—
  6. AUG 29IN AGIN AG noticestates nationwide total 57,526day 0
  7. AUG 29MT AGMT AG notice153 MT residentsday 0
  8. AUG 29MA AGMA AG notice984 MA residentsday 0
  9. AUG 29NH AGNH AG notice309 NH residentsday 0
  10. AUG 29ME AGME AG noticestates nationwide total 57,526day 0
  11. SEP 2VT AGVT AG noticeno count stated+4d
  12. SEP 4TX AGTX AG noticemost recent · states nationwide total 57,526+6d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 8, 2025 – Jul 31, 2025
CA AG
Discovered
Jul 31, 2025· 145d undetected
IL AG + CA AG + WA AG +6
Data types
Financial account · Financial credentials · Identity (basic) · PCI · PII
IL AG + CA AG + NE AG +6
Attack vector
Unauthorized Access
CA 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)

57,526

Sum of filed state slices

9,719· 16.9% of stated

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

US57,526
TX5,675
WA1,371
MA984
IN822
NH309
NE219
ME186
MT153

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 filing12 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
Reviewed
operator-reviewed Jun 12, 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

6 days

Cadence

~1 / 0.7d

vs. multi-state median

1.0× 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. 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.