babuk | 06f91fc7261d927a8b95818eec6fd925ea44eb5e4cddc914818940e1ffe0c69b

General

Target

babuk.exe
Size

495KB
MD5

d13989592e1f3213ca5b4dcad185e5aa
SHA1

b9b1195908946636a344cf3bff53a1f224f0085f
SHA256

4fbded3b4a76d753743cc5b0d4c7b1f5ee5b262a79051d4ef0085513b49505f2
SHA512

bbe21a1c67fbbd54db49da72e487b1afc55c8592aa622c5f5957a815e24a8bac1eb72fa9088d9903e9f8158a71512052c6c189637dfedb1ffcff70b37f2a29f7

Score

10^/10

babuk ransomware

Malware Config

Extracted

Path

C:\How To Restore Your Files.txt

Ransom Note

############## [ babuk ransomware greetings you ] ############## Introduction ---------------------------------------------- Congratulations! If you see this note, your company've been randomly chosen for security audit and your company haven't passed it. Unfortunately your servers are encrypted, backups are encrtypted too or deleted. Our enctyption algorythms are strong and it's impossible to decrypt your stuff without our help. Only one method to restore all your network and systems is - to buy our universal decryption software. Follow simple steps that discribed down below and your data will be saved. In case you ignore this situation, the consequences could me much serious, than you can imagine. Guarantees ---------------------------------------------- The hack and system encryption wasn't compromised by your competitors or any other 3rd party, this is just and only our initiative and only thing we interested is profit. Accurding the previous sentence We are very much value of our reputation. If we do not do our work and liabilities, nobody will pay us. This is not in our interests. All our decryption software is perfectly tested and will decrypt your data. We guarantee full support and help through the all decryption process. As the proof of our abilities and honesty, we can decrypt few small files for free, check the link provided and ask any questions. Data leakage ---------------------------------------------- We have copied some quantity of data from your servers. Check those proofs and estimate the seriousness of consequences which can occur in case you ignore us: (no blog url) This link is private and only you can see it. Use tor browser to open link. Ignoring the interaction with us brings you the publishing your data in our public blog http://wavbeudogz6byhnardd2lkp2jafims3j7tj6k6qnywchn2csngvtffqd.onion/ Contact ---------------------------------------------- 1) Download tor browser: https://www.torproject.org/download/ 2) Open it 3) Follow this link in tor browser: http://os3xs2l3ftdqeuhxyuo4e6ymxvknp3gx6abordkcjde4coe37k66xyid.onion/4ee7ff7421bcb2ab35c523623ce11174c037e7db0562578b8a245630fc16a047 * 6 simple steps do minimize harm from ransomware. ----------------------------------------------------------------------------------------------------------------- Thousands of companies around the world are struggling on ransomware these days, and the most of companies are making the same mistakes again and again. Let’s figure out how to minimize harm and do not be a dumb and pathetic donkey which will make fun for journalists and so on.. 1. If you see small fella malicious .exe file never load it to virustotal.com or any other virus researching website. Otherwise the info about the hack is not a secret anymore. The fact that your company is under ransomware attack is already known by filthy predators data security agents who will post in their pity twitters the fresh known news “OMG ANOTHER RANSOMWARE NOW IT’S “Your company name LLC!!!!! We are all gonna die aaaaaa halp” 2. No any public announcements about the hack or data leakage. And do not applicate to law enforcement. If you commit this actions, more serious consequences can occur and you pay much more than a ransom amount. Law structures like GDPR in this case can oblige you to pay huge fine. 3. As soon as you see your network compromised, follow the link inside any note and follow instructions. 4. Calm your employees. Explain them that this is a drill. And you test your network security systems. 5. If you decide to hire the data recovery company, obligate them to do not inform anyone and any third party about details of the attack. We strongly do not recommend to cooperate with data recovery company, because they do absolutely nothing that you can do by yourself and take money for it. all communications with hackers could be conducted by your it department indipendently without any extra payments. 6. Do not try to decrypt your data via 3rd party software. Most of ransomware use strong encryption algorthm and you can harm your files by using 3rd party decryption software.

URLs

http://wavbeudogz6byhnardd2lkp2jafims3j7tj6k6qnywchn2csngvtffqd.onion/

http://os3xs2l3ftdqeuhxyuo4e6ymxvknp3gx6abordkcjde4coe37k66xyid.onion/4ee7ff7421bcb2ab35c523623ce11174c037e7db0562578b8a245630fc16a047

Signatures

Babuk Locker
RaaS first seen in 2021 initially called Vasa Locker.
ransomware babuk
Deletes shadow copies 2 TTPs
Ransomware often targets backup files to inhibit system recovery.
ransomware

File Deletion
T1107

Inhibit System Recovery
T1490

Modifies extensions of user files 18 IoCs

Ransomware generally changes the extension on encrypted files.

ransomware

Processes:

babuk.exe

description	ioc	process
File opened for modification	C:\Users\Admin\Pictures\CheckpointRename.raw.babyk	babuk.exe
File renamed	C:\Users\Admin\Pictures\CloseBlock.tiff => C:\Users\Admin\Pictures\CloseBlock.tiff.babyk	babuk.exe
File opened for modification	C:\Users\Admin\Pictures\CloseBlock.tiff.babyk	babuk.exe
File opened for modification	C:\Users\Admin\Pictures\GroupUnregister.tiff.babyk	babuk.exe
File renamed	C:\Users\Admin\Pictures\LimitSend.raw => C:\Users\Admin\Pictures\LimitSend.raw.babyk	babuk.exe
File opened for modification	C:\Users\Admin\Pictures\RestoreDisconnect.crw.babyk	babuk.exe
File opened for modification	C:\Users\Admin\Pictures\StopPing.raw.babyk	babuk.exe
File opened for modification	C:\Users\Admin\Pictures\CloseBlock.tiff	babuk.exe
File renamed	C:\Users\Admin\Pictures\ConnectOut.png => C:\Users\Admin\Pictures\ConnectOut.png.babyk	babuk.exe
File opened for modification	C:\Users\Admin\Pictures\LimitSend.raw.babyk	babuk.exe
File renamed	C:\Users\Admin\Pictures\RestoreDisconnect.crw => C:\Users\Admin\Pictures\RestoreDisconnect.crw.babyk	babuk.exe
File renamed	C:\Users\Admin\Pictures\CheckpointRename.raw => C:\Users\Admin\Pictures\CheckpointRename.raw.babyk	babuk.exe
File opened for modification	C:\Users\Admin\Pictures\ConnectOut.png.babyk	babuk.exe
File renamed	C:\Users\Admin\Pictures\GroupUnregister.tiff => C:\Users\Admin\Pictures\GroupUnregister.tiff.babyk	babuk.exe
File renamed	C:\Users\Admin\Pictures\StopPing.raw => C:\Users\Admin\Pictures\StopPing.raw.babyk	babuk.exe
File opened for modification	C:\Users\Admin\Pictures\GroupUnregister.tiff	babuk.exe
File renamed	C:\Users\Admin\Pictures\UnblockDebug.raw => C:\Users\Admin\Pictures\UnblockDebug.raw.babyk	babuk.exe
File opened for modification	C:\Users\Admin\Pictures\UnblockDebug.raw.babyk	babuk.exe

Enumerates connected drives 3 TTPs 24 IoCs

Attempts to read the root path of hard drives other than the default C: drive.

Query Registry

T1012

Peripheral Device Discovery

T1120

System Information Discovery

T1082

Processes:

babuk.exe

description	ioc	process
File opened (read-only)	\??\P:	babuk.exe
File opened (read-only)	\??\S:	babuk.exe
File opened (read-only)	\??\Z:	babuk.exe
File opened (read-only)	\??\V:	babuk.exe
File opened (read-only)	\??\J:	babuk.exe
File opened (read-only)	\??\E:	babuk.exe
File opened (read-only)	\??\I:	babuk.exe
File opened (read-only)	\??\A:	babuk.exe
File opened (read-only)	\??\F:	babuk.exe
File opened (read-only)	\??\K:	babuk.exe
File opened (read-only)	\??\L:	babuk.exe
File opened (read-only)	\??\N:	babuk.exe
File opened (read-only)	\??\W:	babuk.exe
File opened (read-only)	\??\R:	babuk.exe
File opened (read-only)	\??\Y:	babuk.exe
File opened (read-only)	\??\O:	babuk.exe
File opened (read-only)	\??\H:	babuk.exe
File opened (read-only)	\??\X:	babuk.exe
File opened (read-only)	\??\B:	babuk.exe
File opened (read-only)	\??\M:	babuk.exe
File opened (read-only)	\??\Q:	babuk.exe
File opened (read-only)	\??\T:	babuk.exe
File opened (read-only)	\??\U:	babuk.exe
File opened (read-only)	\??\G:	babuk.exe

Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.

System Information Discovery
T1082
Interacts with shadow copies 2 TTPs 2 IoCs
Shadow copies are often targeted by ransomware to inhibit system recovery.
ransomware

File Deletion
T1107

Inhibit System Recovery
T1490

Processes:

vssadmin.exevssadmin.exe

pid process

2948 vssadmin.exe
3504 vssadmin.exe
Suspicious behavior: EnumeratesProcesses 2 IoCs

Processes:

babuk.exe

pid process

740 babuk.exe
740 babuk.exe
Suspicious use of AdjustPrivilegeToken 3 IoCs

Processes:

vssvc.exe

description pid process

Token: SeBackupPrivilege 2304 vssvc.exe
Token: SeRestorePrivilege 2304 vssvc.exe
Token: SeAuditPrivilege 2304 vssvc.exe

pid	process
2948	vssadmin.exe
3504	vssadmin.exe

pid	process
740	babuk.exe
740	babuk.exe

description	pid	process
Token: SeBackupPrivilege	2304	vssvc.exe
Token: SeRestorePrivilege	2304	vssvc.exe
Token: SeAuditPrivilege	2304	vssvc.exe

Suspicious use of WriteProcessMemory 8 IoCs

Processes:

babuk.execmd.execmd.exe

description	pid	process	target process
PID 740 wrote to memory of 4024	740	babuk.exe	cmd.exe
PID 740 wrote to memory of 4024	740	babuk.exe	cmd.exe
PID 4024 wrote to memory of 2948	4024	cmd.exe	vssadmin.exe
PID 4024 wrote to memory of 2948	4024	cmd.exe	vssadmin.exe
PID 740 wrote to memory of 2068	740	babuk.exe	cmd.exe
PID 740 wrote to memory of 2068	740	babuk.exe	cmd.exe
PID 2068 wrote to memory of 3504	2068	cmd.exe	vssadmin.exe
PID 2068 wrote to memory of 3504	2068	cmd.exe	vssadmin.exe

C:\Users\Admin\AppData\Local\Temp\babuk.exe
"C:\Users\Admin\AppData\Local\Temp\babuk.exe"
1⤵
- Modifies extensions of user files
- Enumerates connected drives
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:740
- C:\Windows\System32\cmd.exe
  "C:\Windows\System32\cmd.exe" /c vssadmin.exe delete shadows /all /quiet
  2⤵
  - Suspicious use of WriteProcessMemory
  PID:4024
- - C:\Windows\system32\vssadmin.exe
    vssadmin.exe delete shadows /all /quiet
    3⤵
    - Interacts with shadow copies
    PID:2948
- C:\Windows\System32\cmd.exe
  "C:\Windows\System32\cmd.exe" /c vssadmin.exe delete shadows /all /quiet
  2⤵
  - Suspicious use of WriteProcessMemory
  PID:2068
- - C:\Windows\system32\vssadmin.exe
    vssadmin.exe delete shadows /all /quiet
    3⤵
    - Interacts with shadow copies
    PID:3504