{"id":93619,"date":"2019-01-09T11:00:14","date_gmt":"2019-01-09T19:00:14","guid":{"rendered":"https:\/\/securingtomorrow.mcafee.com\/?p=93619"},"modified":"2024-02-19T21:46:01","modified_gmt":"2024-02-20T05:46:01","slug":"ryuk-ransomware-attack-rush-to-attribution-misses-the-point","status":"publish","type":"post","link":"https:\/\/www.mcafee.com\/blogs\/other-blogs\/mcafee-labs\/ryuk-ransomware-attack-rush-to-attribution-misses-the-point\/","title":{"rendered":"Ryuk Ransomware Attack: Rush to Attribution Misses the Point"},"content":{"rendered":"

Senior analyst Ryan Sherstobitoff contributed to this report. <\/em><\/p>\n

During the past week, an outbreak of Ryuk ransomware that impeded newspaper printing services in the United States has garnered a lot of attention. To determine who was behind the attack many have cited past research that compares code from Ryuk with the older ransomware Hermes to link the attack to North Korea. Determining attribution was largely based on the fact that the Hermes ransomware has been used in the past by North Korean actors, and code blocks in Ryuk are similar to those in Hermes.<\/p>\n

The McAfee Advanced Threat Research team has investigated this incident and determined how the malware works, how the attackers operate, and how to detect it. Based on the technical indicators, known cybercriminal characteristics, and evidence discovered on the dark web, our hypothesis is that the Ryuk attacks may not necessarily be backed by a nation-state, but rather share the hallmarks of a cybercrime operation.<\/p>\n

How McAfee approaches attribution<\/strong><\/p>\n

Attribution is a critical part of any cybercrime investigation. However, technical evidence is often not enough to positively identify who is behind an attack because it does not provide all the pieces of the puzzle. Artifacts do not all appear at once; a new piece of evidence unearthed years after an attack can shine a different light on an investigation and introduce new challenges to current assumptions.<\/p>\n

Ryuk attack: putting the pieces together<\/strong><\/p>\n

In October 2017, we investigated an attack on a Taiwanese bank<\/a>. We discovered the actors used a clever tactic to distract the IT staff: a ransomware outbreak timed for the same moment that the thieves were stealing money. We used the term pseudo-ransomware<\/em> to describe this attack. The malware was Hermes version 2.1.<\/p>\n

One of the functions we often see in ransomware<\/a> samples is that they will not execute if the victim\u2019s system language is one of the following:<\/p>\n