Analysis
-
max time kernel
143s -
max time network
153s -
platform
windows10-2004_x64 -
resource
win10v2004-20230915-en -
resource tags
arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system -
submitted
18/09/2023, 04:45
Static task
static1
Behavioral task
behavioral1
Sample
1a719d2e782c0b0c3d5176191cec1633f78c8b876881f6ea5376fc82174a41cc.exe
Resource
win10v2004-20230915-en
2 signatures
150 seconds
General
-
Target
1a719d2e782c0b0c3d5176191cec1633f78c8b876881f6ea5376fc82174a41cc.exe
-
Size
371KB
-
MD5
5eac59c9bc13f31770e2254319dedce3
-
SHA1
d6e4326cf8ae41e7400d546973c713cd77de2e4e
-
SHA256
1a719d2e782c0b0c3d5176191cec1633f78c8b876881f6ea5376fc82174a41cc
-
SHA512
f84fa1064661aa9f48c18390dc41b348535bb173c19caad8761c21200b2be04cdede26eff9caa615505e249c14d275ec24ec6f4802cc3833d26c057121506a70
-
SSDEEP
6144:nFvJm09zORs+z/TMify9DAOJgQbGw+RC3Bmunmc7Q18/:nNw09CK5NkubSC3Bmun37I8/
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3956 set thread context of 4760 3956 1a719d2e782c0b0c3d5176191cec1633f78c8b876881f6ea5376fc82174a41cc.exe 88 -
Suspicious use of WriteProcessMemory 13 IoCs
description pid Process procid_target PID 3956 wrote to memory of 2352 3956 1a719d2e782c0b0c3d5176191cec1633f78c8b876881f6ea5376fc82174a41cc.exe 87 PID 3956 wrote to memory of 2352 3956 1a719d2e782c0b0c3d5176191cec1633f78c8b876881f6ea5376fc82174a41cc.exe 87 PID 3956 wrote to memory of 2352 3956 1a719d2e782c0b0c3d5176191cec1633f78c8b876881f6ea5376fc82174a41cc.exe 87 PID 3956 wrote to memory of 4760 3956 1a719d2e782c0b0c3d5176191cec1633f78c8b876881f6ea5376fc82174a41cc.exe 88 PID 3956 wrote to memory of 4760 3956 1a719d2e782c0b0c3d5176191cec1633f78c8b876881f6ea5376fc82174a41cc.exe 88 PID 3956 wrote to memory of 4760 3956 1a719d2e782c0b0c3d5176191cec1633f78c8b876881f6ea5376fc82174a41cc.exe 88 PID 3956 wrote to memory of 4760 3956 1a719d2e782c0b0c3d5176191cec1633f78c8b876881f6ea5376fc82174a41cc.exe 88 PID 3956 wrote to memory of 4760 3956 1a719d2e782c0b0c3d5176191cec1633f78c8b876881f6ea5376fc82174a41cc.exe 88 PID 3956 wrote to memory of 4760 3956 1a719d2e782c0b0c3d5176191cec1633f78c8b876881f6ea5376fc82174a41cc.exe 88 PID 3956 wrote to memory of 4760 3956 1a719d2e782c0b0c3d5176191cec1633f78c8b876881f6ea5376fc82174a41cc.exe 88 PID 3956 wrote to memory of 4760 3956 1a719d2e782c0b0c3d5176191cec1633f78c8b876881f6ea5376fc82174a41cc.exe 88 PID 3956 wrote to memory of 4760 3956 1a719d2e782c0b0c3d5176191cec1633f78c8b876881f6ea5376fc82174a41cc.exe 88 PID 3956 wrote to memory of 4760 3956 1a719d2e782c0b0c3d5176191cec1633f78c8b876881f6ea5376fc82174a41cc.exe 88
Processes
-
C:\Users\Admin\AppData\Local\Temp\1a719d2e782c0b0c3d5176191cec1633f78c8b876881f6ea5376fc82174a41cc.exe"C:\Users\Admin\AppData\Local\Temp\1a719d2e782c0b0c3d5176191cec1633f78c8b876881f6ea5376fc82174a41cc.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3956 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2352
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:4760
-