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 Jul 9, 2025 by Handala; no regulatory filing has corroborated it yet.
Mojtaba, Are you still under the illusion that the Stables Rectory Farm meeting in Halstead was private? Every word spoken there was recorded , in full, high-fidelity, multi-channel format. Has James, your Mossad handler, told you yet? Does he know that the March meeting was a staged intel trap? You may be surprised to learn:...
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.