This blog post will explain the workings of the ransomware named Wasted Locker based on 3 different samples. Last weeks I read a lot of articles about companies getting attack by Wasted Locker. Wasted Locker is ransomware used to attack large companies to make ransom demands. These amounts sometimes go up to $ 10 million.

Employees later shared with BleepingComputer that the ransom demand was $10 million. -

Static analysis

  • The program Detect It Easy detected the linker Polink(2.50*)[EXE32,signed]
  • Compiler stamp Thu Jun 11 06:10:48 2020 UTC
  • 18 imports
  • File extension - rhl_wastedinfo
  • The program Detect It Easy detected the linker Polink(2.50*)[EXE32,signed]
  • Compiler stamp Wed Jul 22 20:43:17 2020 UTC
  • 64 imports
  • File extension - garminwasted
  • The program Detect It Easy detected the linker Microsoft Visual C/C++(2005)[-].
  • Compiler stamp Tue May 26 19:46:34 2020 UTC
  • 128 imports
  • File extension - bbawasted_info


The first 2 samples are protected with a custom crypter, referred to as CryptOne by Fox-IT. To further analyse the unpacked executable I used x64dbg and Scylla to dump the memory to an executable.

WastedLocker is protected with a custom crypter, referred to as CryptOne* by Fox-IT InTELL. On examination, the code turned out to be very basic and used also by other malware families such as: *Netwalker, Gozi ISFB v3, ZLoader and Smokeloader. -

Packed executables SHA-256 hashes

  • 5CD04805F9753CA08B82E88C27BF5426D1D356BB26B281885573051048911367
  • 905EA119AD8D3E54CD228C458A1B5681ABC1F35DF782977A23812EC4EFA0288A

The main function executes uses LoadLibrary to load kernel32.dll in memory and GetProcAddress to retrieve the address of the function VirtualAlloc. VirtualAlloc is then used to create a memory with the memory protection constant 0x40 = PAGE_EXECUTE_READWRITE (


After that, another function writes shellcode to the new memory_region. At the end of the main function, it takes a jump to the created memory_region_offset.



To further analyse the instructions at new the memory_region I dumped to memory region to a file and opened it Ghidra at the specified offset. The crypter writes a “new” executable to a memory region, then uses a XOR-based algorithm to decrypt the code. And then writes the new memory region that contains a new executable to the address 0x00400000 of the original executable in memory.

local_3a0 = new memory_region local_38c = original memory address of executable in memory



After the crypter is done it jumps back to the entry point of the decrypted executable.


Using x64dbg I dumped the memory to an executable to further analysis the ransomware.

Ransomware Analysis

This part of the analysis is based on the sample with the following SHA256 hash. This file was already unpacked but works almost the same as the other samples.

  • BCDAC1A2B67E2B47F8129814DCA3BCF7D55404757EB09F1C3103F57DA3153EC8

The ransomware starts with determining if it’s get executed with elevated privileges. Using GetTokenInformation the TokenElevation is checked. The TOKEN_ELEVATION structure indicates whether a token has elevated privileges. If the process runs with elevated privileges 0x1 is written to the buffer elevated_flag = TokenInformation, otherwise it writes 0x0 to elevated_flag.


If the major version number of the Windows version ( is bigger then 5, so Windows Vista or later and if the process is not running with elevated privileges (elevated_flag = 0) it will execute the function elevate_priviliges.


The function elevate_priviliges copies a “random” DLL in the directory C:\WINDOWS\system32\ to the folder C:\Users\<username>\AppData\Roaming\<random> using CopyFileW.


It then sets the file attribute of to new file location to 0x2 = FILE_ATTRIBUTE_HIDDEN.


Alternate Data Streams ( )

Instead of just writing the executable to copied DLL, the ransomware uses the file attribute ADS. This a way of hiding the ransomware in a not suspicious file. The function ReadFile reads the file that started the process, then CreateFileW is used to create the ADS in the <random-DLL>:bin and WriteFile writes the buffer that contains the executable to the ADS of the <random-DLL>:bin.


The buffer shows the following in the dump.


After that, a new directory is created in the temporary folder (%temp%\<random>\), for example, C:\Users\re\AppData\Local\Temp\D8BB. Then another folder is created with the name "C:\\Windows " . Note the extra space!


Before copying files NTcreate is called with the flag IO_REPARSE_TAG_MOUNT_POINT to %temp%\<random>\ and the directory %temp%\<random>\system32 is created. Using CopyFileW winsat.exe and the DDL winmm.dll is copied to %temp%\<random>\system32\ and then the entry point of winmm.dll is overwritten with new shellcode shown below.


To launch winsat.exe the function ShellExecuteExW is called which starts the following processes. winsat.exe is executed with elevated privileges and loads the DLL winmm.dll and winmm.dll is patched with shellcode that executes the ransomware hidden in the ADS C:\Users\re\AppData\Roaming\<random>:bin. The ransomware uses a vulnerability called DLL hijacking (



To use CryptoAPI functions of Windows the function CryptAcquireContextW is called. The encryption method used is RSA public key alogrithm, because the dwProvType parameter is 0x1 which stands for Cryptographic Provider Type PROV_RSA_FULL.


Then CryptGenRandom is called which fills the buffer random_bytes with cryptographically random bytes.


This buffer is used by other functions that execute the encryption routine.

Instead of copying the file that will be encrypted MoveFileW is used to move the file to <file-name>.bbawasted. The extension is not the same in all samples sometimes the name of the company being attacked is used here.

At this moment I was stuck because I didn’t understand how the files were being encrypted. Luckily Sophos wrote a blog post ( about the technique used.

Each file is encrypted using the AES algorithm with a newly generated AES key and IV (256-bit in CBC mode) for each file. The AES key and IV are encrypted with an embedded public RSA key (4096 bits). The RSA encrypted output of key material is converted to base64 and then stored into the ransom note. -

After encrypting the file the ransomware note is written to <file-name>.bbawasted_info with the key used to encrypt the file. The file is not associated with the ransomware, it is just a random file in my home directory.


I hope I was able to explain in a technical way how Wasted Locker works. I did not write about the arguments that can be given to the ransomware which executed different functions based on that, but it is already covered in another blog posts in the references. Next time I want to better analyze the encryption method used by the ransomware.


  • 5CD04805F9753CA08B82E88C27BF5426D1D356BB26B281885573051048911367
  • 905EA119AD8D3E54CD228C458A1B5681ABC1F35DF782977A23812EC4EFA0288A
  • BCDAC1A2B67E2B47F8129814DCA3BCF7D55404757EB09F1C3103F57DA3153EC8

Triage reports