Saban Systems
bd_60a35e2839537f39 · schema v1 · pii pii-v1
Full breach record for Saban Systems →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Handala on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
Saban Systems Hacked Saban Systems, has quietly become a central player in Israel’s expanding surveillance infrastructure. Through undisclosed agreements with Shin Bet, the nation’s internal security agency, Saban Systems has been tasked with the deployment of high-grade surveillance cameras across both public and classified sectors. The operation, internally referred to as “Silent Horizon,” involves not...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jun 19, 2025
Claim posted
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
handala
According to ransomware.live, Not a Ransomware Group