Analysis
-
max time kernel
90s -
max time network
139s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
15/10/2022, 19:48
Static task
static1
Behavioral task
behavioral1
Sample
c8243e70f039d74a6fffced3793c60ed039c69e1ff0f230ed43b5cde0664ba09.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
c8243e70f039d74a6fffced3793c60ed039c69e1ff0f230ed43b5cde0664ba09.exe
Resource
win10v2004-20220812-en
General
-
Target
c8243e70f039d74a6fffced3793c60ed039c69e1ff0f230ed43b5cde0664ba09.exe
-
Size
1.5MB
-
MD5
38ebea1162225a78ca81fb1fb2eed06f
-
SHA1
a1634920ffe0ede52cfe1b8a67482afcf213a762
-
SHA256
c8243e70f039d74a6fffced3793c60ed039c69e1ff0f230ed43b5cde0664ba09
-
SHA512
752af47284221967fd3a649d76f5249523be915566602b84b9a2f45e17ecebed90314948126832034d6227b167a02f82e4e98a299cffbe0e69bcb8a40bcd0f20
-
SSDEEP
12288:9LMxhyxv664BtysdhIl4t4plpgUqdR5nWFpPoSRMGgVKMnnp+Mygc:9ajBUsdhk4iplCUqAbUGgZnnpXygc
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/440-132-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/440-133-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/440-134-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/440-136-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/440-138-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/440-140-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/440-142-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/440-144-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/440-146-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/440-148-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/440-150-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/440-152-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/440-154-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/440-156-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/440-158-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/440-160-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/440-162-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/440-164-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/440-166-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/440-168-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/440-170-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/440-172-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/440-174-0x0000000010000000-0x000000001003E000-memory.dmp upx behavioral2/memory/440-175-0x0000000010000000-0x000000001003E000-memory.dmp upx -
Suspicious use of SetWindowsHookEx 3 IoCs
pid Process 440 c8243e70f039d74a6fffced3793c60ed039c69e1ff0f230ed43b5cde0664ba09.exe 440 c8243e70f039d74a6fffced3793c60ed039c69e1ff0f230ed43b5cde0664ba09.exe 440 c8243e70f039d74a6fffced3793c60ed039c69e1ff0f230ed43b5cde0664ba09.exe