Analysis
-
max time kernel
206s -
max time network
210s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
04/12/2022, 10:06
Static task
static1
Behavioral task
behavioral1
Sample
8fd157db3769e032731a13145201d0b7968adfcc2a7f659ff2108e9fa84ec49e.exe
Resource
win7-20220812-en
3 signatures
150 seconds
Behavioral task
behavioral2
Sample
8fd157db3769e032731a13145201d0b7968adfcc2a7f659ff2108e9fa84ec49e.exe
Resource
win10v2004-20220812-en
4 signatures
150 seconds
General
-
Target
8fd157db3769e032731a13145201d0b7968adfcc2a7f659ff2108e9fa84ec49e.exe
-
Size
640KB
-
MD5
187bc6bc24cbf198892b397a8ddce5ab
-
SHA1
c36a857b8ffb5b193b51335e1ebb449360c60aa5
-
SHA256
8fd157db3769e032731a13145201d0b7968adfcc2a7f659ff2108e9fa84ec49e
-
SHA512
3ac63ace3e08708263f3022ae36d5f9dc5b660296a09ccf42e4c482ae3ee3ec340108b8fc5ab2ef1c0eda8fec88d6f6fb57bf33839c7f14fa25e9472a4e561a3
-
SSDEEP
6144:NNbG4BKing0gSgJjpSCbMHDP6l4c8lBhzEX:+46j7beDP6lQl7E
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 380 set thread context of 2628 380 8fd157db3769e032731a13145201d0b7968adfcc2a7f659ff2108e9fa84ec49e.exe 78 -
Program crash 1 IoCs
pid pid_target Process procid_target 4708 2628 WerFault.exe 78 -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 380 8fd157db3769e032731a13145201d0b7968adfcc2a7f659ff2108e9fa84ec49e.exe -
Suspicious use of WriteProcessMemory 8 IoCs
description pid Process procid_target PID 380 wrote to memory of 2628 380 8fd157db3769e032731a13145201d0b7968adfcc2a7f659ff2108e9fa84ec49e.exe 78 PID 380 wrote to memory of 2628 380 8fd157db3769e032731a13145201d0b7968adfcc2a7f659ff2108e9fa84ec49e.exe 78 PID 380 wrote to memory of 2628 380 8fd157db3769e032731a13145201d0b7968adfcc2a7f659ff2108e9fa84ec49e.exe 78 PID 380 wrote to memory of 2628 380 8fd157db3769e032731a13145201d0b7968adfcc2a7f659ff2108e9fa84ec49e.exe 78 PID 380 wrote to memory of 2628 380 8fd157db3769e032731a13145201d0b7968adfcc2a7f659ff2108e9fa84ec49e.exe 78 PID 380 wrote to memory of 2628 380 8fd157db3769e032731a13145201d0b7968adfcc2a7f659ff2108e9fa84ec49e.exe 78 PID 380 wrote to memory of 2628 380 8fd157db3769e032731a13145201d0b7968adfcc2a7f659ff2108e9fa84ec49e.exe 78 PID 380 wrote to memory of 2628 380 8fd157db3769e032731a13145201d0b7968adfcc2a7f659ff2108e9fa84ec49e.exe 78
Processes
-
C:\Users\Admin\AppData\Local\Temp\8fd157db3769e032731a13145201d0b7968adfcc2a7f659ff2108e9fa84ec49e.exe"C:\Users\Admin\AppData\Local\Temp\8fd157db3769e032731a13145201d0b7968adfcc2a7f659ff2108e9fa84ec49e.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:380 -
C:\Users\Admin\AppData\Local\Temp\8fd157db3769e032731a13145201d0b7968adfcc2a7f659ff2108e9fa84ec49e.exeC:\Users\Admin\AppData\Local\Temp\8fd157db3769e032731a13145201d0b7968adfcc2a7f659ff2108e9fa84ec49e.exe2⤵PID:2628
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2628 -s 4683⤵
- Program crash
PID:4708
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 364 -p 2628 -ip 26281⤵PID:4956