COOPER CREEK PARTNERS MANAGEMENT LLC — April 2024 breach
One linked filing — more sources may join as they report · filed May 2, 2024. View entity profile → Other incidents for this victim →
incident inc_de3a51c16c3b4714 · merged by deterministic
Litigation Timing
Discovered → first regulatory filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Incident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- MAY 2SC AGSC AG noticeonly filing · no count statedday 0
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Apr 22, 2024 – Apr 23, 2024 SC AG
- Discovered
- Apr 22, 2024 SC AG
- Data types
- PII · Identity (basic) · Financial SC AG
- Attack vector
- Unauthorized Access SC AG
- Response
- Responded to the incident immediately upon discovery · Took steps to ensure the security of our systems · Taken steps to ensure the continuing integrity of your personal information and prevent future attackers from obtaining unauthorized access to our systems SC AG
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Evidence ladder — rungs this incident occupies
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.