Analysis
-
max time kernel
138s -
max time network
166s -
platform
windows10-2004_x64 -
resource
win10v2004-20220414-en -
submitted
03-07-2022 17:21
Static task
static1
Behavioral task
behavioral1
Sample
3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe
Resource
win7-20220414-en
windows7_x64
0 signatures
0 seconds
General
-
Target
3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe
-
Size
452KB
-
MD5
ca2d6a008af257899c489df9f21a6127
-
SHA1
e998bdf611639bdccefb2f69df1bb7ce5d8a8be9
-
SHA256
3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5
-
SHA512
d2b33a6ff87e730eb3e987da8c61a276018f00f85c4d0a9b65bf4f2cff03a4c1367ed95e3d5f2abfac92c212011f6f4b7d6f529840c4d0880e357219650f31db
Malware Config
Extracted
Family
netwire
C2
185.84.181.80:3360
Attributes
-
activex_autorun
false
-
copy_executable
false
-
delete_original
false
-
host_id
HostId-%Rand%
-
keylogger_dir
%AppData%\Logs\
-
lock_executable
false
-
offline_keylogger
true
-
password
Password
-
registry_autorun
false
-
use_mutex
false
Signatures
-
NetWire RAT payload 4 IoCs
Processes:
resource yara_rule behavioral2/memory/3172-133-0x0000000000000000-mapping.dmp netwire behavioral2/memory/3172-134-0x0000000000400000-0x000000000042C000-memory.dmp netwire behavioral2/memory/3172-137-0x0000000000400000-0x000000000042C000-memory.dmp netwire behavioral2/memory/3172-138-0x0000000000400000-0x000000000042C000-memory.dmp netwire -
Suspicious use of SetThreadContext 1 IoCs
Processes:
3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exedescription pid process target process PID 812 set thread context of 3172 812 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe -
Suspicious use of FindShellTrayWindow 2 IoCs
Processes:
3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exepid process 812 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe 812 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe -
Suspicious use of SendNotifyMessage 2 IoCs
Processes:
3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exepid process 812 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe 812 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
Processes:
3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exepid process 812 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe -
Suspicious use of WriteProcessMemory 12 IoCs
Processes:
3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exedescription pid process target process PID 812 wrote to memory of 3172 812 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe PID 812 wrote to memory of 3172 812 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe PID 812 wrote to memory of 3172 812 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe PID 812 wrote to memory of 3172 812 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe PID 812 wrote to memory of 3172 812 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe PID 812 wrote to memory of 3172 812 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe PID 812 wrote to memory of 3172 812 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe PID 812 wrote to memory of 3172 812 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe PID 812 wrote to memory of 3172 812 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe PID 812 wrote to memory of 3172 812 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe PID 812 wrote to memory of 3172 812 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe PID 812 wrote to memory of 3172 812 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe 3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe"C:\Users\Admin\AppData\Local\Temp\3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of FindShellTrayWindow
- Suspicious use of SendNotifyMessage
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:812 -
C:\Users\Admin\AppData\Local\Temp\3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe"C:\Users\Admin\AppData\Local\Temp\3b2e93dd6e7130f1fed2b9436e580c4e54894393f1520b32d919feee537deab5.exe"2⤵PID:3172