Analysis
-
max time kernel
103s -
max time network
118s -
platform
windows7_x64 -
resource
win7-20220414-en -
submitted
01-07-2022 15:03
Static task
static1
Behavioral task
behavioral1
Sample
5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe
Resource
win7-20220414-en
windows7_x64
0 signatures
0 seconds
General
-
Target
5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe
-
Size
1.2MB
-
MD5
003d19970194080b5cf4943b45ffb523
-
SHA1
d1215cc8a501c297157ca4d44bc683f95c747f86
-
SHA256
5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f
-
SHA512
62f69b3c5eaf138b7ed3c30b1e9b79b2ff4fec9d17f537d2f4fc5cd6fe3d775244df6c9449df2ad1694207de1310be0d3ff875ddae73cb8b9c0f5379f8a9a217
Malware Config
Signatures
-
NetWire RAT payload 3 IoCs
Processes:
resource yara_rule behavioral1/memory/1460-57-0x00000000000C0000-0x00000000000EB000-memory.dmp netwire behavioral1/memory/1460-65-0x00000000000C26D0-mapping.dmp netwire behavioral1/memory/1460-71-0x00000000000C0000-0x00000000000EB000-memory.dmp netwire -
Drops startup file 1 IoCs
Processes:
5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exedescription ioc process File opened for modification C:\Users\Admin\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\calc.url 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe -
Suspicious use of SetThreadContext 1 IoCs
Processes:
5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exedescription pid process target process PID 1040 set thread context of 1460 1040 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 1228 1040 WerFault.exe 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe -
Suspicious behavior: EnumeratesProcesses 2 IoCs
Processes:
5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exepid process 1040 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe 1040 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe -
Suspicious use of FindShellTrayWindow 3 IoCs
Processes:
5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exepid process 1040 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe 1040 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe 1040 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe -
Suspicious use of SendNotifyMessage 3 IoCs
Processes:
5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exepid process 1040 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe 1040 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe 1040 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe -
Suspicious use of WriteProcessMemory 10 IoCs
Processes:
5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exedescription pid process target process PID 1040 wrote to memory of 1460 1040 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe PID 1040 wrote to memory of 1460 1040 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe PID 1040 wrote to memory of 1460 1040 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe PID 1040 wrote to memory of 1460 1040 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe PID 1040 wrote to memory of 1460 1040 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe PID 1040 wrote to memory of 1460 1040 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe PID 1040 wrote to memory of 1228 1040 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe WerFault.exe PID 1040 wrote to memory of 1228 1040 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe WerFault.exe PID 1040 wrote to memory of 1228 1040 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe WerFault.exe PID 1040 wrote to memory of 1228 1040 5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe WerFault.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe"C:\Users\Admin\AppData\Local\Temp\5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe"1⤵
- Drops startup file
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of FindShellTrayWindow
- Suspicious use of SendNotifyMessage
- Suspicious use of WriteProcessMemory
PID:1040 -
C:\Users\Admin\AppData\Local\Temp\5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe"C:\Users\Admin\AppData\Local\Temp\5a9dc7a0a78582178b5ecc4b83725338027de4ec8d68ccf2f22ea6e92aab509f.exe"2⤵PID:1460
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1040 -s 3242⤵
- Program crash
PID:1228