Analysis
-
max time kernel
150s -
max time network
156s -
platform
windows10-2004_x64 -
resource
win10v2004-20231215-en -
resource tags
arch:x64arch:x86image:win10v2004-20231215-enlocale:en-usos:windows10-2004-x64system -
submitted
15-12-2023 16:01
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
52H5G7F46.exe
Resource
win7-20231215-en
windows7-x64
2 signatures
150 seconds
General
-
Target
52H5G7F46.exe
-
Size
16.2MB
-
MD5
16a4f6e01cfcd72dbc87f939428be5af
-
SHA1
a0358b84506c1b74b5e681de4d1b009832f61b8a
-
SHA256
7271bfe93c41ef4ffd9b94194de6eaa3849c68055cca2fe4507b11c85a86afae
-
SHA512
23b131cb8e9034d3da35f25025b3a8bb8f72ef6c39aa9fe32f9bef009bdb07170e9cc8116c86ecb645e6b6bcb6d6f8122823a2eb07bb1929d94d7bcf4f0d6f9b
-
SSDEEP
49152:QTmuEoPcYA4tSvagQTP1U2XTKKw/4rH4tVgCrpJU12GM6FoOLjwgpL6hf+CiTACa:QTzV
Malware Config
Signatures
-
Bandook payload 8 IoCs
Processes:
resource yara_rule behavioral2/memory/1800-17-0x0000000013140000-0x0000000014E33000-memory.dmp family_bandook behavioral2/memory/1800-16-0x0000000013140000-0x0000000014E33000-memory.dmp family_bandook behavioral2/memory/1800-19-0x0000000013140000-0x0000000014E33000-memory.dmp family_bandook behavioral2/memory/1800-20-0x0000000013140000-0x0000000014E33000-memory.dmp family_bandook behavioral2/memory/1800-22-0x0000000013140000-0x0000000014E33000-memory.dmp family_bandook behavioral2/memory/1800-23-0x0000000013140000-0x0000000014E33000-memory.dmp family_bandook behavioral2/memory/1800-25-0x0000000013140000-0x0000000014E33000-memory.dmp family_bandook behavioral2/memory/1800-31-0x0000000013140000-0x0000000014E33000-memory.dmp family_bandook -
Processes:
resource yara_rule behavioral2/memory/1800-14-0x0000000013140000-0x0000000014E33000-memory.dmp upx behavioral2/memory/1800-15-0x0000000013140000-0x0000000014E33000-memory.dmp upx behavioral2/memory/1800-17-0x0000000013140000-0x0000000014E33000-memory.dmp upx behavioral2/memory/1800-16-0x0000000013140000-0x0000000014E33000-memory.dmp upx behavioral2/memory/1800-19-0x0000000013140000-0x0000000014E33000-memory.dmp upx behavioral2/memory/1800-20-0x0000000013140000-0x0000000014E33000-memory.dmp upx behavioral2/memory/1800-22-0x0000000013140000-0x0000000014E33000-memory.dmp upx behavioral2/memory/1800-23-0x0000000013140000-0x0000000014E33000-memory.dmp upx behavioral2/memory/1800-25-0x0000000013140000-0x0000000014E33000-memory.dmp upx behavioral2/memory/1800-31-0x0000000013140000-0x0000000014E33000-memory.dmp upx -
Suspicious behavior: EnumeratesProcesses 2 IoCs
Processes:
msinfo32.exepid Process 1800 msinfo32.exe 1800 msinfo32.exe -
Suspicious use of WriteProcessMemory 8 IoCs
Processes:
52H5G7F46.exedescription pid Process procid_target PID 3376 wrote to memory of 1800 3376 52H5G7F46.exe 83 PID 3376 wrote to memory of 1800 3376 52H5G7F46.exe 83 PID 3376 wrote to memory of 1800 3376 52H5G7F46.exe 83 PID 3376 wrote to memory of 1804 3376 52H5G7F46.exe 84 PID 3376 wrote to memory of 1804 3376 52H5G7F46.exe 84 PID 3376 wrote to memory of 1804 3376 52H5G7F46.exe 84 PID 3376 wrote to memory of 1800 3376 52H5G7F46.exe 83 PID 3376 wrote to memory of 1800 3376 52H5G7F46.exe 83
Processes
-
C:\Users\Admin\AppData\Local\Temp\52H5G7F46.exe"C:\Users\Admin\AppData\Local\Temp\52H5G7F46.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:3376 -
C:\windows\SysWOW64\msinfo32.exeC:\windows\syswow64\msinfo32.exe2⤵
- Suspicious behavior: EnumeratesProcesses
PID:1800
-
-
C:\Users\Admin\AppData\Local\Temp\52H5G7F46.exeC:\Users\Admin\AppData\Local\Temp\52H5G7F46.exe nnchwwghwgehwgewyeywyeywyye2⤵PID:1804
-