Analysis
-
max time kernel
173s -
max time network
238s -
platform
windows7_x64 -
resource
win7-20220812-en -
resource tags
arch:x64arch:x86image:win7-20220812-enlocale:en-usos:windows7-x64system -
submitted
22-10-2022 06:35
Static task
static1
Behavioral task
behavioral1
Sample
54e5e90fbafdf6f051f2c89da50a4b95.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
54e5e90fbafdf6f051f2c89da50a4b95.exe
Resource
win10v2004-20220901-en
General
-
Target
54e5e90fbafdf6f051f2c89da50a4b95.exe
-
Size
192KB
-
MD5
54e5e90fbafdf6f051f2c89da50a4b95
-
SHA1
f1e4459301f216cd4ff0bd27deb9d5a910ef9f5b
-
SHA256
e4d62d22644bd8f7b85b47328cbac771dd76473902ac2a92cb3bb06ff7ed091a
-
SHA512
a22ccbff0ff8da17a8a3a04f38f644b041b47e1c995b8b40b9a7ec4577c850439d244b966834f86d7ce6dd4ec3369ac11d9950429a3336b9b9c53095ea9b0b4b
-
SSDEEP
1536:bB+R6Ywvj1k3w45lEdhKzoUSFeuiS2FIlKbz0PEziNQKjoa:tAwvj1Mw4shKzoUSFeuiS2FIIcwKoa
Malware Config
Signatures
-
Downloads MZ/PE file
-
Adds Run key to start application 2 TTPs 1 IoCs
Processes:
54e5e90fbafdf6f051f2c89da50a4b95.exedescription ioc process Set value (str) \REGISTRY\USER\S-1-5-21-2292972927-2705560509-2768824231-1000\Software\Microsoft\Windows\CurrentVersion\Run\Qusfukpzsf = "\"C:\\Users\\Admin\\AppData\\Roaming\\Vvxyeheuij\\Qusfukpzsf.exe\"" 54e5e90fbafdf6f051f2c89da50a4b95.exe -
Suspicious use of SetThreadContext 2 IoCs
Processes:
54e5e90fbafdf6f051f2c89da50a4b95.exe54e5e90fbafdf6f051f2c89da50a4b95.exedescription pid process target process PID 1628 set thread context of 772 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 772 set thread context of 1112 772 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Suspicious behavior: EnumeratesProcesses 4 IoCs
Processes:
powershell.exe54e5e90fbafdf6f051f2c89da50a4b95.exepid process 1664 powershell.exe 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
Processes:
54e5e90fbafdf6f051f2c89da50a4b95.exepowershell.exedescription pid process Token: SeDebugPrivilege 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe Token: SeDebugPrivilege 1664 powershell.exe -
Suspicious use of WriteProcessMemory 37 IoCs
Processes:
54e5e90fbafdf6f051f2c89da50a4b95.exe54e5e90fbafdf6f051f2c89da50a4b95.exedescription pid process target process PID 1628 wrote to memory of 1664 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe powershell.exe PID 1628 wrote to memory of 1664 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe powershell.exe PID 1628 wrote to memory of 1664 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe powershell.exe PID 1628 wrote to memory of 1664 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe powershell.exe PID 1628 wrote to memory of 1356 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 1628 wrote to memory of 1356 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 1628 wrote to memory of 1356 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 1628 wrote to memory of 1356 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 1628 wrote to memory of 1544 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 1628 wrote to memory of 1544 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 1628 wrote to memory of 1544 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 1628 wrote to memory of 1544 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 1628 wrote to memory of 520 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 1628 wrote to memory of 520 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 1628 wrote to memory of 520 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 1628 wrote to memory of 520 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 1628 wrote to memory of 772 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 1628 wrote to memory of 772 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 1628 wrote to memory of 772 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 1628 wrote to memory of 772 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 1628 wrote to memory of 772 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 1628 wrote to memory of 772 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 1628 wrote to memory of 772 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 1628 wrote to memory of 772 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 1628 wrote to memory of 772 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 1628 wrote to memory of 772 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 1628 wrote to memory of 772 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 1628 wrote to memory of 772 1628 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 772 wrote to memory of 1112 772 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 772 wrote to memory of 1112 772 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 772 wrote to memory of 1112 772 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 772 wrote to memory of 1112 772 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 772 wrote to memory of 1112 772 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 772 wrote to memory of 1112 772 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 772 wrote to memory of 1112 772 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 772 wrote to memory of 1112 772 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe PID 772 wrote to memory of 1112 772 54e5e90fbafdf6f051f2c89da50a4b95.exe 54e5e90fbafdf6f051f2c89da50a4b95.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\54e5e90fbafdf6f051f2c89da50a4b95.exe"C:\Users\Admin\AppData\Local\Temp\54e5e90fbafdf6f051f2c89da50a4b95.exe"1⤵
- Adds Run key to start application
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:1628 -
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" -enc UwB0AGEAcgB0AC0AUwBsAGUAZQBwACAALQBTAGUAYwBvAG4AZABzACAANQAwAA==2⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
PID:1664 -
C:\Users\Admin\AppData\Local\Temp\54e5e90fbafdf6f051f2c89da50a4b95.exeC:\Users\Admin\AppData\Local\Temp\54e5e90fbafdf6f051f2c89da50a4b95.exe2⤵PID:1356
-
C:\Users\Admin\AppData\Local\Temp\54e5e90fbafdf6f051f2c89da50a4b95.exeC:\Users\Admin\AppData\Local\Temp\54e5e90fbafdf6f051f2c89da50a4b95.exe2⤵PID:1544
-
C:\Users\Admin\AppData\Local\Temp\54e5e90fbafdf6f051f2c89da50a4b95.exeC:\Users\Admin\AppData\Local\Temp\54e5e90fbafdf6f051f2c89da50a4b95.exe2⤵PID:520
-
C:\Users\Admin\AppData\Local\Temp\54e5e90fbafdf6f051f2c89da50a4b95.exeC:\Users\Admin\AppData\Local\Temp\54e5e90fbafdf6f051f2c89da50a4b95.exe2⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:772 -
C:\Users\Admin\AppData\Local\Temp\54e5e90fbafdf6f051f2c89da50a4b95.exe"C:\Users\Admin\AppData\Local\Temp\54e5e90fbafdf6f051f2c89da50a4b95.exe"3⤵PID:1112