Analysis
-
max time kernel
196s -
max time network
238s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
19/10/2022, 15:08
Static task
static1
Behavioral task
behavioral1
Sample
4b5bda9fd666af06c6e99744ecd24f92b352fa4d849eeabe2103762b4a1a4081.exe
Resource
win7-20220812-en
5 signatures
150 seconds
Behavioral task
behavioral2
Sample
4b5bda9fd666af06c6e99744ecd24f92b352fa4d849eeabe2103762b4a1a4081.exe
Resource
win10v2004-20220812-en
5 signatures
150 seconds
General
-
Target
4b5bda9fd666af06c6e99744ecd24f92b352fa4d849eeabe2103762b4a1a4081.exe
-
Size
96KB
-
MD5
82eebe059fe8374b81faefd2ec5f199d
-
SHA1
f27a1f67c04215736842d934dc1faa95bc5ea48b
-
SHA256
4b5bda9fd666af06c6e99744ecd24f92b352fa4d849eeabe2103762b4a1a4081
-
SHA512
81f4454a39351c12b77d0f8c2545451ea31a1a3f9d586248c2654e3ea0eb32c12bff9ad37fdab6eff278bb2fc89fe84f4426eddf4cc261eb42adab88e1326d78
-
SSDEEP
3072:j7DfM5VU2nQTCaXZ/HozwAgjTtmcIFsv7:ri50hHofgjTgcIFG
Score
8/10
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/736-133-0x0000000000400000-0x0000000002728000-memory.dmp upx behavioral2/memory/736-135-0x0000000000400000-0x0000000000409000-memory.dmp upx behavioral2/memory/736-137-0x0000000000400000-0x0000000002728000-memory.dmp upx behavioral2/memory/736-138-0x0000000000400000-0x0000000002728000-memory.dmp upx behavioral2/memory/736-139-0x0000000000400000-0x0000000000409000-memory.dmp upx behavioral2/memory/736-140-0x0000000000400000-0x0000000000409000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 876 set thread context of 736 876 4b5bda9fd666af06c6e99744ecd24f92b352fa4d849eeabe2103762b4a1a4081.exe 81 -
Suspicious behavior: EnumeratesProcesses 2 IoCs
pid Process 876 4b5bda9fd666af06c6e99744ecd24f92b352fa4d849eeabe2103762b4a1a4081.exe 876 4b5bda9fd666af06c6e99744ecd24f92b352fa4d849eeabe2103762b4a1a4081.exe -
Suspicious use of SetWindowsHookEx 2 IoCs
pid Process 876 4b5bda9fd666af06c6e99744ecd24f92b352fa4d849eeabe2103762b4a1a4081.exe 876 4b5bda9fd666af06c6e99744ecd24f92b352fa4d849eeabe2103762b4a1a4081.exe -
Suspicious use of WriteProcessMemory 9 IoCs
description pid Process procid_target PID 876 wrote to memory of 736 876 4b5bda9fd666af06c6e99744ecd24f92b352fa4d849eeabe2103762b4a1a4081.exe 81 PID 876 wrote to memory of 736 876 4b5bda9fd666af06c6e99744ecd24f92b352fa4d849eeabe2103762b4a1a4081.exe 81 PID 876 wrote to memory of 736 876 4b5bda9fd666af06c6e99744ecd24f92b352fa4d849eeabe2103762b4a1a4081.exe 81 PID 876 wrote to memory of 736 876 4b5bda9fd666af06c6e99744ecd24f92b352fa4d849eeabe2103762b4a1a4081.exe 81 PID 876 wrote to memory of 736 876 4b5bda9fd666af06c6e99744ecd24f92b352fa4d849eeabe2103762b4a1a4081.exe 81 PID 876 wrote to memory of 736 876 4b5bda9fd666af06c6e99744ecd24f92b352fa4d849eeabe2103762b4a1a4081.exe 81 PID 876 wrote to memory of 736 876 4b5bda9fd666af06c6e99744ecd24f92b352fa4d849eeabe2103762b4a1a4081.exe 81 PID 876 wrote to memory of 736 876 4b5bda9fd666af06c6e99744ecd24f92b352fa4d849eeabe2103762b4a1a4081.exe 81 PID 876 wrote to memory of 736 876 4b5bda9fd666af06c6e99744ecd24f92b352fa4d849eeabe2103762b4a1a4081.exe 81
Processes
-
C:\Users\Admin\AppData\Local\Temp\4b5bda9fd666af06c6e99744ecd24f92b352fa4d849eeabe2103762b4a1a4081.exe"C:\Users\Admin\AppData\Local\Temp\4b5bda9fd666af06c6e99744ecd24f92b352fa4d849eeabe2103762b4a1a4081.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:876 -
C:\Users\Admin\AppData\Local\Temp\4b5bda9fd666af06c6e99744ecd24f92b352fa4d849eeabe2103762b4a1a4081.exeC:\Users\Admin\AppData\Local\Temp\4b5bda9fd666af06c6e99744ecd24f92b352fa4d849eeabe2103762b4a1a4081.exe2⤵PID:736
-