Analysis
-
max time kernel
93s -
max time network
157s -
platform
windows10-2004_x64 -
resource
win10v2004-20230915-en -
resource tags
arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system -
submitted
16/10/2023, 00:38
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
2f692d2c3aa1946a5a5f498699caa54c9629716e619437743f151bf54f2b2430.exe
Resource
win10v2004-20230915-en
3 signatures
150 seconds
General
-
Target
2f692d2c3aa1946a5a5f498699caa54c9629716e619437743f151bf54f2b2430.exe
-
Size
295KB
-
MD5
63ea15b5d412638ff7fe449d2bc94823
-
SHA1
b0e3fc3b8b4ca5a70f478fe346e975b89ea3ce0e
-
SHA256
2f692d2c3aa1946a5a5f498699caa54c9629716e619437743f151bf54f2b2430
-
SHA512
017a5b2437064426cdafff034f7a70ac1951b31cd379919634061a0d68a872942e2e0faf8ce05c02b1e7b81f5b3401dc5e1e41e3688188200e709be122d411e9
-
SSDEEP
6144:KZEe3bpi5aaYm6/C8D+U4HFn9xF3iqraMHX/bJwU/I8TJn:KZEe3D8HF9x4qrZHjJwU/I8TJn
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 520 set thread context of 2292 520 2f692d2c3aa1946a5a5f498699caa54c9629716e619437743f151bf54f2b2430.exe 83 -
Program crash 1 IoCs
pid pid_target Process procid_target 3656 520 WerFault.exe 81 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 520 wrote to memory of 2292 520 2f692d2c3aa1946a5a5f498699caa54c9629716e619437743f151bf54f2b2430.exe 83 PID 520 wrote to memory of 2292 520 2f692d2c3aa1946a5a5f498699caa54c9629716e619437743f151bf54f2b2430.exe 83 PID 520 wrote to memory of 2292 520 2f692d2c3aa1946a5a5f498699caa54c9629716e619437743f151bf54f2b2430.exe 83 PID 520 wrote to memory of 2292 520 2f692d2c3aa1946a5a5f498699caa54c9629716e619437743f151bf54f2b2430.exe 83 PID 520 wrote to memory of 2292 520 2f692d2c3aa1946a5a5f498699caa54c9629716e619437743f151bf54f2b2430.exe 83 PID 520 wrote to memory of 2292 520 2f692d2c3aa1946a5a5f498699caa54c9629716e619437743f151bf54f2b2430.exe 83 PID 520 wrote to memory of 2292 520 2f692d2c3aa1946a5a5f498699caa54c9629716e619437743f151bf54f2b2430.exe 83 PID 520 wrote to memory of 2292 520 2f692d2c3aa1946a5a5f498699caa54c9629716e619437743f151bf54f2b2430.exe 83 PID 520 wrote to memory of 2292 520 2f692d2c3aa1946a5a5f498699caa54c9629716e619437743f151bf54f2b2430.exe 83 PID 520 wrote to memory of 2292 520 2f692d2c3aa1946a5a5f498699caa54c9629716e619437743f151bf54f2b2430.exe 83
Processes
-
C:\Users\Admin\AppData\Local\Temp\2f692d2c3aa1946a5a5f498699caa54c9629716e619437743f151bf54f2b2430.exe"C:\Users\Admin\AppData\Local\Temp\2f692d2c3aa1946a5a5f498699caa54c9629716e619437743f151bf54f2b2430.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:520 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2292
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 520 -s 2722⤵
- Program crash
PID:3656
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 452 -p 520 -ip 5201⤵PID:2696