Analysis
-
max time kernel
121s -
max time network
125s -
platform
windows7_x64 -
resource
win7-20240319-en -
resource tags
arch:x64arch:x86image:win7-20240319-enlocale:en-usos:windows7-x64system -
submitted
28/03/2024, 22:18
Static task
static1
Behavioral task
behavioral1
Sample
0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe
Resource
win7-20240319-en
3 signatures
300 seconds
General
-
Target
0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe
-
Size
369KB
-
MD5
709b4a2ddc267d1e206052d75b6024f5
-
SHA1
0830a0c93f531defa187a8947310a8f21b1040cb
-
SHA256
0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3
-
SHA512
83a541217c08eb348482e1d3739f519e8463077a273ab7833806aa7f09949788906e6f111d2ede7d3d4cceef0cfc16b2b6238d099f61d354f8c4b7086b5528b2
-
SSDEEP
6144:dTFBaM1p5sfDMenimB7dzVtDFpnJnAJqTH8Kmarh8O9qjAnvlnGPZp:twDMkimBZDFpndAJCtV98O9qjAdncp
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1192 set thread context of 2000 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 30 -
Program crash 2 IoCs
pid pid_target Process procid_target 2736 1192 WerFault.exe 27 3016 2000 WerFault.exe 30 -
Suspicious use of WriteProcessMemory 28 IoCs
description pid Process procid_target PID 1192 wrote to memory of 2204 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 29 PID 1192 wrote to memory of 2204 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 29 PID 1192 wrote to memory of 2204 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 29 PID 1192 wrote to memory of 2204 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 29 PID 1192 wrote to memory of 2204 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 29 PID 1192 wrote to memory of 2204 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 29 PID 1192 wrote to memory of 2204 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 29 PID 1192 wrote to memory of 2000 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 30 PID 1192 wrote to memory of 2000 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 30 PID 1192 wrote to memory of 2000 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 30 PID 1192 wrote to memory of 2000 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 30 PID 1192 wrote to memory of 2000 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 30 PID 1192 wrote to memory of 2000 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 30 PID 1192 wrote to memory of 2000 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 30 PID 1192 wrote to memory of 2000 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 30 PID 1192 wrote to memory of 2000 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 30 PID 1192 wrote to memory of 2000 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 30 PID 1192 wrote to memory of 2000 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 30 PID 1192 wrote to memory of 2000 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 30 PID 1192 wrote to memory of 2000 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 30 PID 1192 wrote to memory of 2736 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 31 PID 1192 wrote to memory of 2736 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 31 PID 1192 wrote to memory of 2736 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 31 PID 1192 wrote to memory of 2736 1192 0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe 31 PID 2000 wrote to memory of 3016 2000 RegAsm.exe 32 PID 2000 wrote to memory of 3016 2000 RegAsm.exe 32 PID 2000 wrote to memory of 3016 2000 RegAsm.exe 32 PID 2000 wrote to memory of 3016 2000 RegAsm.exe 32
Processes
-
C:\Users\Admin\AppData\Local\Temp\0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe"C:\Users\Admin\AppData\Local\Temp\0dada0f2a9f4c8444deb496043c26428164573683244666e897162619be947b3.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1192 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:2204
-
-
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:2000 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2000 -s 2603⤵
- Program crash
PID:3016
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1192 -s 5202⤵
- Program crash
PID:2736
-