{"record":{"id":"ATTACK:enterprise:S0366","title":"WannaCry","type":"Software","source_url":"https://attack.mitre.org/software/S0366","snapshot":"enterprise-attack-20.0.json","status":"active","rights":"Source metadata only; source notices retained; no operational prose or payloads","review_status":"machine-extracted; source-specific checks passed, editorial review pending","stix_id":"malware--75ecdbf1-c2bb-4afc-a3f9-c8da4de8c661","external_id":"S0366","domain":"enterprise","created":"2019-03-25T17:30:17.004Z","modified":"2024-12-09T02:29:13.859Z","version":"1.1","aliases":[],"tactics":[],"source_references":[{"source_name":"WanaCrypt0r"},{"source_name":"WCry"},{"source_name":"WanaCry"},{"source_name":"WanaCrypt"},{"source_name":"FireEye WannaCry 2017","url":"https://www.fireeye.com/blog/threat-research/2017/05/wannacry-malware-profile.html"},{"source_name":"SecureWorks WannaCry Analysis","url":"https://www.secureworks.com/research/wcry-ransomware-analysis"},{"source_name":"Washington Post WannaCry 2017","url":"https://www.washingtonpost.com/business/economy/more-than-150-countries-affected-by-massive-cyberattack-europol-says/2017/05/14/5091465e-3899-11e7-9e48-c4f199710b69_story.html?utm_term=.7fa16b41cad4"},{"source_name":"LogRhythm WannaCry","url":"https://web.archive.org/web/20230522041200/https://logrhythm.com/blog/a-technical-analysis-of-wannacry-ransomware/"},{"source_name":"US-CERT WannaCry 2017","url":"https://www.us-cert.gov/ncas/alerts/TA17-132A"}]},"assertions":[{"id":"enterprise:relationship--0e12dc13-6f73-4ad9-9cb5-845d443b4d58","subject":"ATTACK:enterprise:S0366","predicate":"uses","object":"ATTACK:enterprise:T1210","asserted_by":"MITRE ATT&CK","source_url":"https://raw.githubusercontent.com/mitre-attack/attack-stix-data/c2494b29dd268c46a5d0ea0990553e4327cd2253/enterprise-attack/enterprise-attack-20.0.json","snapshot":"enterprise-attack-20.0.json","evidence_locator":"relationship--0e12dc13-6f73-4ad9-9cb5-845d443b4d58","modified":"2026-08-04T20:30:55.745Z","references":[{"source_name":"FireEye WannaCry 2017","url":"https://www.fireeye.com/blog/threat-research/2017/05/wannacry-malware-profile.html"},{"source_name":"LogRhythm WannaCry","url":"https://web.archive.org/web/20230522041200/https://logrhythm.com/blog/a-technical-analysis-of-wannacry-ransomware/"},{"source_name":"US-CERT WannaCry 2017","url":"https://www.us-cert.gov/ncas/alerts/TA17-132A"}],"qualification":"Source assertion; no new actor identity, alias equivalence, CVE exploitation or causal inference. Procedure prose omitted.","source_occurrences":1},{"id":"enterprise:relationship--1427027f-0fd1-4781-b4b3-06dc8e6e9998","subject":"ATTACK:enterprise:S0366","predicate":"uses","object":"ATTACK:enterprise:T1489","asserted_by":"MITRE ATT&CK","source_url":"https://raw.githubusercontent.com/mitre-attack/attack-stix-data/c2494b29dd268c46a5d0ea0990553e4327cd2253/enterprise-attack/enterprise-attack-20.0.json","snapshot":"enterprise-attack-20.0.json","evidence_locator":"relationship--1427027f-0fd1-4781-b4b3-06dc8e6e9998","modified":"2026-04-29T14:23:05.931Z","references":[{"source_name":"FireEye WannaCry 2017","url":"https://www.fireeye.com/blog/threat-research/2017/05/wannacry-malware-profile.html"},{"source_name":"SecureWorks WannaCry Analysis","url":"https://www.secureworks.com/research/wcry-ransomware-analysis"}],"qualification":"Source assertion; no new actor identity, alias equivalence, CVE exploitation or causal inference. Procedure prose omitted.","source_occurrences":1},{"id":"enterprise:relationship--25e7ca82-2784-433a-90a9-a3483615a655","subject":"ATTACK:enterprise:G0032","predicate":"uses","object":"ATTACK:enterprise:S0366","asserted_by":"MITRE ATT&CK","source_url":"https://raw.githubusercontent.com/mitre-attack/attack-stix-data/c2494b29dd268c46a5d0ea0990553e4327cd2253/enterprise-attack/enterprise-attack-20.0.json","snapshot":"enterprise-attack-20.0.json","evidence_locator":"relationship--25e7ca82-2784-433a-90a9-a3483615a655","modified":"2026-07-31T20:48:46.507Z","references":[{"source_name":"FireEye WannaCry 2017","url":"https://www.fireeye.com/blog/threat-research/2017/05/wannacry-malware-profile.html"},{"source_name":"SecureWorks WannaCry Analysis","url":"https://www.secureworks.com/research/wcry-ransomware-analysis"},{"source_name":"FireEye APT38 Oct 2018","url":"https://services.google.com/fh/files/misc/apt38-un-usual-suspects.pdf"},{"source_name":"LogRhythm WannaCry","url":"https://web.archive.org/web/20230522041200/https://logrhythm.com/blog/a-technical-analysis-of-wannacry-ransomware/"}],"qualification":"Source assertion; no new actor identity, alias equivalence, CVE exploitation or causal inference. Procedure prose omitted.","source_occurrences":1},{"id":"enterprise:relationship--3ca496bf-41f9-4d0b-b36d-576f90db340e","subject":"ATTACK:enterprise:S0366","predicate":"uses","object":"ATTACK:enterprise:T1083","asserted_by":"MITRE ATT&CK","source_url":"https://raw.githubusercontent.com/mitre-attack/attack-stix-data/c2494b29dd268c46a5d0ea0990553e4327cd2253/enterprise-attack/enterprise-attack-20.0.json","snapshot":"enterprise-attack-20.0.json","evidence_locator":"relationship--3ca496bf-41f9-4d0b-b36d-576f90db340e","modified":"2026-04-29T14:23:06.007Z","references":[{"source_name":"FireEye WannaCry 2017","url":"https://www.fireeye.com/blog/threat-research/2017/05/wannacry-malware-profile.html"},{"source_name":"LogRhythm WannaCry","url":"https://web.archive.org/web/20230522041200/https://logrhythm.com/blog/a-technical-analysis-of-wannacry-ransomware/"}],"qualification":"Source assertion; no new actor identity, alias equivalence, CVE exploitation or causal inference. Procedure prose omitted.","source_occurrences":1},{"id":"enterprise:relationship--3f58682a-dc04-40f6-b224-42bab6ef6f67","subject":"ATTACK:enterprise:S0366","predicate":"uses","object":"ATTACK:enterprise:T1120","asserted_by":"MITRE ATT&CK","source_url":"https://raw.githubusercontent.com/mitre-attack/attack-stix-data/c2494b29dd268c46a5d0ea0990553e4327cd2253/enterprise-attack/enterprise-attack-20.0.json","snapshot":"enterprise-attack-20.0.json","evidence_locator":"relationship--3f58682a-dc04-40f6-b224-42bab6ef6f67","modified":"2026-04-29T14:23:06.011Z","references":[{"source_name":"FireEye WannaCry 2017","url":"https://www.fireeye.com/blog/threat-research/2017/05/wannacry-malware-profile.html"}],"qualification":"Source assertion; no new actor identity, alias equivalence, CVE exploitation or causal inference. Procedure prose omitted.","source_occurrences":1},{"id":"enterprise:relationship--5c56206f-8ae3-4296-ab89-bc2036b74896","subject":"ATTACK:enterprise:S0366","predicate":"uses","object":"ATTACK:enterprise:T1486","asserted_by":"MITRE ATT&CK","source_url":"https://raw.githubusercontent.com/mitre-attack/attack-stix-data/c2494b29dd268c46a5d0ea0990553e4327cd2253/enterprise-attack/enterprise-attack-20.0.json","snapshot":"enterprise-attack-20.0.json","evidence_locator":"relationship--5c56206f-8ae3-4296-ab89-bc2036b74896","modified":"2026-04-29T14:23:06.051Z","references":[{"source_name":"FireEye WannaCry 2017","url":"https://www.fireeye.com/blog/threat-research/2017/05/wannacry-malware-profile.html"},{"source_name":"SecureWorks WannaCry Analysis","url":"https://www.secureworks.com/research/wcry-ransomware-analysis"},{"source_name":"LogRhythm WannaCry","url":"https://web.archive.org/web/20230522041200/https://logrhythm.com/blog/a-technical-analysis-of-wannacry-ransomware/"}],"qualification":"Source assertion; no new actor identity, alias equivalence, CVE exploitation or causal inference. Procedure prose omitted.","source_occurrences":1},{"id":"enterprise:relationship--6ad5d5c8-b53e-417c-a574-3818269d1e85","subject":"ATTACK:enterprise:S0366","predicate":"uses","object":"ATTACK:enterprise:T1047","asserted_by":"MITRE ATT&CK","source_url":"https://raw.githubusercontent.com/mitre-attack/attack-stix-data/c2494b29dd268c46a5d0ea0990553e4327cd2253/enterprise-attack/enterprise-attack-20.0.json","snapshot":"enterprise-attack-20.0.json","evidence_locator":"relationship--6ad5d5c8-b53e-417c-a574-3818269d1e85","modified":"2026-04-29T14:23:06.070Z","references":[{"source_name":"FireEye WannaCry 2017","url":"https://www.fireeye.com/blog/threat-research/2017/05/wannacry-malware-profile.html"},{"source_name":"SecureWorks WannaCry Analysis","url":"https://www.secureworks.com/research/wcry-ransomware-analysis"},{"source_name":"LogRhythm WannaCry","url":"https://web.archive.org/web/20230522041200/https://logrhythm.com/blog/a-technical-analysis-of-wannacry-ransomware/"}],"qualification":"Source assertion; no new actor identity, alias equivalence, CVE exploitation or causal inference. Procedure prose omitted.","source_occurrences":1},{"id":"enterprise:relationship--6b22c256-44a9-4b73-8df6-e4da9c32a5a3","subject":"ATTACK:enterprise:S0366","predicate":"uses","object":"ATTACK:enterprise:T1563.002","asserted_by":"MITRE ATT&CK","source_url":"https://raw.githubusercontent.com/mitre-attack/attack-stix-data/c2494b29dd268c46a5d0ea0990553e4327cd2253/enterprise-attack/enterprise-attack-20.0.json","snapshot":"enterprise-attack-20.0.json","evidence_locator":"relationship--6b22c256-44a9-4b73-8df6-e4da9c32a5a3","modified":"2026-04-29T14:23:06.071Z","references":[{"source_name":"LogRhythm WannaCry","url":"https://web.archive.org/web/20230522041200/https://logrhythm.com/blog/a-technical-analysis-of-wannacry-ransomware/"}],"qualification":"Source assertion; no new actor identity, alias equivalence, CVE exploitation or causal inference. Procedure prose omitted.","source_occurrences":1},{"id":"enterprise:relationship--76d0be57-e439-4640-b26d-db422353d9e5","subject":"ATTACK:enterprise:S0366","predicate":"uses","object":"ATTACK:enterprise:T1490","asserted_by":"MITRE ATT&CK","source_url":"https://raw.githubusercontent.com/mitre-attack/attack-stix-data/c2494b29dd268c46a5d0ea0990553e4327cd2253/enterprise-attack/enterprise-attack-20.0.json","snapshot":"enterprise-attack-20.0.json","evidence_locator":"relationship--76d0be57-e439-4640-b26d-db422353d9e5","modified":"2026-04-29T14:23:06.088Z","references":[{"source_name":"FireEye WannaCry 2017","url":"https://www.fireeye.com/blog/threat-research/2017/05/wannacry-malware-profile.html"},{"source_name":"SecureWorks WannaCry Analysis","url":"https://www.secureworks.com/research/wcry-ransomware-analysis"},{"source_name":"LogRhythm WannaCry","url":"https://web.archive.org/web/20230522041200/https://logrhythm.com/blog/a-technical-analysis-of-wannacry-ransomware/"}],"qualification":"Source assertion; no new actor identity, alias equivalence, CVE exploitation or causal inference. Procedure prose omitted.","source_occurrences":1},{"id":"enterprise:relationship--7a116d1c-33ab-4729-abff-2e37dc387f31","subject":"ATTACK:enterprise:S0366","predicate":"uses","object":"ATTACK:enterprise:T1018","asserted_by":"MITRE ATT&CK","source_url":"https://raw.githubusercontent.com/mitre-attack/attack-stix-data/c2494b29dd268c46a5d0ea0990553e4327cd2253/enterprise-attack/enterprise-attack-20.0.json","snapshot":"enterprise-attack-20.0.json","evidence_locator":"relationship--7a116d1c-33ab-4729-abff-2e37dc387f31","modified":"2026-04-29T14:23:06.092Z","references":[{"source_name":"SecureWorks WannaCry Analysis","url":"https://www.secureworks.com/research/wcry-ransomware-analysis"}],"qualification":"Source assertion; no new actor identity, alias equivalence, CVE exploitation or causal inference. Procedure prose omitted.","source_occurrences":1},{"id":"enterprise:relationship--a802b910-b023-425a-8c09-c1b2df185812","subject":"ATTACK:enterprise:S0366","predicate":"uses","object":"ATTACK:enterprise:T1564.001","asserted_by":"MITRE ATT&CK","source_url":"https://raw.githubusercontent.com/mitre-attack/attack-stix-data/c2494b29dd268c46a5d0ea0990553e4327cd2253/enterprise-attack/enterprise-attack-20.0.json","snapshot":"enterprise-attack-20.0.json","evidence_locator":"relationship--a802b910-b023-425a-8c09-c1b2df185812","modified":"2026-04-29T14:23:06.154Z","references":[{"source_name":"LogRhythm WannaCry","url":"https://web.archive.org/web/20230522041200/https://logrhythm.com/blog/a-technical-analysis-of-wannacry-ransomware/"},{"source_name":"Checkpoint WannaCry 2017","url":"https://blog.checkpoint.com/research/crying-futile-sandblast-forensic-analysis-wannacry/"}],"qualification":"Source assertion; no new actor identity, alias equivalence, CVE exploitation or causal inference. Procedure prose omitted.","source_occurrences":1},{"id":"enterprise:relationship--b3c7d447-9b00-4bd6-b0b7-25c0bb56d28a","subject":"ATTACK:enterprise:S0366","predicate":"uses","object":"ATTACK:enterprise:T1016","asserted_by":"MITRE ATT&CK","source_url":"https://raw.githubusercontent.com/mitre-attack/attack-stix-data/c2494b29dd268c46a5d0ea0990553e4327cd2253/enterprise-attack/enterprise-attack-20.0.json","snapshot":"enterprise-attack-20.0.json","evidence_locator":"relationship--b3c7d447-9b00-4bd6-b0b7-25c0bb56d28a","modified":"2026-04-29T14:23:06.171Z","references":[{"source_name":"SecureWorks WannaCry Analysis","url":"https://www.secureworks.com/research/wcry-ransomware-analysis"}],"qualification":"Source assertion; no new actor identity, alias equivalence, CVE exploitation or causal inference. Procedure prose omitted.","source_occurrences":1},{"id":"enterprise:relationship--c49a3d89-c8fa-4c5d-813e-f4495d892d1a","subject":"ATTACK:enterprise:S0366","predicate":"uses","object":"ATTACK:enterprise:T1222.001","asserted_by":"MITRE ATT&CK","source_url":"https://raw.githubusercontent.com/mitre-attack/attack-stix-data/c2494b29dd268c46a5d0ea0990553e4327cd2253/enterprise-attack/enterprise-attack-20.0.json","snapshot":"enterprise-attack-20.0.json","evidence_locator":"relationship--c49a3d89-c8fa-4c5d-813e-f4495d892d1a","modified":"2026-04-29T14:23:06.194Z","references":[{"source_name":"LogRhythm WannaCry","url":"https://web.archive.org/web/20230522041200/https://logrhythm.com/blog/a-technical-analysis-of-wannacry-ransomware/"}],"qualification":"Source assertion; no new actor identity, alias equivalence, CVE exploitation or causal inference. Procedure prose omitted.","source_occurrences":1},{"id":"enterprise:relationship--cf498579-a7c9-4d06-949b-fb75bf762990","subject":"ATTACK:enterprise:S0366","predicate":"uses","object":"ATTACK:enterprise:T1090.003","asserted_by":"MITRE ATT&CK","source_url":"https://raw.githubusercontent.com/mitre-attack/attack-stix-data/c2494b29dd268c46a5d0ea0990553e4327cd2253/enterprise-attack/enterprise-attack-20.0.json","snapshot":"enterprise-attack-20.0.json","evidence_locator":"relationship--cf498579-a7c9-4d06-949b-fb75bf762990","modified":"2026-04-29T14:23:06.209Z","references":[{"source_name":"SecureWorks WannaCry Analysis","url":"https://www.secureworks.com/research/wcry-ransomware-analysis"}],"qualification":"Source assertion; no new actor identity, alias equivalence, CVE exploitation or causal inference. Procedure prose omitted.","source_occurrences":1},{"id":"enterprise:relationship--d9bfa498-69a1-44f9-8e44-67a6a4c48088","subject":"ATTACK:enterprise:S0366","predicate":"uses","object":"ATTACK:enterprise:T1573.002","asserted_by":"MITRE ATT&CK","source_url":"https://raw.githubusercontent.com/mitre-attack/attack-stix-data/c2494b29dd268c46a5d0ea0990553e4327cd2253/enterprise-attack/enterprise-attack-20.0.json","snapshot":"enterprise-attack-20.0.json","evidence_locator":"relationship--d9bfa498-69a1-44f9-8e44-67a6a4c48088","modified":"2026-09-02T20:09:43.705Z","references":[{"source_name":"SecureWorks WannaCry Analysis","url":"https://www.secureworks.com/research/wcry-ransomware-analysis"}],"qualification":"Source assertion; no new actor identity, alias equivalence, CVE exploitation or causal inference. Procedure prose omitted.","source_occurrences":1},{"id":"enterprise:relationship--facd3eca-9156-47a8-85d1-09719bc0eb88","subject":"ATTACK:enterprise:S0366","predicate":"uses","object":"ATTACK:enterprise:T1543.003","asserted_by":"MITRE ATT&CK","source_url":"https://raw.githubusercontent.com/mitre-attack/attack-stix-data/c2494b29dd268c46a5d0ea0990553e4327cd2253/enterprise-attack/enterprise-attack-20.0.json","snapshot":"enterprise-attack-20.0.json","evidence_locator":"relationship--facd3eca-9156-47a8-85d1-09719bc0eb88","modified":"2026-04-29T14:23:06.265Z","references":[{"source_name":"FireEye WannaCry 2017","url":"https://www.fireeye.com/blog/threat-research/2017/05/wannacry-malware-profile.html"},{"source_name":"LogRhythm WannaCry","url":"https://web.archive.org/web/20230522041200/https://logrhythm.com/blog/a-technical-analysis-of-wannacry-ransomware/"}],"qualification":"Source assertion; no new actor identity, alias equivalence, CVE exploitation or causal inference. Procedure prose omitted.","source_occurrences":1},{"id":"enterprise:relationship--fe78de3a-107f-4870-b5a1-c60289d68dec","subject":"ATTACK:enterprise:S0366","predicate":"uses","object":"ATTACK:enterprise:T1570","asserted_by":"MITRE ATT&CK","source_url":"https://raw.githubusercontent.com/mitre-attack/attack-stix-data/c2494b29dd268c46a5d0ea0990553e4327cd2253/enterprise-attack/enterprise-attack-20.0.json","snapshot":"enterprise-attack-20.0.json","evidence_locator":"relationship--fe78de3a-107f-4870-b5a1-c60289d68dec","modified":"2026-09-03T19:46:58.503Z","references":[{"source_name":"LogRhythm WannaCry","url":"https://web.archive.org/web/20230522041200/https://logrhythm.com/blog/a-technical-analysis-of-wannacry-ransomware/"}],"qualification":"Source assertion; no new actor identity, alias equivalence, CVE exploitation or causal inference. Procedure prose omitted.","source_occurrences":1}],"source_snapshot":{"file":"enterprise-attack-20.0.json","url":"https://raw.githubusercontent.com/mitre-attack/attack-stix-data/c2494b29dd268c46a5d0ea0990553e4327cd2253/enterprise-attack/enterprise-attack-20.0.json","sha256":"81113ba98afa2928f3dcff62022539f7ce30c315c32e14422f11ff95ce534352","bytes":55271014,"checked_at":"2026-10-16T03:31:39Z"},"notices_url":"https://aol.pm/source-notices.txt","notices":"License\n-------\nThe MITRE Corporation (MITRE) hereby grants you a non-exclusive, royalty-free license to use ATT&CK® for research,\ndevelopment, and commercial purposes. Any copy you make for such purposes is authorized provided that you reproduce\nMITRE's copyright designation and this license in any such copy.\n\n\"© 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation.\"\n\nDisclaimers\n-----------\nMITRE does not claim ATT&CK enumerates all possibilities for the types of actions and behaviors documented as part\nof its adversary model and framework of techniques. Using the information contained within ATT&CK to address or cover\nfull categories of techniques will not guarantee full defensive coverage as there may be undisclosed techniques or\nvariations on existing techniques not documented by ATT&CK.\n\nALL DOCUMENTS AND THE INFORMATION CONTAINED THEREIN ARE PROVIDED ON AN \"AS IS\" BASIS AND THE CONTRIBUTOR, THE\nORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE MITRE CORPORATION, ITS BOARD OF TRUSTEES, OFFICERS,\nAGENTS, AND EMPLOYEES, DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT\nTHE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR\nFITNESS FOR A PARTICULAR PURPOSE.\n"}