CUSHMAN & WAKEFIELD, INC.
bd_f94238367dc88287 · schema v1 · pii pii-v1
Full breach record for CUSHMAN & WAKEFIELD, INC. →2 incidents on fileThreat-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
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
May 3, 2026
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?Ransomware claims (1)
- Leak Siteshinyhuntersbd_94dad4d39b7268ca2026-05-03Verified by operator
Regulatory filings (5) · sorted by filing gap
- Pressshinyhuntersbd_73d80c5e639295172026-04-29 · +4dCandidate
- Vermont State AGbd_1baa16367dbbe7a12026-08-07 · +96dVerified by operator
- New Hampshire State AGbd_27631192cebaf0702026-08-07 · +96dVerified
- California State AGbd_ad8121b21cc043a92026-08-07 · +96dVerified by operator
Show 1 more filing ↓Show fewer ↑up to 96d gap
- Massachusetts State AGbd_cdf44100b3bfaed92026-08-07 · +96dVerified by operator
Filing propagation · 6 filings · 4 states
View merged incident ↗Pattern: first filing Apr 29, last Aug 7 (MA) — a 100-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.