Unverified threat-actor claim — not a regulatory filing
Attribution, victim identity, and counts shown here derive from a threat actor's public extortion-blog claims, aggregated by ransomware.live. They have not been validated by the victim or any regulator. Treat them as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Unverified claim. Posted to a leak site Apr 18, 2023 by ALPHV; no regulatory filing has corroborated it yet.
incident inc_88f3c15553d54c81 · merge_method human · confidence 100%
Litigation Timing
Filing span
10days
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
Leak SiteUnverified claimLifecycle stage 1 of 3: Unverified claimUnverified claimConfirmedEnforcedalphv
Affected (total reported)
—
Data types
—
Jurisdictions
2
FEDERAL
Linked filings
2
all Leak Site
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
🌐GLOBALClaimed by ALPHV / BlackCatFirst sightinglinked via operator-confirmed · 100%
Western Digital Corporation is an American computer drive manufacturer and data storage company, headquartered in San Jose, California. It designs, manufactures and sells data technology products, including data storage devices, data center systems and cloud storage services.
🌐GLOBALClaimed by ALPHV / BlackCatMost recentlinked via operator-confirmed · 100%
Western Digital Corporation is an American computer drive manufacturer and data storage company, headquartered in San Jose, California. It designs, manufactures and sells data technology products, including data storage devices, data center systems and cloud storage services.
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.