Acadian Ambulance
Clustered 2 filings across 1 jurisdiction · filed Jul 22, 2024. View entity profile → Other incidents for this victim →
incident inc_3a31d8a300944a16 · merged by deterministic · confidence 0%
Unverified threat-actor claim — not a regulatory filing
Attribution, victim identity, and counts shown here derive from a threat actor's public extortion-blog claims, aggregated by ransomware.live. They have not been validated by the victim or any regulator. Treat them as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Litigation Timing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
Member cascade — every filing about this breach
- JUL 22Leak sitedaixin postonly record · attacker claim · unverifiedday 0
- Watching: SEC 8-K · state-AG notices · victim statement. (day 787 of watch).
Roll-up facts — reconciled across members
- Breach window
- —
- Discovered
- —
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Evidence ladder — rungs this incident occupies
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
No regulator filing linked yet.
No SEC filing or victim statement yet.
Merge provenance
- Method
- deterministic
- Confidence
- 0.00 · below the 0.85 auto-merge floor
- Audit
- Every link edge records its method, confidence and model + prompt versions (0% is the strongest edge).
Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.
Filing velocity
Spread
28 days
vs. multi-state median
3.5× 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.