Skip to main content

Ransomware victim disclosure

All victims

DINI

Claimed by CRY0 · listed 2 months ago

59d
Age
since listed · listed for ransom

Status timeline

  1. ListedMay 17, 2026

Current state: Listed for ransom

At a glance

Group
CRY0
Status
Listed for ransom
Listed on leak site
May 17, 2026

About the victim

AI dossier — public-source company profile

DINI is described as a family-run transportation and automotive business. Beyond this characterization from the leak post, no further details about its location, scale, or specific services are publicly available. The company's country of operation is currently unknown.

Industry
Transportation & Automotive Services

Attack summary

Severity: low — This is an initial listing only with no proof files, no stated ransom, no confirmed data exfiltration, no data volume, and no operational impact described. Minimal verifiable information is available.

The CRY0 ransomware group has listed DINI on their leak blog, claiming an attack on the company. No specific details about encryption, exfiltration, data volume, or ransom demand have been disclosed in the available post excerpt.

low

What the group claims

A family-run transportation and automotive business

The leak post

captured from the group's site
cry0 Team Blog - Home
This is a cry0 Team Blog. Select a post to read.
DINI is a family-run transportation and automotive business base...

Screenshot of the leak post

Leak screenshot for DINI

Sources

Source

Indexed 2 months ago

This page surfaces a public ransomware disclosure indexed by Darkfield. Original posts come from the operator's own leak site; we cross-check against ransomware.live, RansomLook and RansomWatch where applicable. Share this URL freely.

Is this your supplier? Your competitor? You?

Pro plans monitor your domain, corporate emails, and crypto wallets across every new ransomware leak-site post, breach dump and Telegram callout — alerts within 5 minutes.

Disclosure context

About CRY0

CRY0 is a ransomware group first observed in May 2026 with an apparent financial motivation, though its limited activity to date makes comprehensive attribution difficult. With only a single confirmed victim recorded and a targeting pattern focused on the transportation and automotive sectors, the group remains nascent and has not yet accumulated sufficient operational history to establish a well-documented profile in open-source intelligence reporting by organizations such as CISA, the FBI, Mandiant, or comparable security research firms. No confirmed country of origin, RaaS affiliation, or links to established threat actor clusters have been publicly documented at this time. Similarly, specific details regarding initial access vectors, tooling, encryption methodologies, or data exfiltration practices have not been publicly attributed to CRY0 by reputable sources, and no notable high-profile campaigns, record ransom demands, or law enforcement actions have been recorded against the group. Given its emergence in May 2026 and minimal victim count, CRY0 should be regarded as an emerging and unverified threat actor warranting continued monitoring, particularly within transportation and automotive industry verticals, as future activity may yield more substantive intelligence to support a fuller threat assessment. The group has been linked to 2 public disclosures across our corpus. First observed on a leak site on May 17, 2026; most recent post July 6, 2026. The operation is currently active.

Timeline of this disclosure

  • May 17, 2026DINI listed by CRY0on the group's public leak site

Sector and geography

This disclosure adds to ransomware activity in the Transportation and Automotive sector.

If your organisation is affected

A listing by CRY0 means DINI appeared on a ransomware extortion site and is being pressured to pay before any publication. If this is your organisation, or a supplier you depend on, the priority is to confirm the intrusion and contain it before the window to act closes.

  • Engage your incident-response team and preserve forensic evidence before remediating — do not wipe affected systems first.
  • Force a password reset and revoke active sessions for exposed accounts; rotate any credentials, API keys or certificates that may have been in the stolen data.
  • Assess regulatory notification duties (GDPR, NIS2, sector regulators) — many carry a 72-hour reporting clock from awareness.
  • Monitor for the data appearing on CRY0's leak site and across paste and breach channels, and brief downstream partners who may be exposed through you.

How we know this. Darkfield monitors public ransomware leak sites continuously, archiving every new disclosure and the data later released against the victim. Each entry on this page is sourced from the operator's own publication and cross-checked against complementary OSINT feeds (RansomLook, ransomware.live, RansomWatch). We do not collect or host stolen data — only the metadata, timestamps and screenshots needed to make the public disclosure searchable and accountable. Records here are corrected when the original post is edited, retracted, or merged with another disclosure.