Iran Internation WhatsApp and Internal Access
bd_853ac1c5a0db5187 · schema v1 · pii pii-v1
Full breach record for Iran Internation WhatsApp and Internal Access →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
You only saw the tip of the iceberg... When you first assumed that only your Telegram had been compromised, we smiled , a bitter smile. Because while you drifted in illusions of safety, we had already made a home beneath your skin. 31 months. Not a night. Not a season. For over two and a...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jul 9, 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