ransomware

Linux.Encoder

Also known as: Linux.Encoder.{0,3}

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

Summary

Ransomware Linux 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
Bitdefender · Linux.Encoder.1 Decryptorverified on 11 Nov 2026whole familyconditional — Only the Linux.Encoder.1 variant (.encrypted files); all encrypted files must be kept to find the seed.
Bitdefender · Linux.Encoder.3 Decryptorverified on 11 Nov 2026whole familyconditional — Only the Linux.Encoder.3 variant (.encrypted files); the key is embedded in each encrypted file.

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 Linux.Encoder 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 Linux.Encoder

  • On Linux servers, encrypted files get the .encrypted extension.
  • Files with the .encrypted extension on Linux systems.
  • Different families can use the same extension. If in doubt, check the Vexday search.

2. Free tools

  • Bitdefender · Linux.Encoder.1 Decryptor, works under conditions: Only the Linux.Encoder.1 variant (.encrypted files); all encrypted files must be kept to find the seed. Official page
  • What you need: Do not delete any encrypted file; run the scripts (bash and Python) that sort the files by encryption time and find the key seed.
  • Limits: The malware does not preserve file owner and group, which may break something. Files that fail require repeating the process with the error list.
  • Bitdefender · Linux.Encoder.3 Decryptor, works under conditions: Only the Linux.Encoder.3 variant (.encrypted files); the key is embedded in each encrypted file. Official page
  • What you need: Python; the script runs one file at a time, for each file you want to decrypt.

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:

  • Do not delete any encrypted file before finishing.
  • File owner and group are not restored; adjust the permissions afterwards.
  • Check the decryption before removing the .encrypted files.

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

No extension or note cataloged.

Groups using the family

No group with a documented link.

Indicators

No indicator linked to this family.