Fable ransomware is reported to add .fable to filenames and leave RecoveryNotice.txt. If previously working documents suddenly become unreadable and both markers appear, disconnect the affected device from the network and preserve the files and note. A matching filename alone is not a diagnosis. For a work or school system, contact IT or incident response before installing tools, rebooting, or erasing anything. Malware cleanup and file recovery are separate jobs: removing the malicious program does not decrypt files, and a ransom demand is not a reliable recovery plan.
Check the .fable and RecoveryNotice.txt pair
The published Fable description reports an added extension rather than a replacement of the original one. A document could therefore appear as report.docx.fable. That example illustrates the naming pattern; it is not a file recovered from a victim. The accompanying note name is RecoveryNotice.txt. These are reported recognition clues, not findings from a Gridinsoft laboratory test.
Compare the situation with what you actually see:
- Many files stopped opening at about the same time, and the note appeared nearby: treat this as a suspected ransomware incident. Record a few affected filenames, their locations, and when the problem was first noticed.
- Only one unfamiliar file has this suffix: establish where it came from. A renamed file, a test document, or a file from another application can have an arbitrary extension. Do not run an unknown file to identify it.
- The suffix or note differs: save the exact spelling. Do not select a decryptor merely because a search result uses the name Fable.
Removing .fable from a name only changes the label. It does not reverse encryption. Keep the originals unchanged; experiments belong on separate copies after the incident is contained.
Contain first, then choose the cleanup branch
For a personal PC, unplug Ethernet and disconnect Wi-Fi. Keep backup drives disconnected. For an organization, call the response team from a separate device and follow its incident plan. Network isolation limits access to other systems, but does not itself stop a process already encrypting local files.
If files are still changing, do not spend time installing software while damage continues. Ask an incident responder to stop the activity. If you cannot promptly stop it and further loss is occurring, shutting down may limit damage, but loses volatile evidence. When the machine can be contained without shutdown, avoid an unnecessary reboot before a responder decides whether memory capture is needed. The joint #StopRansomware Guide explains the evidence tradeoff in its response checklist.
Before cleanup or reinstalling, preserve the note, the original encrypted files, security-tool findings, and relevant logs. On organizational systems, responders should decide how to capture disk and memory evidence. Do not connect a valuable clean backup to the affected PC to make a quick copy. Our guide to preserving files from an infected Windows computer explains when to stop and get help rather than copying from a running infection.
Once containment and evidence preservation are complete, a personal Windows PC can move to malware cleanup. An attacker may have left other malicious components or unwanted startup entries; deleting the ransom note would not check those. This is a reason to scan, not a claim that a particular loader or persistence technique has been confirmed for Fable.
For this cleanup branch, use Gridinsoft Anti-Malware: obtain the installer from the official site on a clean device, install it when it is safe to proceed, update the database, run a Full Scan, and review and remove detected threats. Restart only after preservation is complete, then check again if activity returns. Do not reconnect to an affected network simply to update a scanner; if you cannot safely install or update it, use professional recovery assistance instead. On managed systems, IT should choose and coordinate the cleanup tools.
The scan is for malicious files and components. It is not a Fable decryptor, does not restore stolen data, and cannot certify that every route into a system has been closed. A compromised organization may need to rebuild affected systems and investigate access beyond the visible ransomware.
What the ransom note claims—and what to verify
The reported note addresses a university, demands $25,000, sets short contact/payment deadlines, and alleges data theft and deleted backups. It offers decryption and deletion of stolen information in return for payment. Those are the attacker’s statements. They do not establish a confirmed university breach, successful theft, missing backups, or a working recovery tool.
The distinction changes your next step. A deadline in a text file should not replace a check of your actual recovery options. An assertion that backups were deleted should trigger a check of backup systems and retention history by their administrator—not an assumption that every independent copy is gone. A promise to delete stolen data cannot show that no other copy exists.
There is no verified cipher, initial infection route, or victim count established in the evidence used for this guide. Do not infer that a recent email, installer, or remote connection was the cause solely because it preceded the discovery. Preserve that timeline for investigation.
Can .fable files be recovered?
As of November 17, 2026, we did not find a Fable-specific tool in No More Ransom’s decryption-tools directory. This is a dated check of that directory, not proof that no solution exists anywhere or will ever become available. Its tools are family-specific: the instructions and supported variants must match before a tool is considered.
You have a backup from before the incident
Keep it isolated while the affected system is cleaned or rebuilt. Check that representative files open correctly in a clean environment. Restore from the verified copy only after the route of compromise is addressed.
A cloud service has older file versions
Check version history from a clean device or ask the administrator. A synced encrypted file and a retained earlier version are different things. Verify what is actually available before restoring or deleting anything.
A trusted project later lists a matching decryptor
Read its requirements and limitations. Preserve originals and test only copies in a clean environment. A successful test on one file does not establish that every file is recoverable.
No usable backup or matching tool is available
Retain the encrypted data and note for later reassessment. A reputable recovery specialist can assess available options, but cannot honestly guarantee decryption merely from the filename.
A normal deleted-file recovery utility is not a cryptographic decryptor. It may find an older unencrypted copy in some circumstances, but that is a different operation from unlocking the encrypted file. Avoid installing recovery software onto the only disk containing evidence or potentially recoverable data; obtain advice before making further writes.
Keep copies private. If an identification service requests a note or encrypted file, first check its privacy terms and whether you have permission to share that material. Work, student, customer, medical, and financial records should not become public samples simply because a form accepts uploads.
Recovery does not settle a possible data breach
Being able to open your files again answers the availability question. It does not establish whether someone accessed accounts or copied information earlier. If the note’s theft allegation concerns an organization, let its incident team investigate logs and access records and coordinate any necessary notifications. Do not announce confirmed theft solely from the note—or dismiss the possibility because a backup worked.
If you also see unfamiliar sign-ins, changed recovery settings, or unauthorized messages, secure the affected accounts from a clean device. Our account recovery guide covers sessions, recovery methods, and linked accounts. Changing passwords on the affected PC may expose the replacements.
Be wary of unsolicited recovery offers, remote-access requests, and claims of guaranteed Fable decryption. Ask what technical method is proposed and what evidence supports it before paying or sharing files. The Ransom Busters recovery-scam guide shows why a service’s recovery promises need independent scrutiny.
For Fable, the practical order is to contain the incident, preserve the .fable files and RecoveryNotice.txt, remove the compromise, and evaluate recovery against verified copies or a genuinely matching tool. Keep the attacker’s promises separate from those decisions.
References
- CISA, MS-ISAC, NSA, and FBI. #StopRansomware Guide. Joint Ransomware Task Force, October 2023; official FBI IC3-hosted edition, accessed November 17, 2026. Part 2: Ransomware and Data Extortion Response Checklist.
- The No More Ransom Project. Decryption Tools. Living directory, accessed November 17, 2026.

