Analysis
-
max time kernel
140s -
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
22-05-2024 02:15
Static task
static1
Behavioral task
behavioral1
Sample
3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe
Resource
win7-20240508-en
Behavioral task
behavioral2
Sample
3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe
Resource
win10v2004-20240508-en
General
-
Target
3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe
-
Size
1.1MB
-
MD5
9f956c2e570b17d57ebbc61f2a9328af
-
SHA1
f6da8c53609c47e18347ba77b96f747af0b6934e
-
SHA256
3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7
-
SHA512
6095461ededb99d13e5e89800a535bdea00a2b6aca78841a195fc3cc076e85a3e0c432d5164e5d30c4b4cab4ea64d45fe199ab334c8e0ca9bc33901e7408ec24
-
SSDEEP
24576:kfZanlLXYSKEDRWTg+YeP/YkOqLKDbu6MGY0r:kPSKRM+Y2ZPLodV
Malware Config
Signatures
-
Processes:
resource yara_rule behavioral2/memory/4860-0-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx behavioral2/memory/4860-24-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx behavioral2/memory/4860-41-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx behavioral2/memory/4860-45-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx behavioral2/memory/4860-44-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx behavioral2/memory/4860-39-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx behavioral2/memory/4860-37-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx behavioral2/memory/4860-35-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx behavioral2/memory/4860-31-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx behavioral2/memory/4860-30-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx behavioral2/memory/4860-28-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx behavioral2/memory/4860-26-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx behavioral2/memory/4860-22-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx behavioral2/memory/4860-20-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx behavioral2/memory/4860-18-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx behavioral2/memory/4860-16-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx behavioral2/memory/4860-14-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx behavioral2/memory/4860-12-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx behavioral2/memory/4860-10-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx behavioral2/memory/4860-8-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx behavioral2/memory/4860-6-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx behavioral2/memory/4860-4-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx behavioral2/memory/4860-2-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx behavioral2/memory/4860-1-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx behavioral2/memory/4860-47-0x0000000000C10000-0x0000000000C4E000-memory.dmp upx -
Suspicious behavior: EnumeratesProcesses 30 IoCs
Processes:
3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exepid process 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe -
Suspicious use of SetWindowsHookEx 3 IoCs
Processes:
3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exepid process 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe 4860 3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe"C:\Users\Admin\AppData\Local\Temp\3e19537dd50b605b7c98fe36fd7cdadfa21e8debcb99a93de0c7d0eef8ac71b7.exe"1⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
PID:4860