Analysis
-
max time kernel
147s -
max time network
155s -
platform
windows10-2004_x64 -
resource
win10v2004-20240221-en -
resource tags
arch:x64arch:x86image:win10v2004-20240221-enlocale:en-usos:windows10-2004-x64system -
submitted
25/02/2024, 05:19
Behavioral task
behavioral1
Sample
a2fd48d51533768c6b61462e5f74ff47.exe
Resource
win7-20240215-en
5 signatures
150 seconds
Behavioral task
behavioral2
Sample
a2fd48d51533768c6b61462e5f74ff47.exe
Resource
win10v2004-20240221-en
5 signatures
150 seconds
General
-
Target
a2fd48d51533768c6b61462e5f74ff47.exe
-
Size
368KB
-
MD5
a2fd48d51533768c6b61462e5f74ff47
-
SHA1
8cbffeca16a629045154188b8ef331ecc037a91f
-
SHA256
0ee40740d11768f330cfd96c6b5de855955cea419a3176411228c36291c4d1d4
-
SHA512
eb6b40d6db3d112cdab1224550e199a82fd1cb2b7c59c93e6e9de084eff9811f7f27328c157fd6608c24dd8efdf19f53c86d21520b1bba1ab800aa17dface29a
-
SSDEEP
6144:fGL/rU1rBD9bJATiEDRFA0Cnm5oOuAwZiT4H9xE/Snga7LUQpR5KgMgsK4:fGL/rerARe0Cnm5omwZ5E/SngKpRggry
Score
7/10
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/1904-0-0x0000000000400000-0x000000000051C000-memory.dmp upx behavioral2/memory/1904-8-0x0000000000400000-0x000000000051C000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1904 set thread context of 1624 1904 a2fd48d51533768c6b61462e5f74ff47.exe 86 -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 1624 a2fd48d51533768c6b61462e5f74ff47.exe 1624 a2fd48d51533768c6b61462e5f74ff47.exe 1624 a2fd48d51533768c6b61462e5f74ff47.exe 1624 a2fd48d51533768c6b61462e5f74ff47.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 1904 a2fd48d51533768c6b61462e5f74ff47.exe -
Suspicious use of WriteProcessMemory 11 IoCs
description pid Process procid_target PID 1904 wrote to memory of 1624 1904 a2fd48d51533768c6b61462e5f74ff47.exe 86 PID 1904 wrote to memory of 1624 1904 a2fd48d51533768c6b61462e5f74ff47.exe 86 PID 1904 wrote to memory of 1624 1904 a2fd48d51533768c6b61462e5f74ff47.exe 86 PID 1904 wrote to memory of 1624 1904 a2fd48d51533768c6b61462e5f74ff47.exe 86 PID 1904 wrote to memory of 1624 1904 a2fd48d51533768c6b61462e5f74ff47.exe 86 PID 1904 wrote to memory of 1624 1904 a2fd48d51533768c6b61462e5f74ff47.exe 86 PID 1904 wrote to memory of 1624 1904 a2fd48d51533768c6b61462e5f74ff47.exe 86 PID 1624 wrote to memory of 3312 1624 a2fd48d51533768c6b61462e5f74ff47.exe 28 PID 1624 wrote to memory of 3312 1624 a2fd48d51533768c6b61462e5f74ff47.exe 28 PID 1624 wrote to memory of 3312 1624 a2fd48d51533768c6b61462e5f74ff47.exe 28 PID 1624 wrote to memory of 3312 1624 a2fd48d51533768c6b61462e5f74ff47.exe 28
Processes
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:3312
-
C:\Users\Admin\AppData\Local\Temp\a2fd48d51533768c6b61462e5f74ff47.exe"C:\Users\Admin\AppData\Local\Temp\a2fd48d51533768c6b61462e5f74ff47.exe"2⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1904 -
C:\Users\Admin\AppData\Local\Temp\a2fd48d51533768c6b61462e5f74ff47.exe"C:\Users\Admin\AppData\Local\Temp\a2fd48d51533768c6b61462e5f74ff47.exe"3⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:1624
-
-