Analysis
-
max time kernel
136s -
max time network
156s -
platform
windows10-2004_x64 -
resource
win10v2004-20220414-en -
submitted
27/04/2022, 15:22
Static task
static1
Behavioral task
behavioral1
Sample
3b78f0d649e384179c12f8efcd36eb06d1484198c413f0f00e7124b05f50dedc.exe
Resource
win7-20220414-en
General
-
Target
3b78f0d649e384179c12f8efcd36eb06d1484198c413f0f00e7124b05f50dedc.exe
-
Size
812KB
-
MD5
cfa968813fa0bfd7dc8dc2ebd0a1d761
-
SHA1
397f43f47ab3ff37b4dabe4fa5eae15ca506fff2
-
SHA256
3b78f0d649e384179c12f8efcd36eb06d1484198c413f0f00e7124b05f50dedc
-
SHA512
ce22c402088e342a6b4814e55f96a3e82b0aa358ba36ad6765cf9f2c62093d558e50d4d384d34a373b80d8d32095b2e6c4a0f0de03055ee5713e0b2a632f8dae
Malware Config
Extracted
quasar
2.1.0.0
Office04
127.0.0.1:4782
microsoft.ddns.net:1603
VNM_MUTEX_7zNZZlxRKgAO9rNOW0
-
encryption_key
rmN2FkutvROvHylehfK8
-
install_name
Client.exe
-
log_directory
Logs
-
reconnect_delay
3000
-
startup_key
Venom Client Startup
-
subdirectory
SubDir
Signatures
-
Contains code to disable Windows Defender 1 IoCs
A .NET executable tasked with disabling Windows Defender capabilities such as realtime monitoring, blocking at first seen, etc.
resource yara_rule behavioral2/memory/3108-139-0x0000000000400000-0x000000000048C000-memory.dmp disable_win_def -
Quasar Payload 1 IoCs
resource yara_rule behavioral2/memory/3108-139-0x0000000000400000-0x000000000048C000-memory.dmp family_quasar -
Adds Run key to start application 2 TTPs 1 IoCs
description ioc Process Set value (str) \REGISTRY\USER\S-1-5-21-1809750270-3141839489-3074374771-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\HWMonitor = "C:\\Users\\Admin\\AppData\\Roaming\\HWMonitor\\chome_exe.exe" powershell.exe -
Looks up external IP address via web service 1 IoCs
Uses a legitimate IP lookup service to find the infected system's external IP.
flow ioc 58 ip-api.com -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4180 set thread context of 3108 4180 3b78f0d649e384179c12f8efcd36eb06d1484198c413f0f00e7124b05f50dedc.exe 101 -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 4180 3b78f0d649e384179c12f8efcd36eb06d1484198c413f0f00e7124b05f50dedc.exe 4180 3b78f0d649e384179c12f8efcd36eb06d1484198c413f0f00e7124b05f50dedc.exe 3268 powershell.exe 3268 powershell.exe -
Suspicious use of AdjustPrivilegeToken 4 IoCs
description pid Process Token: SeDebugPrivilege 4180 3b78f0d649e384179c12f8efcd36eb06d1484198c413f0f00e7124b05f50dedc.exe Token: SeDebugPrivilege 3268 powershell.exe Token: SeDebugPrivilege 3108 RegAsm.exe Token: SeDebugPrivilege 3108 RegAsm.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 3108 RegAsm.exe -
Suspicious use of WriteProcessMemory 14 IoCs
description pid Process procid_target PID 4180 wrote to memory of 3268 4180 3b78f0d649e384179c12f8efcd36eb06d1484198c413f0f00e7124b05f50dedc.exe 98 PID 4180 wrote to memory of 3268 4180 3b78f0d649e384179c12f8efcd36eb06d1484198c413f0f00e7124b05f50dedc.exe 98 PID 4180 wrote to memory of 3268 4180 3b78f0d649e384179c12f8efcd36eb06d1484198c413f0f00e7124b05f50dedc.exe 98 PID 4180 wrote to memory of 2092 4180 3b78f0d649e384179c12f8efcd36eb06d1484198c413f0f00e7124b05f50dedc.exe 100 PID 4180 wrote to memory of 2092 4180 3b78f0d649e384179c12f8efcd36eb06d1484198c413f0f00e7124b05f50dedc.exe 100 PID 4180 wrote to memory of 2092 4180 3b78f0d649e384179c12f8efcd36eb06d1484198c413f0f00e7124b05f50dedc.exe 100 PID 4180 wrote to memory of 3108 4180 3b78f0d649e384179c12f8efcd36eb06d1484198c413f0f00e7124b05f50dedc.exe 101 PID 4180 wrote to memory of 3108 4180 3b78f0d649e384179c12f8efcd36eb06d1484198c413f0f00e7124b05f50dedc.exe 101 PID 4180 wrote to memory of 3108 4180 3b78f0d649e384179c12f8efcd36eb06d1484198c413f0f00e7124b05f50dedc.exe 101 PID 4180 wrote to memory of 3108 4180 3b78f0d649e384179c12f8efcd36eb06d1484198c413f0f00e7124b05f50dedc.exe 101 PID 4180 wrote to memory of 3108 4180 3b78f0d649e384179c12f8efcd36eb06d1484198c413f0f00e7124b05f50dedc.exe 101 PID 4180 wrote to memory of 3108 4180 3b78f0d649e384179c12f8efcd36eb06d1484198c413f0f00e7124b05f50dedc.exe 101 PID 4180 wrote to memory of 3108 4180 3b78f0d649e384179c12f8efcd36eb06d1484198c413f0f00e7124b05f50dedc.exe 101 PID 4180 wrote to memory of 3108 4180 3b78f0d649e384179c12f8efcd36eb06d1484198c413f0f00e7124b05f50dedc.exe 101
Processes
-
C:\Users\Admin\AppData\Local\Temp\3b78f0d649e384179c12f8efcd36eb06d1484198c413f0f00e7124b05f50dedc.exe"C:\Users\Admin\AppData\Local\Temp\3b78f0d649e384179c12f8efcd36eb06d1484198c413f0f00e7124b05f50dedc.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:4180 -
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe"powershell.exe" Remove-ItemProperty -Path 'HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Run' -Name 'HWMonitor';New-ItemProperty -Path 'HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Run' -Name 'HWMonitor' -Value '"C:\Users\Admin\AppData\Roaming\HWMonitor\chome_exe.exe"' -PropertyType 'String'2⤵
- Adds Run key to start application
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
PID:3268
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:2092
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
PID:3108
-