ransomwareS0366

WannaCry

Also known as: WanaCry, WanaCrypt, WanaCrypt0r, WannaCrypt, WCRY, WCrypt, Wcry Ransomware

Alert when a public recovery tool comes out, when compatibility changes and when a new variant appears.

Summary

According to numerous open-source reports, a widespread ransomware campaign is affecting various organizations with reports of tens of thousands of infections in as many as 74 countries, including the United States, United Kingdom, Spain, Russia, Taiwan, France, and Japan. The software can run in as many as 27 different languages. The latest version of this ransomware variant, known as WannaCry, WCry, or Wanna Decryptor, was discovered the morning of May 12, 2017, by an independent security researcher and has spread rapidly over several hours, with initial reports beginning around 4:00 AM EDT, May 12, 2017. Open-source reporting indicates a requested ransom of .1781 bitcoins, roughly $300 U.S.

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, valid for any family. · published on 10 Nov 2026

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

In Brazil, besides the CSIRTs
  • 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.

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: .wcry .WNCRY
note: @Please_Read_Me@.txt @wanadecryptor@.exe

source: microsoft.comblog.talosintelligence.com

Groups using the family

Techniques (MITRE ATT&CK) 16

The techniques MITRE ATT&CK documents for this family. Each links to the technique page on ATT&CK, with detection and mitigation guidance.

ATT&CK 20.1. © The MITRE Corporation. S0366

U.S. Treasury sanctions (OFAC)

OFAC press releases that sanction people or companies and tie them, in the text itself, to this family or to the groups that operate or use it.

According to OFAC, facilitating a ransom payment to sanctioned people or companies may violate U.S. sanctions. OFAC advisory. Not legal advice.

CVEs exploited by the groups

These CVEs belong to the group (source and confidence alongside), not necessarily to this family.

Indicators

79 indicators linked to this family

  • sha256_hash · 34e22edd2350543f4b621924eb1bff7bffdd2ab7f7ddd30f57b01e7afb78b69c · community indicator feed
  • sha256_hash · 107bde9126611222a6c6622985635e3c5bcf8cc11a080a1a1431facc19897eee · community indicator feed
  • sha256_hash · 690638f098adb2a5940c2409a412626fb95aa6bfb38a3b9c151008fb99274391 · community indicator feed
  • sha256_hash · a947e19ee6e1e28113205ae36579011ec35455317a2bbcf632d4b55bf39e4174 · community indicator feed
  • sha256_hash · 533e67aa31d63a0ba46ce26b18962508c13fc6a31a6e8a001ab059e5f2cf34b9 · community indicator feed
  • sha256_hash · 69769ea6ce90420aa08968c589ee96f23a602bc8f9483b4a7af8dfe058cca460 · community indicator feed
  • sha256_hash · b07b17b3cf0ec6d943e7af638c6f973240b87b7a25168c84eef54bc4a7c95680 · community indicator feed
  • sha256_hash · 44f08e83abd27fb12e0bc636835e04407ee06adbf292b26bab8f7b65424bfde3 · community indicator feed
  • sha256_hash · ed01ebfbc9eb5bbea545af4d01bf5f1071661840480439c6e5babe8e080e41aa · group leak site
  • md5_hash · 84c82835a5d21bbcf75a61706d8ab549 · group leak site