Analysis
-
max time kernel
122s -
max time network
140s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
12-10-2023 17:33
Static task
static1
Behavioral task
behavioral1
Sample
05be32c1ac4d4f8080d6afa867e7a9cbdef17ca4b426a65580ae9b5f99b4741c.exe
Resource
win7-20230831-en
Behavioral task
behavioral2
Sample
05be32c1ac4d4f8080d6afa867e7a9cbdef17ca4b426a65580ae9b5f99b4741c.exe
Resource
win10v2004-20230915-en
General
-
Target
05be32c1ac4d4f8080d6afa867e7a9cbdef17ca4b426a65580ae9b5f99b4741c.exe
-
Size
1.2MB
-
MD5
1887ee1fe7412938d0b50e5048e66022
-
SHA1
221ec027a401906ad86063ee058f029298989798
-
SHA256
05be32c1ac4d4f8080d6afa867e7a9cbdef17ca4b426a65580ae9b5f99b4741c
-
SHA512
b2336235c24fe1d3df8e732bd10520d78043739701a6e40dd5f87ab094b1fd35556f22f1fed9bb6c722829b6395f560a39703229e475598b7f391dc0819fb092
-
SSDEEP
24576:VYtTYUw0/rq2RKjMWtjW5dXdswgy0nEGfyi0qdmGSygOTMrZV2RZ:VYtTYH0/O2vWNCrDgy0nEXi0bDbIZ
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3004 set thread context of 3064 3004 05be32c1ac4d4f8080d6afa867e7a9cbdef17ca4b426a65580ae9b5f99b4741c.exe 28 -
Program crash 1 IoCs
pid pid_target Process procid_target 2956 3064 WerFault.exe 28 -
Suspicious use of WriteProcessMemory 21 IoCs
description pid Process procid_target PID 3004 wrote to memory of 3064 3004 05be32c1ac4d4f8080d6afa867e7a9cbdef17ca4b426a65580ae9b5f99b4741c.exe 28 PID 3004 wrote to memory of 3064 3004 05be32c1ac4d4f8080d6afa867e7a9cbdef17ca4b426a65580ae9b5f99b4741c.exe 28 PID 3004 wrote to memory of 3064 3004 05be32c1ac4d4f8080d6afa867e7a9cbdef17ca4b426a65580ae9b5f99b4741c.exe 28 PID 3004 wrote to memory of 3064 3004 05be32c1ac4d4f8080d6afa867e7a9cbdef17ca4b426a65580ae9b5f99b4741c.exe 28 PID 3004 wrote to memory of 3064 3004 05be32c1ac4d4f8080d6afa867e7a9cbdef17ca4b426a65580ae9b5f99b4741c.exe 28 PID 3004 wrote to memory of 3064 3004 05be32c1ac4d4f8080d6afa867e7a9cbdef17ca4b426a65580ae9b5f99b4741c.exe 28 PID 3004 wrote to memory of 3064 3004 05be32c1ac4d4f8080d6afa867e7a9cbdef17ca4b426a65580ae9b5f99b4741c.exe 28 PID 3004 wrote to memory of 3064 3004 05be32c1ac4d4f8080d6afa867e7a9cbdef17ca4b426a65580ae9b5f99b4741c.exe 28 PID 3004 wrote to memory of 3064 3004 05be32c1ac4d4f8080d6afa867e7a9cbdef17ca4b426a65580ae9b5f99b4741c.exe 28 PID 3004 wrote to memory of 3064 3004 05be32c1ac4d4f8080d6afa867e7a9cbdef17ca4b426a65580ae9b5f99b4741c.exe 28 PID 3004 wrote to memory of 3064 3004 05be32c1ac4d4f8080d6afa867e7a9cbdef17ca4b426a65580ae9b5f99b4741c.exe 28 PID 3004 wrote to memory of 3064 3004 05be32c1ac4d4f8080d6afa867e7a9cbdef17ca4b426a65580ae9b5f99b4741c.exe 28 PID 3004 wrote to memory of 3064 3004 05be32c1ac4d4f8080d6afa867e7a9cbdef17ca4b426a65580ae9b5f99b4741c.exe 28 PID 3004 wrote to memory of 3064 3004 05be32c1ac4d4f8080d6afa867e7a9cbdef17ca4b426a65580ae9b5f99b4741c.exe 28 PID 3064 wrote to memory of 2956 3064 AppLaunch.exe 29 PID 3064 wrote to memory of 2956 3064 AppLaunch.exe 29 PID 3064 wrote to memory of 2956 3064 AppLaunch.exe 29 PID 3064 wrote to memory of 2956 3064 AppLaunch.exe 29 PID 3064 wrote to memory of 2956 3064 AppLaunch.exe 29 PID 3064 wrote to memory of 2956 3064 AppLaunch.exe 29 PID 3064 wrote to memory of 2956 3064 AppLaunch.exe 29
Processes
-
C:\Users\Admin\AppData\Local\Temp\05be32c1ac4d4f8080d6afa867e7a9cbdef17ca4b426a65580ae9b5f99b4741c.exe"C:\Users\Admin\AppData\Local\Temp\05be32c1ac4d4f8080d6afa867e7a9cbdef17ca4b426a65580ae9b5f99b4741c.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3004 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:3064 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3064 -s 2003⤵
- Program crash
PID:2956
-
-