The Spooner Risk Control
bd_2632586931dda336 · schema v1 · pii pii-v1
Full breach record for The Spooner Risk Control →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Black Basta 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
The Spooner Risk Control family of companies was established in 1975, when Tom Spooner uprooted his youngest son from his bedroom so it could be turned into an office. What started as a labor relations and HR consulting firm has grown to offer solutions for many of the challenges that employers face today.Spooner’s journey into workers’ compensation started in 1981, when a client asked Tom to attend an Industrial Commission hearing on behalf of their company. The client felt they’d paid more than enough for this particular workers’ comp claim, but the Hearing Officer didn’t consider that a valid argument. However, the Hearing Officer suggested that Tom read the Ohio Revised Code Workers’ Compensation book, since it was clear he truly wanted to protect and help the businesses he works with. Nearly 50 years later, that remains the goal of every company under the Spooner umbrella. In 2017, Tom’s grandson Joe Spooner stepped into the role of president to ensure the company’s values continue to align with those ideals.SITE: https://spoonerinc.com Address 28605 Ranney ParkwayWestlake, Ohio 44145Phone: [REDACTED-PHONE] ext. 153
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Apr 23, 2023
Claim posted
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
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.
No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.
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.