ransomware

Xorist

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

Summary

Ransomware encrypted files will still have the original non-encrypted header of 0x33 bytes length

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

Recovery

Public tool under conditions

ToolVariantRecovery
Emsisoft · Xorist Decryptorverified on 11 Nov 2026whole familyconfirmed — Variants generated with the Xorist kit (extension and note vary), with a file pair; the encrypted file must be at least 144 bytes.
Trend Micro · Trend Micro Ransomware Decryptorverified on 11 Nov 2026whole familyconfirmed — Files with the .xorist extension or a random one. The tool may ask for an encrypted/original pair.

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

Guidance specific to this family. · published on 11 Nov 2026

A guide to Xorist built from the tools' official pages, read on 11 November 2026. Use it together with the general guide: containing the attack and preserving evidence come before any tool.

1. Confirm it is Xorist

  • There is no fixed sign: the kit lets the attacker choose the extension, the name and the text of the note, and the vendor does not list extensions.
  • Each family leaves a pattern in the name: .777, .locky (AutoLocky), .RSNSLocked, .LeChiffre, .purge, .xorist, .crypted, .cerber, the prefix Lock. (MirCop) and others listed in the guide.
  • Extensions cited by the sources: .73i87A, .antihacker2017, .EnCiPhErEd, .encoderpass, .fileiscryptedhard, .p5tkjw, ....PAY_IN_MAXIM_24_HOURS_OR_ALL_YOUR_FILES_WILL_BE_PERMANENTLY_DELETED_PLEASE_BE_REZONABLE_you_have_only_1_single_chance_YOU_NEED_TO_PURCHASE_THE_DECRYPTOR_FROM_US_FAST_AND_URGENT, .PoAr2w, .zc3791, .xorist.
  • Ransom notes cited by the sources: HOW TO DECRYPT FILES.TXT.
  • Different families can use the same extension. If in doubt, check the Vexday search.

2. Free tools

  • Emsisoft · Xorist Decryptor, works: Variants generated with the Xorist kit (extension and note vary), with a file pair; the encrypted file must be at least 144 bytes. Official page
  • What you need: A file pair: an encrypted file of at least 144 bytes and its original version.
  • Trend Micro · Trend Micro Ransomware Decryptor, works: Files with the .xorist extension or a random one. The tool may ask for an encrypted/original pair. Official page
  • What you need: Choose the family (or let the tool identify it from the file). For CryptXXX V1, XORIST, XORBAT and Nemucod, it may ask for an encrypted/original pair from a backup, the larger the better.
  • Limits: List of families from the 2016 guide. CryptXXX V3 may come out only partially; TeslaCrypt V1 and V2 require another tool, requested from Trend Micro support.

3. Use the tool safely

  1. Copy the encrypted files to another disk and work only on the copy. Keep the originals untouched.
  2. Download the tool only from the official page above, never from another site.
  3. Set aside a file pair: the original (from a backup, an e-mail or another machine) and the same file encrypted.
  4. Run the tool on a machine isolated from the network, following the vendor's manual.
  5. Open a few recovered files to check them before deleting anything.

Warnings the vendor highlights:

  • Remove or isolate the malware before decrypting, otherwise it may encrypt the files again.
  • Do not rename the original or the encrypted file used as the pair.
  • By default the tool keeps the encrypted files; only turn this off after checking the result.
  • CryptXXX V3 may be only partially recovered.

4. If it does not work

  • Do not delete the encrypted files or the ransom note: new keys and tools can come out later. Follow the family on Vexday to be notified.
  • Get help from an incident response team and follow the general guide to contain, recover and report the incident.
  • Paying the ransom does not guarantee you get your data back.

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: .73i87A .antihacker2017 .EnCiPhErEd .encoderpass .fileiscryptedhard .p5tkjw ....PAY_IN_MAXIM_24_HOURS_OR_ALL_YOUR_FILES_WILL_BE_PERMANENTLY_DELETED_PLEASE_BE_REZONABLE_you_have_only_1_single_chance_YOU_NEED_TO_PURCHASE_THE_DECRYPTOR_FROM_US_FAST_AND_URGENT .PoAr2w .xorist .zc3791
note: HOW TO DECRYPT FILES.TXT

source: public recovery-tool catalogue

Groups using the family

No group with a documented link.

Indicators

No indicator linked to this family.