BULLHORN, INC.
bd_dd04768079a26b7b · schema v1 · pii pii-v2
Full breach record for BULLHORN, INC. →Press / market disclosure — not a breach-notification filing
A media or market posting that confirms an incident but carries no breach-notification fields, so compliance clocks aren't assessable. The summary below is extracted from the coverage — verify against the source.
Bullhorn takes staffing platform offline to contain cyberattack. Bullhorn: The American software company Bullhorn was forced to disable access to its platform following a cyberattack that caused a widespread outage. The incident, the first signs of which were observed on Friday, October 16, 2026, was contained by the company, which isolated the threat and launched a forensic investigation. To date, it has not been determined whether customer data was exfiltrated.
P pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Oct 16, 2026
Press report
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Attack → press
—
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.
If an SEC 8-K, state-AG notice or victim statement lands, DisclosureLens merges it into an incident and links it here.
Source ceiling
- incident type + narrative only (may be machine-translated)
- discovery date
- materiality
- affected count
- data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.