Analysis
-
max time kernel
91s -
max time network
155s -
platform
windows10-2004_x64 -
resource
win10v2004-20220901-en -
resource tags
arch:x64arch:x86image:win10v2004-20220901-enlocale:en-usos:windows10-2004-x64system -
submitted
25/11/2022, 11:01
Static task
static1
Behavioral task
behavioral1
Sample
86f1cb445b98e33b9c028f6b86e4a9a698c96ee8fe20751f4a6bef9174d9e14b.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
86f1cb445b98e33b9c028f6b86e4a9a698c96ee8fe20751f4a6bef9174d9e14b.exe
Resource
win10v2004-20220901-en
General
-
Target
86f1cb445b98e33b9c028f6b86e4a9a698c96ee8fe20751f4a6bef9174d9e14b.exe
-
Size
925KB
-
MD5
ac92460214e59abdcf9bfbcefac264bf
-
SHA1
fb103582f7aa8f82a09442134092a3d1922508d7
-
SHA256
86f1cb445b98e33b9c028f6b86e4a9a698c96ee8fe20751f4a6bef9174d9e14b
-
SHA512
93c9bcc7fcdf1cd66c9ec609fcc818ee304b52769985b55f6c29876f3eb6596f45b9cd74a4f182bd901ec0072b28f889b35fc10047181f5e821816fc83530736
-
SSDEEP
12288:wmf8PzkvaBHmLV8P22zx+kdJ00Bvuyymhcx1UG6HyNrSjqOuPn6mc2RREYJaRU:rSkv/VCWkdJ0OpGmyNtjPn68REYsW
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/4868-133-0x0000000000400000-0x00000000004E9000-memory.dmp upx behavioral2/memory/4868-135-0x0000000000400000-0x00000000004E9000-memory.dmp upx behavioral2/memory/4868-136-0x0000000000400000-0x00000000004E9000-memory.dmp upx behavioral2/memory/4868-137-0x0000000000400000-0x00000000004E9000-memory.dmp upx behavioral2/memory/4868-138-0x0000000000400000-0x00000000004E9000-memory.dmp upx behavioral2/memory/4868-139-0x0000000000400000-0x00000000004E9000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1316 set thread context of 4868 1316 86f1cb445b98e33b9c028f6b86e4a9a698c96ee8fe20751f4a6bef9174d9e14b.exe 82 -
Suspicious use of SetWindowsHookEx 5 IoCs
pid Process 4868 86f1cb445b98e33b9c028f6b86e4a9a698c96ee8fe20751f4a6bef9174d9e14b.exe 4868 86f1cb445b98e33b9c028f6b86e4a9a698c96ee8fe20751f4a6bef9174d9e14b.exe 4868 86f1cb445b98e33b9c028f6b86e4a9a698c96ee8fe20751f4a6bef9174d9e14b.exe 4868 86f1cb445b98e33b9c028f6b86e4a9a698c96ee8fe20751f4a6bef9174d9e14b.exe 4868 86f1cb445b98e33b9c028f6b86e4a9a698c96ee8fe20751f4a6bef9174d9e14b.exe -
Suspicious use of WriteProcessMemory 8 IoCs
description pid Process procid_target PID 1316 wrote to memory of 4868 1316 86f1cb445b98e33b9c028f6b86e4a9a698c96ee8fe20751f4a6bef9174d9e14b.exe 82 PID 1316 wrote to memory of 4868 1316 86f1cb445b98e33b9c028f6b86e4a9a698c96ee8fe20751f4a6bef9174d9e14b.exe 82 PID 1316 wrote to memory of 4868 1316 86f1cb445b98e33b9c028f6b86e4a9a698c96ee8fe20751f4a6bef9174d9e14b.exe 82 PID 1316 wrote to memory of 4868 1316 86f1cb445b98e33b9c028f6b86e4a9a698c96ee8fe20751f4a6bef9174d9e14b.exe 82 PID 1316 wrote to memory of 4868 1316 86f1cb445b98e33b9c028f6b86e4a9a698c96ee8fe20751f4a6bef9174d9e14b.exe 82 PID 1316 wrote to memory of 4868 1316 86f1cb445b98e33b9c028f6b86e4a9a698c96ee8fe20751f4a6bef9174d9e14b.exe 82 PID 1316 wrote to memory of 4868 1316 86f1cb445b98e33b9c028f6b86e4a9a698c96ee8fe20751f4a6bef9174d9e14b.exe 82 PID 1316 wrote to memory of 4868 1316 86f1cb445b98e33b9c028f6b86e4a9a698c96ee8fe20751f4a6bef9174d9e14b.exe 82
Processes
-
C:\Users\Admin\AppData\Local\Temp\86f1cb445b98e33b9c028f6b86e4a9a698c96ee8fe20751f4a6bef9174d9e14b.exe"C:\Users\Admin\AppData\Local\Temp\86f1cb445b98e33b9c028f6b86e4a9a698c96ee8fe20751f4a6bef9174d9e14b.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1316 -
C:\Users\Admin\AppData\Local\Temp\86f1cb445b98e33b9c028f6b86e4a9a698c96ee8fe20751f4a6bef9174d9e14b.exe"C:\Users\Admin\AppData\Local\Temp\86f1cb445b98e33b9c028f6b86e4a9a698c96ee8fe20751f4a6bef9174d9e14b.exe"2⤵
- Suspicious use of SetWindowsHookEx
PID:4868
-