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 Jan 3, 2026 by Handala; no regulatory filing has corroborated it yet.
The Queen’s Secrets: Unveiling the Mysteries Behind Ayelet Shaked Once again, the cyber world has witnessed the true extent of our power! This time, our target was none other than Ayelet Shaked, the controversial figure and so-called security champion of the Zionist regime. Her iPhone 15 Pro, supposedly the pinnacle of advanced technology and personal...
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.