Analysis
-
max time kernel
118s -
max time network
118s -
platform
windows7_x64 -
resource
win7-20240508-en -
resource tags
arch:x64arch:x86image:win7-20240508-enlocale:en-usos:windows7-x64system -
submitted
24-05-2024 05:41
Static task
static1
Behavioral task
behavioral1
Sample
3b503c82ebccc07142b9f475478ade75cd38ebc12c8ec8f90acc31a0b63a115a.exe
Resource
win7-20240508-en
Behavioral task
behavioral2
Sample
3b503c82ebccc07142b9f475478ade75cd38ebc12c8ec8f90acc31a0b63a115a.exe
Resource
win10v2004-20240508-en
General
-
Target
3b503c82ebccc07142b9f475478ade75cd38ebc12c8ec8f90acc31a0b63a115a.exe
-
Size
2.4MB
-
MD5
e4f06e42a94d90873daba6045c8112d6
-
SHA1
e15cb5240aa7fd7decb126497d8f43cf4c12d793
-
SHA256
3b503c82ebccc07142b9f475478ade75cd38ebc12c8ec8f90acc31a0b63a115a
-
SHA512
36c16122eb06df256648979d3065d7ae425d8fba63c8d3cfbf1d6b54c044e9adbc2b632f9a67b2e29a8fe52929d5428407cadd431d5fbf447717f4ff03c7658c
-
SSDEEP
49152:hyBfv2akhoBTRDlrZ/or1/eDB2eGfFXr+YOd9Z4hYuKt40b:hyR2allqo1CSN4hPK
Malware Config
Signatures
-
resource yara_rule behavioral1/memory/2072-5-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral1/memory/2072-9-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral1/memory/2072-44-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral1/memory/2072-43-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral1/memory/2072-42-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral1/memory/2072-39-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral1/memory/2072-37-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral1/memory/2072-35-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral1/memory/2072-33-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral1/memory/2072-31-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral1/memory/2072-29-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral1/memory/2072-27-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral1/memory/2072-25-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral1/memory/2072-23-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral1/memory/2072-21-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral1/memory/2072-19-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral1/memory/2072-17-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral1/memory/2072-15-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral1/memory/2072-13-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral1/memory/2072-11-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral1/memory/2072-7-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral1/memory/2072-3-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral1/memory/2072-2-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral1/memory/2072-1-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral1/memory/2072-45-0x0000000010000000-0x000000001003E000-memory.dmp upx -
Suspicious use of SetWindowsHookEx 3 IoCs
pid Process 2072 3b503c82ebccc07142b9f475478ade75cd38ebc12c8ec8f90acc31a0b63a115a.exe 2072 3b503c82ebccc07142b9f475478ade75cd38ebc12c8ec8f90acc31a0b63a115a.exe 2072 3b503c82ebccc07142b9f475478ade75cd38ebc12c8ec8f90acc31a0b63a115a.exe