Analysis
-
max time kernel
22s -
max time network
26s -
platform
windows10-2004_x64 -
resource
win10v2004-20220414-en -
submitted
12-07-2022 12:50
Static task
static1
Behavioral task
behavioral1
Sample
4a90cac96c04e3cf0b797290dbcc1403d36fd6a6fa26e87c865283ec4086621b.exe
Resource
win7-20220414-en
Behavioral task
behavioral2
Sample
4a90cac96c04e3cf0b797290dbcc1403d36fd6a6fa26e87c865283ec4086621b.exe
Resource
win10v2004-20220414-en
General
-
Target
4a90cac96c04e3cf0b797290dbcc1403d36fd6a6fa26e87c865283ec4086621b.exe
-
Size
79KB
-
MD5
c82d0e4f5eab0bc5c26f79628cbef4fc
-
SHA1
68e68a909a04803528d156b4705567164c221270
-
SHA256
4a90cac96c04e3cf0b797290dbcc1403d36fd6a6fa26e87c865283ec4086621b
-
SHA512
8a272a263ce742b84c1a99ae5073a735c71381257382811914f995aaf7f04d24bff669116786b113a9b2c6ca5400523acb7a69fa89d2f135af593673055ead8a
Malware Config
Extracted
metasploit
encoder/call4_dword_xor
Signatures
-
MetaSploit
Detected malicious payload which is part of the Metasploit Framework, likely generated with msfvenom or similar.
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
4a90cac96c04e3cf0b797290dbcc1403d36fd6a6fa26e87c865283ec4086621b.exedescription pid process target process PID 1264 set thread context of 4780 1264 4a90cac96c04e3cf0b797290dbcc1403d36fd6a6fa26e87c865283ec4086621b.exe 4a90cac96c04e3cf0b797290dbcc1403d36fd6a6fa26e87c865283ec4086621b.exe -
Program crash 2 IoCs
Processes:
WerFault.exeWerFault.exepid pid_target process target process 5024 4780 WerFault.exe 4a90cac96c04e3cf0b797290dbcc1403d36fd6a6fa26e87c865283ec4086621b.exe 2560 1264 WerFault.exe 4a90cac96c04e3cf0b797290dbcc1403d36fd6a6fa26e87c865283ec4086621b.exe -
Suspicious use of WriteProcessMemory 5 IoCs
Processes:
4a90cac96c04e3cf0b797290dbcc1403d36fd6a6fa26e87c865283ec4086621b.exedescription pid process target process PID 1264 wrote to memory of 4780 1264 4a90cac96c04e3cf0b797290dbcc1403d36fd6a6fa26e87c865283ec4086621b.exe 4a90cac96c04e3cf0b797290dbcc1403d36fd6a6fa26e87c865283ec4086621b.exe PID 1264 wrote to memory of 4780 1264 4a90cac96c04e3cf0b797290dbcc1403d36fd6a6fa26e87c865283ec4086621b.exe 4a90cac96c04e3cf0b797290dbcc1403d36fd6a6fa26e87c865283ec4086621b.exe PID 1264 wrote to memory of 4780 1264 4a90cac96c04e3cf0b797290dbcc1403d36fd6a6fa26e87c865283ec4086621b.exe 4a90cac96c04e3cf0b797290dbcc1403d36fd6a6fa26e87c865283ec4086621b.exe PID 1264 wrote to memory of 4780 1264 4a90cac96c04e3cf0b797290dbcc1403d36fd6a6fa26e87c865283ec4086621b.exe 4a90cac96c04e3cf0b797290dbcc1403d36fd6a6fa26e87c865283ec4086621b.exe PID 1264 wrote to memory of 4780 1264 4a90cac96c04e3cf0b797290dbcc1403d36fd6a6fa26e87c865283ec4086621b.exe 4a90cac96c04e3cf0b797290dbcc1403d36fd6a6fa26e87c865283ec4086621b.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\4a90cac96c04e3cf0b797290dbcc1403d36fd6a6fa26e87c865283ec4086621b.exe"C:\Users\Admin\AppData\Local\Temp\4a90cac96c04e3cf0b797290dbcc1403d36fd6a6fa26e87c865283ec4086621b.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
-
C:\Users\Admin\AppData\Local\Temp\4a90cac96c04e3cf0b797290dbcc1403d36fd6a6fa26e87c865283ec4086621b.exeC:\Users\Admin\AppData\Local\Temp\4a90cac96c04e3cf0b797290dbcc1403d36fd6a6fa26e87c865283ec4086621b.exe2⤵
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4780 -s 123⤵
- Program crash
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1264 -s 2562⤵
- Program crash
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 420 -p 4780 -ip 47801⤵
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 456 -p 1264 -ip 12641⤵
Network
MITRE ATT&CK Matrix
Replay Monitor
Loading Replay Monitor...
Downloads
-
memory/1264-132-0x0000000001000000-0x0000000001015000-memory.dmpFilesize
84KB
-
memory/1264-133-0x0000000001000000-0x0000000001015000-memory.dmpFilesize
84KB
-
memory/4780-130-0x0000000000000000-mapping.dmp
-
memory/4780-131-0x0000000029A00000-0x0000000029A1E000-memory.dmpFilesize
120KB