Analysis
-
max time kernel
264s -
max time network
337s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
04/12/2022, 11:05
Static task
static1
Behavioral task
behavioral1
Sample
f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe
Resource
win10v2004-20221111-en
General
-
Target
f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe
-
Size
344KB
-
MD5
6eeac630128719936ef932f2ff60fae9
-
SHA1
d05d073426064bd0a67fe43fa466a2f683e3a439
-
SHA256
f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757
-
SHA512
1d2040c444433eb3ccb80bb987bb63024a6ea228e19f03349d5e23486937f75142925453f9b4afe9b996787d69d023903d90c8b1d4b13139ea32520a3568342c
-
SSDEEP
6144:OHCXa3TJ7xryFl90ei+T1Jhw54PNPPkKgzvQ86YyGwQz8ygT0MlihXkLrK:OR3F82sCANj8MGwI8ygTr6kLW
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/4532-137-0x0000000000400000-0x0000000000472000-memory.dmp upx behavioral2/memory/4532-139-0x0000000000400000-0x0000000000472000-memory.dmp upx behavioral2/memory/4532-140-0x0000000000400000-0x0000000000472000-memory.dmp upx behavioral2/memory/4532-148-0x0000000000400000-0x0000000000472000-memory.dmp upx -
Suspicious use of SetThreadContext 3 IoCs
description pid Process procid_target PID 3096 set thread context of 4532 3096 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe 81 PID 3096 set thread context of 0 3096 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe PID 4532 set thread context of 2132 4532 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe 82 -
Suspicious use of SetWindowsHookEx 2 IoCs
pid Process 3096 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe 4532 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe -
Suspicious use of WriteProcessMemory 20 IoCs
description pid Process procid_target PID 3096 wrote to memory of 4532 3096 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe 81 PID 3096 wrote to memory of 4532 3096 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe 81 PID 3096 wrote to memory of 4532 3096 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe 81 PID 3096 wrote to memory of 4532 3096 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe 81 PID 3096 wrote to memory of 4532 3096 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe 81 PID 3096 wrote to memory of 4532 3096 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe 81 PID 3096 wrote to memory of 4532 3096 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe 81 PID 3096 wrote to memory of 4532 3096 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe 81 PID 3096 wrote to memory of 0 3096 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe PID 3096 wrote to memory of 0 3096 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe PID 3096 wrote to memory of 0 3096 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe PID 3096 wrote to memory of 0 3096 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe PID 3096 wrote to memory of 0 3096 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe PID 4532 wrote to memory of 2132 4532 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe 82 PID 4532 wrote to memory of 2132 4532 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe 82 PID 4532 wrote to memory of 2132 4532 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe 82 PID 4532 wrote to memory of 2132 4532 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe 82 PID 4532 wrote to memory of 2132 4532 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe 82 PID 4532 wrote to memory of 2132 4532 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe 82 PID 4532 wrote to memory of 2132 4532 f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe 82
Processes
-
C:\Users\Admin\AppData\Local\Temp\f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe"C:\Users\Admin\AppData\Local\Temp\f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3096 -
C:\Users\Admin\AppData\Local\Temp\f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe"C:\Users\Admin\AppData\Local\Temp\f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe"2⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4532 -
C:\Users\Admin\AppData\Local\Temp\f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe"C:\Users\Admin\AppData\Local\Temp\f76da3758230ca6de884ffe4df871cc0e26e781955f96ed2ef39125924042757.exe"3⤵PID:2132
-
-