![\"DMA](\"\/huntsville-al\/wp-content\/uploads\/sites\/13\/2019\/04\/new_dma_lock.png\")
<\/p>\n<\/p>\n
Posted: May 29, 2017 by Malwarebytes Labs
\nLast updated: May 30, 2017<\/p>\n
Ransomware has become a popular criminal business with a relatively easy entrance. Even the people with little technical knowledge can build their own ransomware-based on open source code, that has been published on the internet some time ago. Nevertheless, cybercriminals keep stealing, not only from victims but also from each other. Some time ago we heard about PetrWrap \u2013 a ransomware built upon a binary of the infamous Petya. But that is not the only case. For some time, we have been observing a threat actor who distributes patched DMA Locker binaries.<\/p>\n
Real or stolen DMA Locker \u2013 why would you care?<\/p>\n
The observed samples of the stolen version of DMA Locker have been built based on one and the same instance of DMA Locker \u2013 so, they carry inside the same public key. This implies, that all the victims of this version can get their data back with the help of the same private key. And now comes the best part: we have this key and we distribute it for free to all affected persons.<\/p>\n
If you are a victim of the fake DMA Locker, you can send e-mail with samples of you encrypted files to: hasherezade-at-gmail.com<\/p>\n
How to recognize the stolen versions?<\/p>\n
Since the fake DMA Locker is based on the binary of the original DMA Locker 3.0, they have exactly the same GUI \u2013 only the keywords referring to DMA Locker has been removed:<\/p>\n
<\/p>\n
The main difference between the original and stolen DMA Locker is a different marker at the beginning of the encrypted file. While the real DMA Locker prefixes content with: !DMALOCK, the stolen version have many different prefix patterns. Some we have observed are:<\/p>\n
!XPTLOCK5.0
\n!Locked#2.0
\n!Locked!###
\n!Encrypt!##
\nHowever, the threat actor changes them periodically \u2013 so, anything that is different from the standard pattern may suggest that we are dealing with the \u201cpirated\u201d, decryptable version.<\/p>\n
An example of the file encrypted by the fake DMA Locker:<\/p>\n
![\"encrypted](\"\/huntsville-al\/wp-content\/uploads\/sites\/13\/2017\/05\/prefix.png\")
<\/p>\n
What are the chances to get the data back?<\/p>\n
Up to now, we managed to help 100% of the known victims of the fake DMA Locker. So far, the threat actor responsible for distributing it has not changed the key \u2013 so, the prospects of getting data back are still big. However, the chance to get help drastically shrink in case you were attacked with the legitimate DMA Locker, which may look the same at first sight.<\/p>\n
How to prevent the attack?<\/p>\n
Distributors of the fake (as well as the original) DMA Locker enter the victim machine via hacked Remote Desktop. Thus, we recommend paying attention if you have Remote Desktop open and if so, if it is properly secured.<\/p>\n
Analyzed sample<\/p>\n