Skip to content

Anubis Ransomware Recovery: What's Recoverable

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

Anubis has been active since December 2024 as a ransomware-as-a-service operation, running affiliate programs with revenue splits from 50% to 80%, plus a separate program for affiliates who only want help monetizing data they've already stolen. Confirmed victims span healthcare, construction and other sectors across Australia, Canada, Peru and the United States.

Encryption, and an optional wiper

File content is encrypted using ECIES (Elliptic Curve Integrated Encryption Scheme), via a Go-based implementation similar to one used by EvilByte/Prince ransomware, with files renamed to a .anubis extension. The detail that sets Anubis apart is a separate /WIPEMODE flag: rather than encrypting, it truncates a file's contents to zero bytes — permanently destructive rather than reversible with a key.

What this means for recovery

This is the one distinction that changes everything about what's realistic: if a file was wiped rather than encrypted, no decryption key — leaked, purchased or otherwise obtained — brings back content that no longer exists in that copy. Recovery for a wiped file depends entirely on sources outside the ransomware itself: backups, snapshots, shadow copies or an unaffected replica. Establishing which behaviour actually happened, file by file, is the first thing an assessment needs to determine before anything else about the case can be judged.

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

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.

Facing this problem? 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

Request assessmentEmergency