Skip to main content

Hit by ransomware? Isolate affected systems now. Do not reboot or reformat.

SheMo Noransom舍末无勒

Ransomware family

Akira Ransomware Decryption & Data Recovery

  • Active
  • Critical
  • Some versions decryptable

Akira is a ransomware-as-a-service operation that emerged in March 2023, breaking in through VPNs without MFA and edge-device flaws, then encrypting Windows estates and VMware ESXi clusters under double extortion. CISA's November 2025 advisory update calls it an imminent threat to critical infrastructure.

First seen
2023-03
File extensions
.akira .powerranges .akiranew
Ransom notes
akira_readme.txt
Affected platforms
Windows / Linux / VMware ESXi

Family profile

File extensions
  • .akira
  • .powerranges
  • .akiranew
  • .aki
Ransom notes
  • akira_readme.txt
  • fn.txt
Contact patterns
  • Tor negotiation site + per-victim login code
  • No mailbox and no wallet address in the note
  • Akira leak site (retro terminal interface)
Aliases / versions
Akira_v2、Megazord、Storm-1567、Howling Scorpius、Punk Spider、Gold Sahara
First seen
2023-03
Status
Active
Threat level
Critical
Affected platforms
  • Windows
  • Linux
  • VMware ESXi
Tags
  • Leak-site regular
  • Active
  • Ransomware-as-a-Service
  • Double extortion
  • Targets virtualization
  • Exploits vulnerabilities
  • RDP brute force
Decryptor
Some versions decryptable

Only a few early Akira builds have a viable free decryption path. Current builds do not.

  • In mid-2023, Avast released a decryptor for early Akira samples (a Windows tool at release, which Avast said could also handle files encrypted by the Linux build). It recovers keys from a matched pair of the same file before and after encryption, and works best with large files. Builds seen after July 2023 are not covered.
  • In March 2025, researcher Yohanes Nugroho published a GPU brute-force tool for the Linux/ESXi variant (Akira Linux v3), which seeded keys from nanosecond timestamps. It requires a reasonably narrow known encryption time window and substantial GPU time. The author notes a newer build fixed the flaw.
  • Akira_v2, covered by the November 2025 CISA/FBI joint advisory update, uses ChaCha20 with RSA key wrapping and has no public decryption method.

Every case therefore starts with sample and file-header analysis to pin down build and encryption timestamp before either path can be ruled in or out. No blanket promise of decryption is possible.

Sources

Latest activity

  1. Huntress: an Akira affiliate entered via an MFA-less SonicWall VPN, rebooted hosts into Safe Mode with Networking to disable EDR, and kept AnyDesk alive there. Encryption failed, but files were exfiltrated in 5 hours.

    Sources
  2. Arctic Wolf saw Akira affiliates log into SonicWall SSL VPN accounts with OTP MFA enabled, likely using OTP seeds stolen in earlier intrusions. Patching CVE-2024-40766 is not enough; reset VPN credentials and seeds.

    Sources
  3. GuidePoint Security: since mid-July 2025 Akira has used BYOVD — loading ThrottleStop's legitimate rwdrv.sys for kernel access, then hlpdrv.sys to disable Microsoft Defender via the registry before deploying the encryptor.

    Sources

Overview

Akira surfaced publicly in March 2023. Its operators are tracked as Storm-1567, Howling Scorpius, Punk Spider and Gold Sahara, and both code and personnel are assessed to have links to the defunct Conti syndicate. It runs as a ransomware-as-a-service business: a core team maintains the encryptor and leak site, affiliates handle intrusion and deployment, and proceeds are split. The retro green-on-black terminal styling of its leak site is one of the family's most recognisable signatures.

CISA, the FBI, DC3 and international partners first published the #StopRansomware advisory AA24-109A in April 2024 and issued a substantial update on 13 November 2025, reporting roughly USD 244 million in claimed ransom proceeds and describing Akira as an imminent threat to critical infrastructure. Public tracking put Akira's 2025 leak-site postings close to a thousand organisations, and through 2026 it has stayed in the top tier of global operations alongside Qilin and DragonForce.

By sector, Akira concentrates on manufacturing, education, information technology, healthcare, financial services and food and agriculture, with a clear preference for small and mid-sized firms — organisations that typically run a full virtualisation stack but lack MFA, log retention and offline backups.

For organisations in China and the wider region the relevance is in the attack surface rather than the branding: Akira's favoured entry points (VPN accounts without second-factor authentication, unpatched Cisco/SonicWall/Fortinet edge devices, exposed Veeam backup servers) map closely onto common enterprise network designs, and its ability to encrypt VMware ESXi and even Nutanix AHV matches the widespread "one hyperconverged cluster runs everything" pattern in manufacturing and hospitals. Chinese vendors and community outlets have tracked Akira's Cisco VPN intrusions since 2023.

How to identify it

Extensions. Most samples rename files to the original name plus .akira; the Megazord branch uses .powerranges, and .akiranew / .aki also appear. The Linux/ESXi encryptor appends .akira as well, concentrating on .vmdk, .vmx and .vmsn virtual-machine files.

Ransom note. akira_readme.txt is dropped in the root and user directories; some builds use fn.txt. The text opens casually, claims data theft, and notably supplies no email address and no wallet address — only a Tor onion URL and a victim-specific login code. That is a clear differentiator from mail-based families such as Phobos or GlobeImposter.

Host-side artefacts.

  • PowerShell calls against Win32_ShadowCopy to delete volume shadow copies; event logs cleared.
  • Security software plus database and backup services stopped; PsExec, AnyDesk, RustDesk, Radmin and Cloudflared frequently present.
  • Exfiltration typically via Rclone, WinSCP, FileZilla or MEGA clients.
  • BYOVD to disable AV (seen since July 2025): rwdrv.sys (the legitimate ThrottleStop driver) and hlpdrv.sys registered as services, with Defender's DisableAntiSpyware registry value rewritten.
  • Safe Mode to evade EDR (first observed August 2026): hosts rebooted into Safe Mode with Networking, where most EDR agents do not load, and AnyDesk added to the Safe Mode registry keys so it starts after the reboot.
  • On ESXi: virtual machines going offline en masse, snapshots removed, ransom notes under /vmfs/volumes.

Caution. The unrelated 2017 malware also named "Akira" is a different family; early tooling for one does not apply to the other.

Infection vectors

Akira affiliates concentrate on edge devices and identity, rarely relying on user clicks.

1. VPN and remote access without MFA. This is the first entry vector listed in the CISA advisory: credential stuffing, brute force, or accounts bought from initial access brokers used to log straight into SSL VPN, followed by lateral movement. Associated flaws include Cisco ASA/FTD CVE-2020-3259 and CVE-2023-20269, and SonicWall SSL VPN CVE-2024-40766. MFA alone is not immunity: in September 2025 Arctic Wolf observed Akira logging into SonicWall SSL VPN accounts that had OTP enabled, most likely reusing credentials and OTP seeds stolen before the appliance was patched. Any device that was exposed needs all VPN credentials and OTP seeds reset — patching alone is not enough.

2. Backup and virtualisation component flaws. Veeam Backup & Replication CVE-2023-27532 and CVE-2024-40711 are exploited repeatedly — take the backup server first, destroy backups, then encrypt. This is the classic Akira path to "production and backups gone together".

3. Exposed RDP and weak credentials. Internet-facing 3389 and a shared local administrator password across the domain are both exploited quickly.

4. Phishing and remote-tool abuse. A minority of cases start with phishing delivery or abuse of legitimate remote tools such as AnyDesk and RustDesk.

Once inside, the pattern is consistent: harvest credentials with Mimikatz or LaZagne, map the domain and network with AdFind, Advanced IP Scanner and SoftPerfect, create a domain admin account, push the encryptor through PsExec or Group Policy, exfiltrate with Rclone, then encrypt everything outside business hours. On ESXi, Akira uses vim-cmd to power off guests and delete snapshots before encrypting the VMDKs, maximising the blast radius.

Encryption behavior

Algorithms. The CISA advisory describes a hybrid scheme: ChaCha20 for file (or block) data, with the ChaCha20 key wrapped by the attacker's RSA public key and appended to the file. Because the private key never leaves the operators, recovering keys from ciphertext alone is not mathematically feasible.

Intermittent / partial encryption. The encryptor chooses full or partial encryption based on file type and size. Small files are encrypted end to end; large files get a subset of blocks encrypted with stretches skipped in between. That is why Akira can finish an entire virtualisation cluster in hours — and it is also what leaves room for recovery: in large .vmdk, .mdf/.ndf or .dbf files, untouched ranges still hold original data. The exact ratio depends on build and command-line switches and must be measured per case, never assumed.

Destructive actions.

  • Deletes all volume shadow copies via PowerShell against Win32_ShadowCopy.
  • Stops and disables database, Exchange and backup-agent services so files can be opened exclusively.
  • Clears event logs and deletes itself.
  • On Linux/ESXi, powers off guests and deletes snapshots before encrypting; since June 2025 it has also been observed encrypting Nutanix AHV environments, the first publicly reported case for this group.

Double extortion. Data is exfiltrated before encryption, so negotiation covers both decryption and non-publication; non-payers are posted to the leak site and released in stages.

Assess before you act

Recoverability assessment

Recoverability for Akira varies widely with build, platform, encryption time window, and how much of the scene survived. We work through the options in this order.

1. Does a public decryptor apply (rare)? For early builds predating July 2023, the Avast decryptor may work if a matched pre- and post-encryption copy of one file is available. For Linux/ESXi v3, the GPU brute-force path is viable when the encryption time can be narrowed sufficiently, though time and compute cost are significant. For current builds such as Akira_v2, no free or commercial decryptor exists.

2. Backups, snapshots and shadow copies. Shadow copies are usually deleted, but scanning for residual VSS difference blocks is still worthwhile. The real opportunities are offline/off-site backups, tape, versioned cloud object storage and its recycle bins, snapshots held on the storage array or NAS controller (which the Windows encryptor cannot delete), and backup copies the attacker overlooked. Where the backup server was the entry point, assume backup repositories were deliberately purged.

3. Repair enabled by partial encryption — the most practical route for .akira files. For ESXi VMDKs and database files confirmed to be intermittently encrypted, we map the encryption layout: locate the ChaCha20-covered blocks against the intact ranges and rebuild from there. Typical outcomes include extracting a complete or near-complete filesystem and business files from unencrypted VMDK ranges, and page- or extent-level repair of SQL Server, Oracle and MySQL data files combined with unencrypted logs and backups to reach a usable, consistent state. How much comes back depends entirely on the encryption ratio and whether critical metadata fell inside encrypted regions — it has to be measured before it can be assessed, and we do not quote percentages before that.

4. Unencrypted copies and log replay. Development and test databases, downstream reporting instances, ERP staging tables, mail attachments, endpoint-local copies, and application transaction logs often close the gap. Where an unencrypted transaction log survives, point-in-time replay is possible.

5. Low-level carving. Some encryptors overwrite in place; others read, encrypt, write a new file and delete the original, leaving recoverable clusters on disk. Deleted VM snapshots and wiped backup volumes deserve the same low-level treatment.

What we will not do. We do not claim "100% decryption" or guarantee recovery, we do not pay ransoms, and we do not negotiate with attackers on a client's behalf. We deliver a measured recoverability assessment that states what can be recovered, to which point in time, and at what cost — the decision stays with the client.

Our response plan

Hit by Akira ransomware? What to do

  1. Containment and forensic preservation

    Isolate affected hosts and ESXi servers from the network, but do not rush to power off or rebuild: memory, VPN and firewall logs, and ESXi hostd/vmkernel logs are how we bound the encryption time window — and that window decides whether the GPU brute-force path is viable for the Linux/ESXi variant.

    We take read-only images of VMDKs, database files and backup volumes first and work only on the images from then on, while preserving akira_readme.txt, encrypted samples, suspicious remote-access processes and account-change records.

  2. Family and build confirmation, encryption analysis

    Confirm the family from the extension (.akira / .powerranges / .akiranew / .aki), note format and file-tail structure, then determine whether this is the Windows build, Linux/ESXi v3, or Akira_v2 — the fork that decides whether any free decryption path exists.

    In parallel we map the encryption layout of representative large files: read headers and tails, run per-block entropy and known-structure comparisons, quantify the real encrypted-versus-intact ratio and distribution, and establish whether writes were in place.

  3. Recoverability assessment and plan

    We validate each of the four routes and state a conclusion: applicability of public decryptors, availability of backups and storage-layer snapshots, how far partial-encryption repair can go, and what unencrypted copies and logs can backfill.

    The deliverable is a recoverability assessment: which systems and data can be recovered, the achievable point in time, what cannot be recovered, and the effort and resources required. The client decides whether to proceed on that basis, rather than paying first and finding out later.

  4. Recovery execution

    Execution happens in an isolated clean environment: rebuild virtual disks and filesystems from unencrypted VMDK ranges; perform page-level repair and consistency validation on SQL Server, Oracle and MySQL; where needed, merge backups, logs and repaired data, then validate usability system by system.

    Business owners sample-verify recovered data against core tables and key documents before any cutover to production, so we never hand back data that opens technically but is unusable operationally.

  5. Attribution, hardening and sign-off

    Reconstruct the intrusion chain: was VPN missing MFA, were Cisco/SonicWall/Fortinet devices unpatched, was Veeam exposed, which account carried lateral movement.

    Hardening targets Akira's fixed playbook: enforce MFA on all VPN and management entry points, establish patch and version governance for edge devices, separate backup infrastructure from the production domain with immutable storage, disable SSH and shell on ESXi, restrict vSphere management-plane access, centralise logs, and add detections for Rclone, AnyDesk and PsExec-style tooling. We close with a sign-off report and a recommended 30-day observation period.

Risk warning

What not to do

  • Do not reboot or power off encrypted ESXi hosts and guests — memory may still hold information that bounds the encryption time window, and that window decides whether the brute-force path for the Linux/ESXi variant is viable.
  • Do not run any "decryptor" or recovery software against original disks. Most Akira decryptors offered online are follow-on scams, and even the legitimate Avast tool should be trialled on an image.
  • Do not format, rebuild or run chkdsk / fsck on encrypted volumes, and do not run consistency repairs against VMDKs — that overwrites the intact blocks intermittent encryption left behind.
  • Do not restore from backup before the entry point is closed. Akira affiliates commonly persist through VPN and Veeam, and a restore into a live intrusion gets re-encrypted.
  • Do not delete akira_readme.txt, encrypted samples or logs, and do not clean up suspicious accounts — they are the only basis for build identification and attribution.
  • Do not contact the Tor site in the note or pay on your own. Payment does not guarantee a working key and carries legal and compliance exposure.

Emergency response

Data already encrypted? Stop and let an engineer look first

We do not pay ransoms and we do not negotiate with attackers. Engineers run a free assessment first, then propose a recovery plan and a firm quote.

Related scenarios

Related industries

Similar families

Related questions

FAQ

Akira Frequently asked questions

  • Can ESXi virtual machines encrypted by Akira be recovered?

    Often yes, subject to two factors.

    First, build. For Linux/ESXi v3 with a sufficiently narrow encryption time window, GPU key brute-forcing is a real option (a researcher has published a working implementation); the cost is compute and elapsed time. Newer builds fixed the underlying flaw.

    Second, encryption mode. Akira generally uses intermittent encryption on large files, so VMDKs typically retain long stretches of original data. We map the encryption layout, rebuild filesystems from intact ranges and extract business data, while also checking storage-array and NAS snapshots — the Windows encryptor cannot delete snapshots held on a storage controller, and this is frequently the fastest route.

    How much returns has to be measured first; we do not quote a percentage before that.

  • There are free Akira decryptors online — why doesn't one work for me?

    Because both public tools have strict limits.

    Avast's 2023 decryptor covers early builds only, and it needs a matched pre- and post-encryption copy of the same file, preferably a large one. Builds after July 2023 are out of scope.

    The 2025 GPU brute-force tool targets Linux/ESXi v3 specifically, exploiting its nanosecond-timestamp key seeding. It requires an approximate encryption time and substantial GPU runtime, and the author notes newer builds are not affected.

    If your files were encrypted by Akira_v2, no public decryptor exists. Put the effort into backups, storage snapshots and partial-encryption repair instead of repeatedly trialling tools on the original disks.

  • Does Akira steal data, and will it be published if we don't pay?

    Yes. Akira is a textbook double-extortion operation: data is exfiltrated with Rclone, WinSCP or MEGA before encryption, and negotiation covers both the decryptor and non-publication. Non-paying victims are posted to its leak site and released in stages.

    One point matters: paying does not mean the data is deleted. The forensic task is to establish when, through which channel and how much data left, determine which business data and personal information are involved, and assess notification obligations to regulators and affected individuals under China's Cybersecurity Law, Data Security Law and PIPL. That analysis is part of our incident-response deliverable.

  • Akira also hit our backup server — are there other options?

    Yes, but in a specific order.

    Akira affiliates routinely exploit Veeam flaws (CVE-2023-27532, CVE-2024-40711) to take the backup server first, so destroyed backups are the norm rather than bad luck. Still worth checking systematically: tape and offline media, versioned off-site or cloud backups and their recycle bins, snapshots on the storage array or NAS controller, and low-level remnants in the backup repository — deleted backup files often leave recoverable clusters.

    In parallel, partial-encryption repair on the production side usually contributes a meaningful share of the data. We combine four streams — backup remnants, production repair, unencrypted copies and log replay — and assess which point in time is reachable.

  • Why does the Akira note give only a URL, with no email address?

    By design. akira_readme.txt provides only a Tor onion URL and a victim-specific login code — no email, no wallet address — with all communication inside their dark-web panel. It centralises negotiation and reduces traceable artefacts.

    For identification that is useful: a note offering an email, QQ or Telegram handle is most likely not Akira but a family such as Phobos, GlobeImposter or Makop, whose handling and recovery paths are entirely different. Misidentifying the family leads straight to the wrong plan, which is why we always start from sample and note comparison.