Analysis
-
max time kernel
211s -
max time network
337s -
platform
windows7_x64 -
resource
win7-20221111-en -
resource tags
arch:x64arch:x86image:win7-20221111-enlocale:en-usos:windows7-x64system -
submitted
01/12/2022, 14:31
Behavioral task
behavioral1
Sample
bfab2d66eadc441de8727159470aa7e9c7e687499f99e30900ce649be4bf37e4.exe
Resource
win7-20221111-en
3 signatures
150 seconds
General
-
Target
bfab2d66eadc441de8727159470aa7e9c7e687499f99e30900ce649be4bf37e4.exe
-
Size
136KB
-
MD5
6366483023d16f01169f69a1a80686c0
-
SHA1
9be45dae1ffce03c7d7e172ab46dfacd605a2a44
-
SHA256
bfab2d66eadc441de8727159470aa7e9c7e687499f99e30900ce649be4bf37e4
-
SHA512
6352be4df44129b970666c6292f1c28e2eb03f18853b23cfb73cb9e6f9ba8daa554e6be7eeb466d35615d68791fe4a1e554c6112f608615e08160d2deb9ddc01
-
SSDEEP
3072:roNoqyco/9ohG/u9/GfIN912z3hlF0CLd6DFUh1q7Bp:kNoqNoShGSsIx2z3hlFlMDFUh1eP
Score
8/10
Malware Config
Signatures
-
resource yara_rule behavioral1/memory/1640-55-0x0000000000400000-0x000000000043D000-memory.dmp upx -
Program crash 1 IoCs
pid pid_target Process procid_target 576 1640 WerFault.exe 20 -
Suspicious use of WriteProcessMemory 4 IoCs
description pid Process procid_target PID 1640 wrote to memory of 576 1640 bfab2d66eadc441de8727159470aa7e9c7e687499f99e30900ce649be4bf37e4.exe 28 PID 1640 wrote to memory of 576 1640 bfab2d66eadc441de8727159470aa7e9c7e687499f99e30900ce649be4bf37e4.exe 28 PID 1640 wrote to memory of 576 1640 bfab2d66eadc441de8727159470aa7e9c7e687499f99e30900ce649be4bf37e4.exe 28 PID 1640 wrote to memory of 576 1640 bfab2d66eadc441de8727159470aa7e9c7e687499f99e30900ce649be4bf37e4.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\bfab2d66eadc441de8727159470aa7e9c7e687499f99e30900ce649be4bf37e4.exe"C:\Users\Admin\AppData\Local\Temp\bfab2d66eadc441de8727159470aa7e9c7e687499f99e30900ce649be4bf37e4.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:1640 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1640 -s 1482⤵
- Program crash
PID:576
-