Analysis
-
max time kernel
142s -
max time network
153s -
platform
windows10-2004_x64 -
resource
win10v2004-20231020-en -
resource tags
arch:x64arch:x86image:win10v2004-20231020-enlocale:en-usos:windows10-2004-x64system -
submitted
23-10-2023 19:33
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
38e876392c87933fc62c51dd1e992c6039eafa7bb61794befc3dcad78579703b.exe
Resource
win10v2004-20231020-en
windows10-2004-x64
2 signatures
150 seconds
General
-
Target
38e876392c87933fc62c51dd1e992c6039eafa7bb61794befc3dcad78579703b.exe
-
Size
1.8MB
-
MD5
fea6e39bb0484ce2d6433670affb9014
-
SHA1
b0b12c92cec981faa5108d890f7b7de8f471e754
-
SHA256
38e876392c87933fc62c51dd1e992c6039eafa7bb61794befc3dcad78579703b
-
SHA512
f52f2bf225de7905fdfbc89397f880d89ca58aea017c468f3b8a6642d271ce3bff383dcda8490c73d2f8b955333408ec9a18e30114b552873de6ff08290f1f4e
-
SSDEEP
24576:jaAfSfS8a1TTnEX1xo6a9Dhvhad4NB4Iu5mRI:jcS8a1To166a3vIa+5mR
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 5072 set thread context of 1672 5072 38e876392c87933fc62c51dd1e992c6039eafa7bb61794befc3dcad78579703b.exe 89 -
Suspicious use of WriteProcessMemory 13 IoCs
description pid Process procid_target PID 5072 wrote to memory of 1304 5072 38e876392c87933fc62c51dd1e992c6039eafa7bb61794befc3dcad78579703b.exe 88 PID 5072 wrote to memory of 1304 5072 38e876392c87933fc62c51dd1e992c6039eafa7bb61794befc3dcad78579703b.exe 88 PID 5072 wrote to memory of 1304 5072 38e876392c87933fc62c51dd1e992c6039eafa7bb61794befc3dcad78579703b.exe 88 PID 5072 wrote to memory of 1672 5072 38e876392c87933fc62c51dd1e992c6039eafa7bb61794befc3dcad78579703b.exe 89 PID 5072 wrote to memory of 1672 5072 38e876392c87933fc62c51dd1e992c6039eafa7bb61794befc3dcad78579703b.exe 89 PID 5072 wrote to memory of 1672 5072 38e876392c87933fc62c51dd1e992c6039eafa7bb61794befc3dcad78579703b.exe 89 PID 5072 wrote to memory of 1672 5072 38e876392c87933fc62c51dd1e992c6039eafa7bb61794befc3dcad78579703b.exe 89 PID 5072 wrote to memory of 1672 5072 38e876392c87933fc62c51dd1e992c6039eafa7bb61794befc3dcad78579703b.exe 89 PID 5072 wrote to memory of 1672 5072 38e876392c87933fc62c51dd1e992c6039eafa7bb61794befc3dcad78579703b.exe 89 PID 5072 wrote to memory of 1672 5072 38e876392c87933fc62c51dd1e992c6039eafa7bb61794befc3dcad78579703b.exe 89 PID 5072 wrote to memory of 1672 5072 38e876392c87933fc62c51dd1e992c6039eafa7bb61794befc3dcad78579703b.exe 89 PID 5072 wrote to memory of 1672 5072 38e876392c87933fc62c51dd1e992c6039eafa7bb61794befc3dcad78579703b.exe 89 PID 5072 wrote to memory of 1672 5072 38e876392c87933fc62c51dd1e992c6039eafa7bb61794befc3dcad78579703b.exe 89
Processes
-
C:\Users\Admin\AppData\Local\Temp\38e876392c87933fc62c51dd1e992c6039eafa7bb61794befc3dcad78579703b.exe"C:\Users\Admin\AppData\Local\Temp\38e876392c87933fc62c51dd1e992c6039eafa7bb61794befc3dcad78579703b.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:5072 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:1304
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:1672
-