People search Kroll data breach timeline because regulated data and trust are existential—one incident triggers class actions and regulator exams. BreachHistory indexes 1 Kroll-linked incident (1 company-confirmed). This page maps every attested event through 2026 with internal links to canonical records.
Why Kroll breach history matters
Kroll operates in Financial Services (United States). Across indexed rows, recurring themes include unverified actor or scraping claims. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2023 — T-Mobile SIM swap on employee; FTX, BlockFi & Genesis bankruptcy claimant data stolen
Verified breach. On August 19, 2023 Kroll confirmed a T-Mobile SIM-swapping attack transferred a Kroll employee's phone number to a threat actor without company authorization, enabling access to files containing personal information of bankruptcy claimants in the BlockFi, FTX, and Genesis restructuring matters Kroll administered. FTX and BlockFi disclosed the breach to customers August 2023; Genesis privately notified customers per CoinDesk reporting. KrebsOnSecurity and The Record documented immediate FTX-themed phishing emails ur Exposed categories include Personal information of bankruptcy claimants across FTX, BlockFi, and Genesis estates administered by Kroll—names and contact details per victim notices; downstream phishing/SIM-sw. No attested victim count is published for this row yet. See the kroll-sim-swap-bankruptcy2023 and canonical BreachHistory entry.
Patterns and analysis
- Unverified actor or scraping claims — appears across multiple Kroll catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Freeze credit and enable fraud alerts if notification letters cite SSN or account numbers.
- Step 5: Bookmark the Kroll company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/kroll · Latest: kroll-sim-swap-bankruptcy2023.
Sources: BreachHistory catalog (1 row for Kroll), company and regulator disclosures cited in individual breach records.