Are there any recovery options for newer Akira ransomware variants?

Start by having the DFIR team identify the specific variant rather than relying on the file extension alone. The public Avast decryptor applies to some Akira infections, but you shouldn't assume it will work on a newer one. V2 and Megazord were identified in the discussion as variants without an available decryptor, though availability can change.

Keep untouched copies of the encrypted files and forensic images. They may be useful if a suitable decryptor or key becomes available later. Test any recovery tool on copies, not the only originals.

Ask your DFIR firm to check all available backups and plan a clean rebuild. Restore data to systems that have been wiped and rebuilt, rather than assuming an encrypted machine is safe once the files are back.

Recovery may also mean accepting some data loss if the backups are incomplete and no usable key is available. Don't discard the encrypted copies just because you have to move on now.

If you've reported the incident to law enforcement, ask your case contact whether a key or decryptor is available for your organization. That's a long shot, not something to build the recovery schedule around. In the US, a local fusion center may also be able to point you toward the right contact.

Paying is another option some organizations consider, but it isn't the same as having a proven recovery method. Discuss the risks and any legal considerations with your incident response team before making that decision, and don't assume payment guarantees usable data.

While looking for a decryptor, make sure the access route is being addressed too. Compromised SSL VPN credentials were suspected in one investigation described in the source material. Your DFIR team can check whether that fits your incident and help contain any access that remains.