Sprague & Jackson
bd_0a2e9089ab17d00b · schema v1 · pii pii-v1
Full breach record for Sprague & Jackson →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Qilin on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
Sprague & Jackson, USA - Sprague & Jackson is a tax services firm that offers a range of client services including secure document submission and payment options. They provide personalized assistance through scheduled meetings to help clients ...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Oct 15, 2025
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (6) · sorted by filing gap
- Indiana State AGbd_495e0dc3516989212026-05-26 · +223dVerified by operator
- Maine State AGbd_561e93a40a8335c42026-05-26 · +223dVerified by operator
- Nebraska State AGbd_7e07aad731fd91e92026-05-26 · +223dVerified by operator
- Vermont State AGbd_fb13980c6ccc84fd2026-05-26 · +223dVerified by operator
Show 2 more filings ↓Show fewer ↑up to 230d gap
- New Hampshire State AGbd_6753b906fd0020062026-06-01 · +229dVerified by operator
- Massachusetts State AGbd_0608e24a308b2a762026-06-02 · +230dVerified by operator
Filing propagation · 7 filings · 6 states
View merged incident ↗Pattern: first filing Oct 15, last Jun 2 (MA) — a 230-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
qilin
According to ransomware.live, Qilin ransomware was first observed in July of 2022. Qilin Ransomware is written in Golang and supports multiple encryption modes; all of which are controlled by the operator. Qilin actors practice double extortion – demanding payment for a decryptor, as well as for the non-release of stolen data.