Ranzijn
bd_38545736ef997b5e · schema v1 · pii pii-v1
Full breach record for Ranzijn →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Raworld 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
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Mar 21, 2024
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (1) · sorted by filing gap
- Pressraworldbd_c6dc1548af6bc7702024-05-15 · +55dCandidate
Filing propagation · 2 filings
View merged incident ↗Pattern: first filing Mar 21, last May 15 — a 55-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
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.
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.
raworld
According to ransomware.live, RA Group, also known as RA World, first surfaced in April 2023, utilizing a custom variant of the Babuk ransomware.