24H ransomware: indicators, decryption and recovery options

Data status: No reliable information

Emergency summary

24H is a ransomware variant recorded in the Ransomware Reverse database. According to our data, encrypted files carry the extension .24H. The documented ransom note is ReadME-24H.txt. No public decryptor is documented in our data; assess backups, decryptor sources and data recovery separately.

Extension
.24H
Ransom Note
ReadME-24H.txt
Platforms
not reliably documented
Decryption
No reliable information

How to recognise 24H

  • Files receive the extension .24H. Whether the extension is appended or the file name replaced can differ by variant.
  • Affected folders typically contain the file ReadME-24H.txt. Copy a ransom note as evidence instead of opening or deleting it on production systems.
  • Contact addresses documented in ransom notes can help with attribution. Do not make contact before incident response and management have agreed on an approach.

First response to 24H

  1. Isolate, do not wipe: disconnect affected systems from the network (LAN, Wi-Fi, VPN). Whether to power a system off depends on the scenario: volatile evidence in memory is lost on shutdown, but if encryption is still running an immediate shutdown can still be the right call.
  2. Do not alter encrypted originals: no renaming of .24H files, no cleanup tools and no reinstall on the original drives.
  3. Document indicators: record the ransom note (ReadME-24H.txt), file extension, time of first detection and affected systems.
  4. Protect backups: do not connect backup repositories to compromised systems and change backup credentials from a clean device.
  5. Preserve logs: export Windows event logs, EDR telemetry, firewall and VPN logs before they rotate.
  6. Answer two questions separately: who contains the attack (incident response)? Who assesses whether the data can be recovered (data recovery)?

Technical characteristics

Family / name24H
File extension(s).24H
Ransom noteReadME-24H.txt
Target platformsnot reliably documented
Encryptionnot reliably documented
Decryptor availabilityNo reliable information
Data exfiltration / double extortionnot reliably documented
Activitynot reliably documented
Attacker contact addresses (from ransom notes)24H@tutanota.com, 24HDecryptor@Mail.ru

Can 24H be decrypted?

No reliable information

Our data contains no reliable information on a public decryptor for 24H. That does not mean none exists – check current sources.

Always test decryptors on copies first and only obtain them from reputable sources such as the No More Ransom project. Supposed decryptors from forums or videos are often malware themselves.

More: Ransomware decryption – options and limits.

Recovery options

Which method works depends on the damage. None of the following options is always possible – but they should be assessed before anyone considers paying a ransom.

MethodPrerequisiteLimitation
Restore from a clean backupThe backup is unchanged, offline or immutable and free of attacker persistence.Backups may be encrypted, deleted or already compromised.
Snapshot recoveryStorage or hypervisor snapshots were not deleted.Attackers often delete snapshots deliberately.
Shadow copies (VSS)Volume shadow copies still exist.Many families delete them before encrypting.
File system reconstructionUsable structures (MFT, inodes, journals) and unencrypted regions exist.Depends on the damage; no substitute for a key.
VM / VMDK / VHDX recoveryVirtual disks are only partially encrypted or datastores can be reconstructed.Depends on variant and encryption mode.
RAID / NAS recoveryDrives are physically readable, RAID parameters can be reconstructed.Rebuilds or initialisation before analysis can destroy data.
Raw recovery / carvingFile contents remain unencrypted in free or unoverwritten areas.File names and folder structure are often lost.
Database / application recoveryDatabase files or transaction logs are partly intact.Technically complex, outcome cannot be guaranteed in advance.

Which route fits your situation?

Frequently asked questions

Is there a decryptor for 24H?

Based on our data: No reliable information. Only test decryptors on copies and only from reputable sources such as No More Ransom.

Which file extension does 24H use?

Documented extension: .24H. The extension can differ by variant; compare the ransom note as well.

What is the 24H ransom note called?

Documented: ReadME-24H.txt. Keep a copy of the note as evidence and do not contact the attackers before an approach has been agreed.

Should I shut down the affected server?

It depends on the scenario. Isolate first (disconnect from the network). Shutting down destroys volatile forensic evidence; if encryption is still running or spreading, an immediate shutdown can still be right. Ideally agree this with an incident response team.

Are my backups affected too?

Possibly. Attackers specifically look for backup servers, repositories and snapshots. Check backups in isolation before reconnecting them and validate restore points for persistence.

Can I copy the encrypted files?

Yes – copying encrypted files to a separate, clean medium is sensible so that later decryption or recovery attempts do not touch the originals. Do not do this from compromised systems.

Related guides

Sources and further reading

  1. [1]No More Ransom – decryption tools nomoreransom.org
  2. [2]ID Ransomware (MalwareHunterTeam) id-ransomware.malwarehunterteam.com

Data from the existing Ransomware Reverse dataset (imported at relaunch, not individually reviewed). Fields without reliable data are marked as such.