Skip to content

Phobos Ransomware Recovery: Free Decryptor, What It Covers, and What to Do When It Fails

By Srinivasan Krishnappa · Ransomware & database recovery engineer · 656+ ransomware recoveries
6 min read
Need this solved now? We have already solved 656+ ransomware and data recovery cases. Call +91 74187 05822 (US +1 917 695 5194), WhatsApp us or email info [at] asittech.com. Free assessment; no data, no charge.

Phobos is a ransomware-as-a-service family active since 2018 and one of the most common in small and mid-size businesses, schools, hospitals and local offices. The US CISA, FBI and MS-ISAC described it in their joint advisory AA24-060A (February 2024): affiliates usually get in through exposed or weakly protected Remote Desktop (RDP), and use common tools such as SmokeLoader and Cobalt Strike.

Encrypted files are renamed in a recognisable pattern: the original name, an .id[XXXXXXXX-XXXX] tag, the attacker's e-mail address in brackets, and an extension. Many extensions are in use, including .phobos, .eking, .eight, .elbie, .faust, .devos, .LIZARD and .8base (8Base was a group built on Phobos). The ransom note is usually info.hta and info.txt.

There is a free Phobos decryptor: use it first, on a copy

In July 2025 Japan's National Police Agency released a free decryptor for Phobos and 8Base, developed with the FBI and tested with Europol. It is available from the police website and from No More Ransom. Files ending in .phobos, .8base, .elbie, .faust and .LIZARD are listed, and other Phobos variants may work too.

Always run it on copies of the encrypted files, never on the only copy, and download it only from the official sites: fake "Phobos decryptors" are a common trap. The tool is not a universal master key, so some incidents are not covered.

When the decryptor does not work

We have recovered Phobos cases ourselves, including ones where the decryptor did not help. If the variant is not covered or the decryption fails, the data is not automatically lost. Very large files such as SQL Server databases, virtual disks and backups are often not encrypted end to end, and the parts that were not encrypted can be read directly. We recover the tables of an encrypted MDF or BAK from the database pages that survived, and virtual machines and files from partly encrypted VMDK, VHDX and backup files.

Keep the encrypted files exactly as they are, do not run repair tools on them, and copy them before trying anything. Then send us a sample for a free assessment. No data, no charge.

Stop the next attack

Phobos is opportunistic: it goes where RDP is open to the internet with weak passwords. Close RDP to the internet or put it behind a VPN with multi-factor authentication, use long unique passwords, lock out repeated failed logins, and keep at least one backup offline where a compromised server cannot reach it.

Veeam backups, SQL Server or Oracle databases encrypted by Phobos?

Ransomware groups go after the backup repository first. A .vbk or .vib file renamed by the ransomware is often not lost: large backup files are usually only partly encrypted, and the intact blocks can be verified and rebuilt into the virtual disks. The same holds for SQL Server MDF and BAK files and for Oracle datafiles and Data Pump exports: the rows the ransomware did not reach can be read directly. In real cases we rebuilt a 466 GB server disk from a 43 GB Akira-encrypted VBK, and recovered 98.8% of the rows from LockBit-encrypted SQL Server backups.

Phobos ransomware data recovery: contact us now

We have already solved 656+ ransomware and data recovery cases: encrypted and corrupted SQL Server, Oracle and MySQL databases, Tally, Busy and Marg ERP data, Veeam backups, VMware and Hyper-V virtual machines, RAID and NAS. Send us the details and we tell you what we can recover.

  • ✓ Free assessment before you pay anything
  • ✓ No data, no charge
  • ✓ NDA on request

Email: info [at] asittech.com · Mon–Fri, 9:00–18:00 IST

Call 24/7Emergency