ransomware

CryptoMix

Also known as: Zeta

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

Summary

Ransomware

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
Avast · CryptoMix Decryptorverified on 11 Nov 2026whole familyconditional — Only files encrypted with the offline key; extensions .CRYPTOSHIELD, .rdmk, .lesli, .scl, .code, .rmd, .rscl and .MOLE (the Mole variant was added in July 2017).
CERT-PL · CryptoMix Decryptorverified on 11 Nov 2026whole familyconditional — Only vulnerable versions of CryptoMix/CryptFile2, and not always. The CERT-PL tool is no longer public: it must be requested from CERT-PL by sending an encrypted file without renaming it.

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 CryptoMix 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 CryptoMix

  • Files get one of these extensions: .CRYPTOSHIELD, .rdmk, .lesli, .scl, .code, .rmd, .rscl or .MOLE.
  • CERT-PL cites encrypted file names in the pattern name.ext.email(...)id(...).lesli; CryptoMix (formerly called CryptFile2) asks for contact by e-mail and has no payment portal.
  • Extensions cited by the sources: .0000, (16 uppercase hex).SYS, .BACKUP, .code, .CRYPTOSHIEL, .CRYPTOSHIELD, .email(supl0@post.com)id(\((a-z0-9){16}\)).lesli, .EMPTY, ***filename*.email(*email*)_id(*id*).rdmk, .id_*_email_zeta@dr.com**.
  • Ransom notes cited by the sources: C:\ProgramData\(random).exe, # HELP_DECRYPT_YOUR_FILES #.TXT, _HELP_INSTRUCTION.TXT, INSTRUCTION RESTORE FILE.TXT.
  • Different families can use the same extension. If in doubt, check the Vexday search.

2. Free tools

  • Avast · CryptoMix Decryptor, works under conditions: Only files encrypted with the offline key; extensions .CRYPTOSHIELD, .rdmk, .lesli, .scl, .code, .rmd, .rscl and .MOLE (the Mole variant was added in July 2017). Official page
  • What you need: Windows computer. According to Avast's general guide, a file pair (an original and its encrypted copy) is only requested when the password needs to be cracked.
  • Limits: Only files encrypted with the offline key (used when the ransomware could not reach the server). Without it, the tool recovers nothing and changes nothing.
  • CERT-PL · CryptoMix Decryptor, works under conditions: Only vulnerable versions of CryptoMix/CryptFile2, and not always. The CERT-PL tool is no longer public: it must be requested from CERT-PL by sending an encrypted file without renaming it. Official page
  • What you need: Request the tool from CERT-PL (official e-mail or incident form), attaching a single encrypted file with its name intact.
  • Limits: Only decrypts vulnerable versions of CryptoMix/CryptFile2, and not always. CERT-PL says its decryptors are outdated, do not work on modern ransomware and are no longer public.

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. Run the tool on a machine isolated from the network, following the vendor's manual.
  4. Open a few recovered files to check them before deleting anything.

Warnings the vendor highlights:

  • Only recovers files encrypted with the offline key; the others are left unchanged.
  • Avast recommends keeping the backup of the encrypted files turned on.
  • Decryption only works sometimes and only on vulnerable versions.
  • CERT-PL warns that its decryptors are outdated and do not work for modern ransomware.

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: .0000 [16 uppercase hex].SYS .BACKUP .code .CRYPTOSHIEL .CRYPTOSHIELD .email[supl0@post.com]id[\[[a-z0-9]{16}\]].lesli .EMPTY *filename*.email[*email*]_id[*id*].rdmk .id_*_email_zeta@dr.com .id_(ID_MACHINE)_email_anx@dr.com_.scl .id_(ID_MACHINE)_email_xoomx@dr.com_.code .lesli .MOLE .MOLE66 .rdmk .rmd .rscl .scl .SYSTEM .TEST .WORK .XZZX
note: C:\ProgramData\[random].exe # HELP_DECRYPT_YOUR_FILES #.TXT _HELP_INSTRUCTION.TXT INSTRUCTION RESTORE FILE.TXT

source: public recovery-tool catalogue

Groups using the family

No group with a documented link.

Indicators

6 indicators linked to this family

  • md5_hash · 2e8492a32f89e12a22c4095b0125d44f · community indicator feed
  • sha256_hash · d19a473410153f49f958a27f49ad18317edcb8c1e994441fd0999ea0acc35fc2 · community indicator feed
  • sha1_hash · d2e3438b30864ba678a4693c007f3ae6e619ecf9 · community indicator feed
  • sha1_hash · 2642793ff2d309549f221170a975eceeb1d53143 · community indicator feed
  • md5_hash · a77368c5258b9aef928dcc27fb2c26a4 · community indicator feed
  • sha256_hash · bf3714398b7b46038bddff63a67d7c3ad2aabc1b996ec156d7ec335937f80c53 · community indicator feed