Analysis
-
max time kernel
141s -
max time network
122s -
platform
windows7_x64 -
resource
win7-20231215-en -
resource tags
arch:x64arch:x86image:win7-20231215-enlocale:en-usos:windows7-x64system -
submitted
25/12/2023, 11:14
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
1a058f36ca7b0be1695b30cf9c55856f.exe
Resource
win7-20231215-en
5 signatures
150 seconds
Behavioral task
behavioral2
Sample
1a058f36ca7b0be1695b30cf9c55856f.exe
Resource
win10v2004-20231215-en
5 signatures
150 seconds
General
-
Target
1a058f36ca7b0be1695b30cf9c55856f.exe
-
Size
184KB
-
MD5
1a058f36ca7b0be1695b30cf9c55856f
-
SHA1
a1eed4a2ef3fbca580dd4f581ef83aafcd9b56b2
-
SHA256
e86d73f832f4dc0fd41875145fe6c1fe15f6e54487eae05c51af0c54401e25ca
-
SHA512
0fc1b06b4e094060705dae6fc7beb2588c7db1d16eb8a75e6277e28d30ac3c273b2294e27935da4a1ecbe324945ad7d933e384a46c4e24303249b319900bb32b
-
SSDEEP
1536:Qm7SPnyuu4epVSvkQakIEUcewWuxJwosuFAs7XtcDB8LO4lBY8EyJBzzq0:kTcXSCkYNTgODB8LtlBYoB3z
Score
7/10
Malware Config
Signatures
-
resource yara_rule behavioral1/memory/2212-2-0x0000000000400000-0x000000000040D000-memory.dmp upx behavioral1/memory/2212-5-0x0000000000400000-0x000000000040D000-memory.dmp upx behavioral1/memory/2212-4-0x0000000000400000-0x000000000040D000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3012 set thread context of 2212 3012 1a058f36ca7b0be1695b30cf9c55856f.exe 28 -
Program crash 1 IoCs
pid pid_target Process procid_target 3044 2212 WerFault.exe 28 -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 3012 1a058f36ca7b0be1695b30cf9c55856f.exe -
Suspicious use of WriteProcessMemory 13 IoCs
description pid Process procid_target PID 3012 wrote to memory of 2212 3012 1a058f36ca7b0be1695b30cf9c55856f.exe 28 PID 3012 wrote to memory of 2212 3012 1a058f36ca7b0be1695b30cf9c55856f.exe 28 PID 3012 wrote to memory of 2212 3012 1a058f36ca7b0be1695b30cf9c55856f.exe 28 PID 3012 wrote to memory of 2212 3012 1a058f36ca7b0be1695b30cf9c55856f.exe 28 PID 3012 wrote to memory of 2212 3012 1a058f36ca7b0be1695b30cf9c55856f.exe 28 PID 3012 wrote to memory of 2212 3012 1a058f36ca7b0be1695b30cf9c55856f.exe 28 PID 3012 wrote to memory of 2212 3012 1a058f36ca7b0be1695b30cf9c55856f.exe 28 PID 3012 wrote to memory of 2212 3012 1a058f36ca7b0be1695b30cf9c55856f.exe 28 PID 3012 wrote to memory of 2212 3012 1a058f36ca7b0be1695b30cf9c55856f.exe 28 PID 2212 wrote to memory of 3044 2212 1a058f36ca7b0be1695b30cf9c55856f.exe 29 PID 2212 wrote to memory of 3044 2212 1a058f36ca7b0be1695b30cf9c55856f.exe 29 PID 2212 wrote to memory of 3044 2212 1a058f36ca7b0be1695b30cf9c55856f.exe 29 PID 2212 wrote to memory of 3044 2212 1a058f36ca7b0be1695b30cf9c55856f.exe 29
Processes
-
C:\Users\Admin\AppData\Local\Temp\1a058f36ca7b0be1695b30cf9c55856f.exe"C:\Users\Admin\AppData\Local\Temp\1a058f36ca7b0be1695b30cf9c55856f.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3012 -
C:\Users\Admin\AppData\Local\Temp\1a058f36ca7b0be1695b30cf9c55856f.exe"C:\Users\Admin\AppData\Local\Temp\1a058f36ca7b0be1695b30cf9c55856f.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:2212 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2212 -s 883⤵
- Program crash
PID:3044
-
-