Data Records Management Services
bd_3fbb671c42273306 · schema v1 · pii pii-v1
Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group INC Ransom 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
"Our Priority We believe that everyone deserves the right to work and play without regards to intimidation of security or data breaches. DRMS trains our professional staff in the latest techno tactics designed to defeat the predatory villains. We do this so that as our customer, you won’t have to. Join us to see how we can protect your data, servers, computer devices in addition to custom software applications allowing you to work and play with confidence." As for us they don't care about their customers privacy at all. They preferred to put their clients business and safety under the threat. Their CEO Benjamin Gurrola had a possibility to get a deal but didn't use it. Soon all sensitive data we'll be published.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
May 18, 2024
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.