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 7, 2026 by Handala; no regulatory filing has corroborated it yet.
Ms. Vered Haimovich, Tonight, there’s nowhere left to hide; The shadows see everything, and it’s time for the truth to be revealed. You, a retired Air Force Colonel, now handpicked by Eyal Zamir, the IDF Chief of Staff, to lead the ultra-secret Squadron 166, are directly responsible for planning, directing, and executing drone operations against...
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.