Analysis
-
max time kernel
132s -
max time network
124s -
platform
windows10-2004_x64 -
resource
win10v2004-20240508-en -
resource tags
arch:x64arch:x86image:win10v2004-20240508-enlocale:en-usos:windows10-2004-x64system -
submitted
26-05-2024 07:21
Static task
static1
Behavioral task
behavioral1
Sample
dee1218e1d773939eebcb8ac7d39f00739e3f539c53c2027098b0c01a05c1ebe.exe
Resource
win7-20231129-en
Behavioral task
behavioral2
Sample
dee1218e1d773939eebcb8ac7d39f00739e3f539c53c2027098b0c01a05c1ebe.exe
Resource
win10v2004-20240508-en
General
-
Target
dee1218e1d773939eebcb8ac7d39f00739e3f539c53c2027098b0c01a05c1ebe.exe
-
Size
1.4MB
-
MD5
0a489e6d166157eb4ab2177b8eede2e0
-
SHA1
63c47dab3eb23149300e992bcaabfd33e59c8681
-
SHA256
dee1218e1d773939eebcb8ac7d39f00739e3f539c53c2027098b0c01a05c1ebe
-
SHA512
0b14ac6956e5e3091b69a203606cd378d3e8acad9f2e29a42b24e3fe21b56b26841dcc345df8c5aec5033f23e391494c8e779db320347d4f20207b9c94977ba2
-
SSDEEP
24576:nsJkrpqa8IDVqRmWOm3jQiYlaaI69axIfIbXnb763G3:nIQm/Yl7Y53K
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/2688-45-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-47-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-46-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-43-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-40-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-38-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-36-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-33-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-31-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-29-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-27-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-25-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-23-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-19-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-17-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-16-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-13-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-11-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-9-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-7-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-3-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-21-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-5-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-2-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-1-0x0000000010000000-0x000000001003F000-memory.dmp upx behavioral2/memory/2688-49-0x0000000010000000-0x000000001003F000-memory.dmp upx -
Suspicious use of SetWindowsHookEx 3 IoCs
pid Process 2688 dee1218e1d773939eebcb8ac7d39f00739e3f539c53c2027098b0c01a05c1ebe.exe 2688 dee1218e1d773939eebcb8ac7d39f00739e3f539c53c2027098b0c01a05c1ebe.exe 2688 dee1218e1d773939eebcb8ac7d39f00739e3f539c53c2027098b0c01a05c1ebe.exe