Analysis
-
max time kernel
90s -
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
06/12/2022, 22:32
Static task
static1
Behavioral task
behavioral1
Sample
b2e3f40d83ea4b28eafc8023b5468e6aab8e65834481f8dda4985fd21609c417.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
b2e3f40d83ea4b28eafc8023b5468e6aab8e65834481f8dda4985fd21609c417.exe
Resource
win10v2004-20220901-en
General
-
Target
b2e3f40d83ea4b28eafc8023b5468e6aab8e65834481f8dda4985fd21609c417.exe
-
Size
1.4MB
-
MD5
a06e7dd098d6e3289eb36c9a0f00f863
-
SHA1
3b4a44b3a081fe74d6dec487e29858d10ce43b69
-
SHA256
b2e3f40d83ea4b28eafc8023b5468e6aab8e65834481f8dda4985fd21609c417
-
SHA512
3ee90d2df07993b534b57b3f9c3a32ebdea4a6793814444aa84f24c97d4747278d0c0b8c49a30526dcf5b4a6be7bf4573dea231a35bedf8c05acfbd7c57708cc
-
SSDEEP
24576:kvQLnSCjeG6G9rRtcmJjlPlWKiXed6IHOvYl/h+X85c8+uAhg7TwVoFlk6hYw/HG:kveyGl9rRfJ9lxp6Iu05fb7Twmnk6n+
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1772 set thread context of 4752 1772 b2e3f40d83ea4b28eafc8023b5468e6aab8e65834481f8dda4985fd21609c417.exe 83 -
Suspicious use of SetWindowsHookEx 2 IoCs
pid Process 1772 b2e3f40d83ea4b28eafc8023b5468e6aab8e65834481f8dda4985fd21609c417.exe 4752 b2e3f40d83ea4b28eafc8023b5468e6aab8e65834481f8dda4985fd21609c417.exe -
Suspicious use of WriteProcessMemory 8 IoCs
description pid Process procid_target PID 1772 wrote to memory of 4752 1772 b2e3f40d83ea4b28eafc8023b5468e6aab8e65834481f8dda4985fd21609c417.exe 83 PID 1772 wrote to memory of 4752 1772 b2e3f40d83ea4b28eafc8023b5468e6aab8e65834481f8dda4985fd21609c417.exe 83 PID 1772 wrote to memory of 4752 1772 b2e3f40d83ea4b28eafc8023b5468e6aab8e65834481f8dda4985fd21609c417.exe 83 PID 1772 wrote to memory of 4752 1772 b2e3f40d83ea4b28eafc8023b5468e6aab8e65834481f8dda4985fd21609c417.exe 83 PID 1772 wrote to memory of 4752 1772 b2e3f40d83ea4b28eafc8023b5468e6aab8e65834481f8dda4985fd21609c417.exe 83 PID 1772 wrote to memory of 4752 1772 b2e3f40d83ea4b28eafc8023b5468e6aab8e65834481f8dda4985fd21609c417.exe 83 PID 1772 wrote to memory of 4752 1772 b2e3f40d83ea4b28eafc8023b5468e6aab8e65834481f8dda4985fd21609c417.exe 83 PID 1772 wrote to memory of 4752 1772 b2e3f40d83ea4b28eafc8023b5468e6aab8e65834481f8dda4985fd21609c417.exe 83
Processes
-
C:\Users\Admin\AppData\Local\Temp\b2e3f40d83ea4b28eafc8023b5468e6aab8e65834481f8dda4985fd21609c417.exe"C:\Users\Admin\AppData\Local\Temp\b2e3f40d83ea4b28eafc8023b5468e6aab8e65834481f8dda4985fd21609c417.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1772 -
C:\Users\Admin\AppData\Local\Temp\b2e3f40d83ea4b28eafc8023b5468e6aab8e65834481f8dda4985fd21609c417.exe"C:\Users\Admin\AppData\Local\Temp\b2e3f40d83ea4b28eafc8023b5468e6aab8e65834481f8dda4985fd21609c417.exe"2⤵
- Suspicious use of SetWindowsHookEx
PID:4752
-