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 30, 2024 by Handala; no regulatory filing has corroborated it yet.
Handala Hacked Kashin Distillery ( One of the largest factories for the production of alcoholic beverages in the occupied territories ) +32 GB Data Dumped! https://kashin.co.il https://web.archive.org/web/202404301014...hin.co.il/ https://www.host-tracker.com/en/ic/2/e23...2f9e88cc0e PoC: https://t.me/Handala_hack/255
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.