Analysis
-
max time kernel
177s -
max time network
187s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
03/12/2022, 17:36
Static task
static1
Behavioral task
behavioral1
Sample
c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe
Resource
win7-20220901-en
Behavioral task
behavioral2
Sample
c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe
Resource
win10v2004-20220812-en
General
-
Target
c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe
-
Size
1.6MB
-
MD5
906bcf1f90c73ba1882b150f17a710ed
-
SHA1
2ef201cec42007df61ba7071c3bd999df5a71897
-
SHA256
c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0
-
SHA512
c247ed5fea504439c040f5af629819702cc2a92c734f45bfb7ba60e3d4d2f9995c8578226b733d8d8ffa17681f2b3a8a1e4942e559d7969f08edfab688d8d310
-
SSDEEP
12288:EGBxzpv5Ps99wW/scYgrF5Ac3//4JQ+5oHk7uWiBO9tD12XkvVmQarZ5I6f0T8jj:7zpv5kX1WwLAJz5oHk6WiBqbYBDs6KA
Malware Config
Signatures
-
Suspicious use of SetThreadContext 2 IoCs
description pid Process procid_target PID 1672 set thread context of 1448 1672 c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe 81 PID 1672 set thread context of 4896 1672 c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe 82 -
Drops file in Windows directory 3 IoCs
description ioc Process File opened for modification C:\Windows\Bilder\peinlich.exe c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe File opened for modification C:\Windows\p.dat c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe File created C:\Windows\Bilder\peinlich.exe c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe -
Modifies registry class 1 IoCs
description ioc Process Key created \REGISTRY\USER\S-1-5-21-2295526160-1155304984-640977766-1000_Classes\Local Settings explorer.exe -
Suspicious use of SetWindowsHookEx 2 IoCs
pid Process 1672 c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe 4896 c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe -
Suspicious use of WriteProcessMemory 14 IoCs
description pid Process procid_target PID 1672 wrote to memory of 1448 1672 c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe 81 PID 1672 wrote to memory of 1448 1672 c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe 81 PID 1672 wrote to memory of 1448 1672 c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe 81 PID 1672 wrote to memory of 1448 1672 c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe 81 PID 1672 wrote to memory of 1448 1672 c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe 81 PID 1672 wrote to memory of 1448 1672 c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe 81 PID 1672 wrote to memory of 4896 1672 c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe 82 PID 1672 wrote to memory of 4896 1672 c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe 82 PID 1672 wrote to memory of 4896 1672 c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe 82 PID 1672 wrote to memory of 4896 1672 c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe 82 PID 1672 wrote to memory of 4896 1672 c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe 82 PID 1672 wrote to memory of 4896 1672 c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe 82 PID 1672 wrote to memory of 4896 1672 c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe 82 PID 1672 wrote to memory of 4896 1672 c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe 82
Processes
-
C:\Users\Admin\AppData\Local\Temp\c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe"C:\Users\Admin\AppData\Local\Temp\c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe"1⤵
- Suspicious use of SetThreadContext
- Drops file in Windows directory
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1672 -
C:\Windows\explorer.exeC:\Windows\explorer.exe2⤵
- Modifies registry class
PID:1448
-
-
C:\Users\Admin\AppData\Local\Temp\c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exeC:\Users\Admin\AppData\Local\Temp\c354cea3e66ce894f053224ce79e76a6ff2ee2d868692d6fa3fafc801393e7f0.exe2⤵
- Suspicious use of SetWindowsHookEx
PID:4896
-