Dediserve Ltd
bd_173b927f096b864f · schema v1 · pii pii-v2
Full breach record for Dediserve Ltd →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group N0n 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
Cloud infrastructure provider (iomart group) · Dublin, Ireland / FRA1 Frankfurt DC | The complete customer register of the FRA1 cloud — 167 tenant accounts with infrastructure details; Disk images of tenant servers: a regulated forex broker's portal (payment gateway configuration, trading-account records), a payment services provider's systems including its internal password vault, and a production real-estate platform; The provider's internal operations mailbox and monitoring configuration | All 46 FRA1 servers are paused and intact - restorable automatically within the hour of settlement. | [ACTIVE: deadline 2026-10-01 05:16 UTC]
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Sep 28, 2026
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.