Razor
Alert when a public recovery tool comes out, when compatibility changes and when a new variant appears.
Summary
Razor was discovered by dnwls0719, it is a part of Garrantydecrypt ransomware family. Like many other programs of this type, Razor is designed to encrypt files (make them unusable/inaccessible), change their filenames, create a ransom note and change victim's desktop wallpaper. Razor renames files by appending the ".razor" extension to their filenames. For example, it renames "1.jpg" to "1.jpg.razor", and so on. It creates a ransom note which is a text file named "#RECOVERY#.txt", this file contains instructions on how to contact Razor's developers (cyber criminals) and other details. As stated in the "#RECOVERY#.txt" file, this ransomware encrypts all files and information about how to purchase a decryption tool can be received by contacting Razor's developers. Victims supposed to contact them via razor2020@protonmail.ch, Jabber client (razor2020@jxmpp.jp) or ICQ client (@razor2020) and wait for further instructions. It is very likely that they will name a price of a decryption tool and/or key and provide cryptocurrency wallet's address that should be used to make a transaction. However, it is never a good idea to trust (pay) any cyber criminals/ransomware developers. It is common
Text from the open source (public malware catalogue or MITRE ATT&CK), unedited: it may be outdated or cover only one variant.
Recovery
No known public tool
Before any tool
- Preserve the encrypted files, the ransom note and any backups before trying anything.
- Test the tool on a copy of the files, in an isolated environment, following the vendor's instructions.
- A decryptor for the family does not guarantee recovery for every variant.
Recovery guide
General guidance for the first hours, valid for any family. It does not replace an incident response team.
1. Contain
- Disconnect the affected machines from the network (cable and Wi-Fi). If you cannot isolate them, shut them down to stop the spread.
- Disconnect the backups too and check that they were not encrypted.
- Change the passwords of administrative, VPN and service accounts from a clean machine: attackers usually hold stolen credentials.
2. Preserve the evidence
- Do not delete the encrypted files or the ransom note. They identify the family, and a tool may appear later.
- Keep the logs (firewall, VPN, domain controller, antivirus or EDR) and, if possible, a copy of the disks and memory of the affected machines.
- Write down what happened and when: the timeline helps the investigation and the notifications.
3. Identify the family
- Look the family up in the Vexday search by file extension, ransom note file name or sample hash.
- Check whether a free tool exists on No More Ransom and on the vendor's official page.
- A tool works for the family and sometimes only for some variants. Always test it on a copy of the files, in an isolated environment, following the vendor's instructions.
4. Recover safely
- Restore from verified backups, only after removing the attacker's access. Restoring earlier can reinfect the environment.
- When in doubt, rebuild the compromised machines from a trusted image.
- Paying the ransom does not guarantee that the data comes back or that it will not be published.
5. Report the incident
- Personal data: check your country's data protection law; many require notifying the authority and the data subjects within short deadlines.
- National CSIRT: report the incident to your country's CSIRT or CERT.
- Police: file a report with the cybercrime unit.
- Cyber insurance: tell the insurer before hiring incident response; many policies require it.
Under attack: who to call
- Personal data involved: notify the ANPD. Under the LGPD (art. 48), the controller notifies the ANPD and the data subjects of an incident that may cause relevant risk or harm, within 3 business days (ANPD Resolution CD/ANPD No. 15/2024). The data protection officer files it through SEI!ANPD. How to notify the ANPD
- File a police report. Ransomware is a crime. Many states have police units specialized in cybercrime; keep the ransom note and the encrypted files as evidence.
CSIRTs · Brazil
The country's incident response teams (CSIRTs), from the ENISA and FIRST lists. Each one serves a constituency: check it before writing.
- CERT.br · Computer Emergency Response Team BrazilFIRST
- Apura CSIRT · Apura DFIR / CSIRT TeamFIRSTServes: Companies
- CAIS/RNP · Brazilian Academic and Research Network CSIRTFIRSTServes: Research and education
- CSIRT-INTER · Banco Inter Computer Security Incident Response TeamFIRSTServes: Financial sector
- CSIRT PETROBRASFIRSTServes: Industrial sector
- CSIRT Soow Sigma · CSIRT Soow Sigma - Computer Security Incident Response TeamFIRSTServes: Government, Public and private sectors
- CTIR Gov-BR · Cyber Incident Prevention, Handling and Response Center of Brazilian GovernmentFIRSTServes: Government, Public and private sectors
- NTTDATA-BR-CERTFIRSTServes: Companies
- Nubank CSIRT · Nu CSIRTFIRSTServes: Financial sector
Another country: Argentina · Chile · Colombia · Costa Rica · Dominican Republic · Ecuador · Spain · Guatemala · Mexico · Panama · Peru · Portugal · El Salvador · Uruguay · Venezuela
Source: ENISA and FIRST lists · updated on 16 Nov 2026
Variants
No variant cataloged.
Extensions and ransom notes
extension: .razor
note: #RECOVERY#.txt
Groups using the family
No group with a documented link.
Indicators
No indicator linked to this family.