ransomware

RansomEXX

Also known as: Defray 2018, Defray777, Ransom X

Alert when a public recovery tool comes out, when compatibility changes and when a new variant appears.

Summary

We recently discovered a new file-encrypting Trojan built as an ELF executable and intended to encrypt data on machines controlled by Linux-based operating systems. After the initial analysis we noticed similarities in the code of the Trojan, the text of the ransom notes and the general approach to extortion, which suggested that we had in fact encountered a Linux build of the previously known ransomware family RansomEXX. This malware is notorious for attacking large organizations and was most active earlier this year. RansomEXX is a highly targeted Trojan. Each sample of the malware contains a hardcoded name of the victim organization. Moreover, both the encrypted file extension and the email address for contacting the extortionists make use of the victim’s name.

Text from the open source (public malware catalogue or MITRE ATT&CK), unedited: it may be outdated or cover only one variant.

Recovery

No known public tool

Before any tool

  • Preserve the encrypted files, the ransom note and any backups before trying anything.
  • Test the tool on a copy of the files, in an isolated environment, following the vendor's instructions.
  • A decryptor for the family does not guarantee recovery for every variant.

Recovery guide

General guidance, valid for any family. · published on 10 Nov 2026

General guidance for the first hours, valid for any family. It does not replace an incident response team.

1. Contain

  • Disconnect the affected machines from the network (cable and Wi-Fi). If you cannot isolate them, shut them down to stop the spread.
  • Disconnect the backups too and check that they were not encrypted.
  • Change the passwords of administrative, VPN and service accounts from a clean machine: attackers usually hold stolen credentials.

2. Preserve the evidence

  • Do not delete the encrypted files or the ransom note. They identify the family, and a tool may appear later.
  • Keep the logs (firewall, VPN, domain controller, antivirus or EDR) and, if possible, a copy of the disks and memory of the affected machines.
  • Write down what happened and when: the timeline helps the investigation and the notifications.

3. Identify the family

  • Look the family up in the Vexday search by file extension, ransom note file name or sample hash.
  • Check whether a free tool exists on No More Ransom and on the vendor's official page.
  • A tool works for the family and sometimes only for some variants. Always test it on a copy of the files, in an isolated environment, following the vendor's instructions.

4. Recover safely

  • Restore from verified backups, only after removing the attacker's access. Restoring earlier can reinfect the environment.
  • When in doubt, rebuild the compromised machines from a trusted image.
  • Paying the ransom does not guarantee that the data comes back or that it will not be published.

5. Report the incident

  • Personal data: check your country's data protection law; many require notifying the authority and the data subjects within short deadlines.
  • National CSIRT: report the incident to your country's CSIRT or CERT.
  • Police: file a report with the cybercrime unit.
  • Cyber insurance: tell the insurer before hiring incident response; many policies require it.

Under attack: who to call

In Brazil, besides the CSIRTs
  • Personal data involved: notify the ANPD. Under the LGPD (art. 48), the controller notifies the ANPD and the data subjects of an incident that may cause relevant risk or harm, within 3 business days (ANPD Resolution CD/ANPD No. 15/2024). The data protection officer files it through SEI!ANPD. How to notify the ANPD
  • File a police report. Ransomware is a crime. Many states have police units specialized in cybercrime; keep the ransom note and the encrypted files as evidence.

CSIRTs · Brazil

The country's incident response teams (CSIRTs), from the ENISA and FIRST lists. Each one serves a constituency: check it before writing.

Another country: Argentina · Chile · Colombia · Costa Rica · Dominican Republic · Ecuador · Spain · Guatemala · Mexico · Panama · Peru · Portugal · El Salvador · Uruguay · Venezuela

Source: ENISA and FIRST lists · updated on 16 Nov 2026

Variants

No variant cataloged.

Extensions and ransom notes

extension: .0s .<abbreviated_company_name> <company_name> .dbe .<org_name> .txd0t
note: <abbreviated_company_name> _READ_ME! .txt TXDOT_READ_ME! .Txt

Groups using the family

  • ransomexx operates the family · corroborated, high confidence

Victims of the groups

6 known victims of the groups that operate or use the family, 2 in Brazil.

The leak site publishes the victim with the group, not the family. A group that runs more than one family shows up on all of them: the victim belongs to the group, and the family used in that attack is not reported.

Most recent
Name hiddenransomexx · Healthcare · VE · 21 Dec 2024
Name hiddenransomexx · Technology · MX · 14 Sep 2024
Name hiddenransomexx · Government & Defense · PE · 24 Mar 2024
Name hiddenransomexx · Education · BR · 03 Sep 2022
Name hiddenransomexx · Technology · EC · 12 Jul 2021
Name hiddenransomexx · Government & Defense · BR · 03 Nov 2020
Available on the SOC, MSSP and Enterprise plans

Here, the victims' names are hidden: the list shows the group, the sector, the country and the attack date.

These plans unlock the raw intelligence that stays closed on the site:

  • the addresses of the groups' leak and negotiation sites;
  • the victims' names;
  • the full negotiation chat;
  • each group's YARA rules and full detection package;
  • the criminals' contacts (email, .onion, Tox) unmasked.

They also include webhook, Slack and Discord alerts, the MCP for AI assistants and more API volume. Enterprise is by request.

See the plans
Most affected sectors

Government & Defense (2) · Technology (2) · Education (1) · Healthcare (1)

Detection

The detection packages of the groups that operate or use the family: the indicators (IOCs) and YARA rules from open intelligence, to hunt for the group in your own environment. The package is published per group, not per family.

Source: open intelligence on the groups. The YARA rules and the full package are on the SOC, MSSP and Enterprise plans.

U.S. Treasury sanctions (OFAC)

OFAC press releases that sanction people or companies and tie them, in the text itself, to this family or to the groups that operate or use it.

  • 20 Feb 2024 · United States Sanctions Affiliates of Russia-Based LockBit Ransomware GroupIvan Gennadievich Kondratiev (Bassterlord), Artur SungatovFrom the press release: “Artur Sungatov, a Russian national, is a Lockbit ransomware group affiliate and has actively engaged in LockBit ransomware attacks.” “he also has ties to REvil, RansomEXX and Avaddon ransomware groups”

According to OFAC, facilitating a ransom payment to sanctioned people or companies may violate U.S. sanctions. OFAC advisory. Not legal advice.

Indicators

No indicator linked to this family.