Analysis
-
max time kernel
118s -
max time network
123s -
platform
windows7_x64 -
resource
win7-20240221-en -
resource tags
arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system -
submitted
22-02-2024 01:01
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
0a27ad541882215cd383bc1702b6c2e5.exe
Resource
win7-20240221-en
3 signatures
150 seconds
General
-
Target
0a27ad541882215cd383bc1702b6c2e5.exe
-
Size
305KB
-
MD5
0a27ad541882215cd383bc1702b6c2e5
-
SHA1
b4b489f3f0496590a86f74f8f371e7e308649e3e
-
SHA256
d19c3ec87d938380c5d1fff9c45357813a42b73499b1342f3b6d5297cf6c53fd
-
SHA512
cf6affd9270a22ba971bfa6cc8f0dd7a8461a6dedbb1174e38d0bd1ab358fa038491e8b239f30065e5a20c1511c3f2e5f67c1968114f00169bbcf544e5f84d64
-
SSDEEP
6144:iBAZ4kXDWC5JrHnaH7999ue/zCuMU6Jw0uDFG2O2scn3L8KM:i+vTXJrHngEe/evKG2BL
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
0a27ad541882215cd383bc1702b6c2e5.exedescription pid Process procid_target PID 1736 set thread context of 2840 1736 0a27ad541882215cd383bc1702b6c2e5.exe 29 -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target Process procid_target 2596 2840 WerFault.exe 29 -
Suspicious use of WriteProcessMemory 17 IoCs
Processes:
0a27ad541882215cd383bc1702b6c2e5.exeRegAsm.exedescription pid Process procid_target PID 1736 wrote to memory of 2840 1736 0a27ad541882215cd383bc1702b6c2e5.exe 29 PID 1736 wrote to memory of 2840 1736 0a27ad541882215cd383bc1702b6c2e5.exe 29 PID 1736 wrote to memory of 2840 1736 0a27ad541882215cd383bc1702b6c2e5.exe 29 PID 1736 wrote to memory of 2840 1736 0a27ad541882215cd383bc1702b6c2e5.exe 29 PID 1736 wrote to memory of 2840 1736 0a27ad541882215cd383bc1702b6c2e5.exe 29 PID 1736 wrote to memory of 2840 1736 0a27ad541882215cd383bc1702b6c2e5.exe 29 PID 1736 wrote to memory of 2840 1736 0a27ad541882215cd383bc1702b6c2e5.exe 29 PID 1736 wrote to memory of 2840 1736 0a27ad541882215cd383bc1702b6c2e5.exe 29 PID 1736 wrote to memory of 2840 1736 0a27ad541882215cd383bc1702b6c2e5.exe 29 PID 1736 wrote to memory of 2840 1736 0a27ad541882215cd383bc1702b6c2e5.exe 29 PID 1736 wrote to memory of 2840 1736 0a27ad541882215cd383bc1702b6c2e5.exe 29 PID 1736 wrote to memory of 2840 1736 0a27ad541882215cd383bc1702b6c2e5.exe 29 PID 1736 wrote to memory of 2840 1736 0a27ad541882215cd383bc1702b6c2e5.exe 29 PID 2840 wrote to memory of 2596 2840 RegAsm.exe 30 PID 2840 wrote to memory of 2596 2840 RegAsm.exe 30 PID 2840 wrote to memory of 2596 2840 RegAsm.exe 30 PID 2840 wrote to memory of 2596 2840 RegAsm.exe 30
Processes
-
C:\Users\Admin\AppData\Local\Temp\0a27ad541882215cd383bc1702b6c2e5.exe"C:\Users\Admin\AppData\Local\Temp\0a27ad541882215cd383bc1702b6c2e5.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1736 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:2840 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2840 -s 2603⤵
- Program crash
PID:2596
-
-