Cardinal Services — June 2025 breach
Clustered 13 records across 11 jurisdictions: 11 filings and 2 leak-site claims · filing window May 20, 2026 → May 27, 2026 (dated filings only). View entity profile → Other incidents for this victim →
incident inc_ec81c19d43bc4ffa · merged by human · confidence 100%
Litigation Timing
SupplementalDiscovered → first regulatory filing
Range of discovered_at dates across filings
Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
Sensitive data
identity_governmentIncident timeline
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 and leak-site claim in this incident
- JUL 15Leak siterhysida postfirst record · attacker claim · unverifiedoperator-confirmedday 0
- AUG 10Leak siteinc_ransom postattacker claim · unverifiedoperator-confirmed+25d
- MAY 20CA AGCA AG noticeno count statedoperator-confirmed+308d
- MAY 20WA AGWA AG notice2,066 WA residentsoperator-confirmed+308d
- MAY 20NE AGNE AG noticefiling day not on record · no count statedoperator-confirmed—
- MAY 20VT AGVT AG notice9 VT residentsauto-linked+308d
- MAY 20IN AGIN AG noticestates nationwide total 142,323auto-linked+308d
- MAY 20MT AGMT AG notice252 MT residentsoperator-confirmed+308d
- MAY 20ME AGME AG noticestates nationwide total 142,323operator-confirmed+308d
- MAY 20MA AGMA AG notice32 MA residentsoperator-confirmed+308d
- MAY 22TX AGTX AG noticestates nationwide total 142,323operator-confirmed+310d
- MAY 26NH AGNH AG notice9 NH residentsoperator-confirmed+314d
- MAY 27OR AGOR AG noticemost recent · states nationwide total 128,551operator-confirmed+315d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Jun 25, 2025 – Aug 8, 2025 CA AG
- Discovered
- Jun 30, 2025WA AG + MT AG + MA AG +2May 12, 2026ME AG + TX AGfilings disagree on discovery
- Data types
- Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII CA AG + WA AG + NE AG +6
- Attack vector
- Ransomware 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)
142,323
Sum of filed state slices
2,785· 2.0% of stated
98% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.
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
Attacker assertion only. Establishes: claim date, group, alleged victim.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
Merge provenance
- Method
- human
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- Reviewed
- operator-reviewed Sep 30, 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
7 days
Cadence
~1 / 0.8d
vs. multi-state median
1.2× 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.