Analysis
-
max time kernel
148s -
max time network
173s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
25/11/2022, 11:17
Static task
static1
Behavioral task
behavioral1
Sample
80dafc0bf8abf4819dcf05ff60e3d9e3f040d47062b4664fb692be5354267fc3.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
80dafc0bf8abf4819dcf05ff60e3d9e3f040d47062b4664fb692be5354267fc3.exe
Resource
win10v2004-20221111-en
General
-
Target
80dafc0bf8abf4819dcf05ff60e3d9e3f040d47062b4664fb692be5354267fc3.exe
-
Size
925KB
-
MD5
86915c50a8f9f0833c8725d8585e6326
-
SHA1
9f5c23d94bc6d4459a2958066f17597fb37e1904
-
SHA256
80dafc0bf8abf4819dcf05ff60e3d9e3f040d47062b4664fb692be5354267fc3
-
SHA512
331696df351765b81028b97c86849e39971be495017531240cff3871090516bac07a3edd9e177a603dccec52875dc4c48ed9fbef75559dba18e987c2d2f1e25a
-
SSDEEP
12288:Qmf8PzkvaBHmLV8P22zx+kdJ00Bvuyymhcx1UG6HyNrSjqOuPn6mc2RREYJaR:LSkv/VCWkdJ0OpGmyNtjPn68REYs
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/3484-133-0x0000000000400000-0x00000000004E9000-memory.dmp upx behavioral2/memory/3484-135-0x0000000000400000-0x00000000004E9000-memory.dmp upx behavioral2/memory/3484-136-0x0000000000400000-0x00000000004E9000-memory.dmp upx behavioral2/memory/3484-137-0x0000000000400000-0x00000000004E9000-memory.dmp upx behavioral2/memory/3484-138-0x0000000000400000-0x00000000004E9000-memory.dmp upx behavioral2/memory/3484-139-0x0000000000400000-0x00000000004E9000-memory.dmp upx behavioral2/memory/3484-140-0x0000000000400000-0x00000000004E9000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3768 set thread context of 3484 3768 80dafc0bf8abf4819dcf05ff60e3d9e3f040d47062b4664fb692be5354267fc3.exe 84 -
Suspicious use of SetWindowsHookEx 5 IoCs
pid Process 3484 80dafc0bf8abf4819dcf05ff60e3d9e3f040d47062b4664fb692be5354267fc3.exe 3484 80dafc0bf8abf4819dcf05ff60e3d9e3f040d47062b4664fb692be5354267fc3.exe 3484 80dafc0bf8abf4819dcf05ff60e3d9e3f040d47062b4664fb692be5354267fc3.exe 3484 80dafc0bf8abf4819dcf05ff60e3d9e3f040d47062b4664fb692be5354267fc3.exe 3484 80dafc0bf8abf4819dcf05ff60e3d9e3f040d47062b4664fb692be5354267fc3.exe -
Suspicious use of WriteProcessMemory 8 IoCs
description pid Process procid_target PID 3768 wrote to memory of 3484 3768 80dafc0bf8abf4819dcf05ff60e3d9e3f040d47062b4664fb692be5354267fc3.exe 84 PID 3768 wrote to memory of 3484 3768 80dafc0bf8abf4819dcf05ff60e3d9e3f040d47062b4664fb692be5354267fc3.exe 84 PID 3768 wrote to memory of 3484 3768 80dafc0bf8abf4819dcf05ff60e3d9e3f040d47062b4664fb692be5354267fc3.exe 84 PID 3768 wrote to memory of 3484 3768 80dafc0bf8abf4819dcf05ff60e3d9e3f040d47062b4664fb692be5354267fc3.exe 84 PID 3768 wrote to memory of 3484 3768 80dafc0bf8abf4819dcf05ff60e3d9e3f040d47062b4664fb692be5354267fc3.exe 84 PID 3768 wrote to memory of 3484 3768 80dafc0bf8abf4819dcf05ff60e3d9e3f040d47062b4664fb692be5354267fc3.exe 84 PID 3768 wrote to memory of 3484 3768 80dafc0bf8abf4819dcf05ff60e3d9e3f040d47062b4664fb692be5354267fc3.exe 84 PID 3768 wrote to memory of 3484 3768 80dafc0bf8abf4819dcf05ff60e3d9e3f040d47062b4664fb692be5354267fc3.exe 84
Processes
-
C:\Users\Admin\AppData\Local\Temp\80dafc0bf8abf4819dcf05ff60e3d9e3f040d47062b4664fb692be5354267fc3.exe"C:\Users\Admin\AppData\Local\Temp\80dafc0bf8abf4819dcf05ff60e3d9e3f040d47062b4664fb692be5354267fc3.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3768 -
C:\Users\Admin\AppData\Local\Temp\80dafc0bf8abf4819dcf05ff60e3d9e3f040d47062b4664fb692be5354267fc3.exe"C:\Users\Admin\AppData\Local\Temp\80dafc0bf8abf4819dcf05ff60e3d9e3f040d47062b4664fb692be5354267fc3.exe"2⤵
- Suspicious use of SetWindowsHookEx
PID:3484
-