Skip to content

Rhysida 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.

Rhysida surfaced in May 2023 and was significant enough that CISA and the FBI issued a joint advisory (AA23-319a) that November. It's a ransomware-as-a-service operation running the standard double-extortion playbook — encrypt, then threaten to leak — against healthcare, education, government and critical infrastructure targets across roughly 25 countries, most heavily in the United States.

Credential access, then deliberately partial encryption

Rhysida affiliates favour logging in over breaking in: valid or compromised credentials against externally facing services, particularly VPNs without multi-factor authentication, are the primary route, with Cobalt Strike used for lateral movement afterward. Encryption itself uses ChaCha20 for file content, with the ChaCha20 keys and initialization vectors wrapped in 4096-bit RSA, and appends a .rhysida extension. Notably, Rhysida uses periodic (intermittent) encryption — deliberately encrypting only sections of a file rather than the whole thing, both to move faster across a network and to evade detection tools that flag full-file encryption patterns.

What this means for recovery

That periodic-encryption behaviour is the detail that matters most for recovery: because Rhysida is skipping sections rather than encrypting exhaustively, larger files — databases, virtual disks, backup archives — often retain substantial unencrypted content even though the file as a whole reports as encrypted. Establishing how much of a given file survived intact is exactly what a technical assessment does before anything else. On the containment side, checking VPN and remote-access logs for the credential misuse this group relies on is worth doing alongside — not instead of — the recovery assessment.

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

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