Analysis
-
max time kernel
125s -
max time network
138s -
platform
windows10-1703_x64 -
resource
win10-20231020-en -
resource tags
arch:x64arch:x86image:win10-20231020-enlocale:en-usos:windows10-1703-x64system -
submitted
31-10-2023 16:37
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
f90d49f04c62f8d43b9d8505af5abfde35120b9b5e697db3db450fe5ae3e2636.exe
Resource
win10-20231020-en
windows10-1703-x64
2 signatures
150 seconds
General
-
Target
f90d49f04c62f8d43b9d8505af5abfde35120b9b5e697db3db450fe5ae3e2636.exe
-
Size
1.0MB
-
MD5
fe844f3596e698e87b06367b0e0bac00
-
SHA1
35990eee996396a9f74f43883fb53386c868cc67
-
SHA256
f90d49f04c62f8d43b9d8505af5abfde35120b9b5e697db3db450fe5ae3e2636
-
SHA512
82a8002cf53f22c83a9a49582f2f2598fc7f93689cdba76424717da08f7a2f29f85a9efb742343f492f61404ab15219f95a23ad3ff90c077930e86e3f7315bb3
-
SSDEEP
12288:rtR2mYRJrnmf/KS/XNdP2V0JRY/a+agcktcJwulyrym2r4m4Kvv2CM10:pkzBnmf/KS/XN1/J2Ugckwr4Qv27
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4816 set thread context of 4148 4816 f90d49f04c62f8d43b9d8505af5abfde35120b9b5e697db3db450fe5ae3e2636.exe 72 -
Suspicious use of WriteProcessMemory 13 IoCs
description pid Process procid_target PID 4816 wrote to memory of 1020 4816 f90d49f04c62f8d43b9d8505af5abfde35120b9b5e697db3db450fe5ae3e2636.exe 71 PID 4816 wrote to memory of 1020 4816 f90d49f04c62f8d43b9d8505af5abfde35120b9b5e697db3db450fe5ae3e2636.exe 71 PID 4816 wrote to memory of 1020 4816 f90d49f04c62f8d43b9d8505af5abfde35120b9b5e697db3db450fe5ae3e2636.exe 71 PID 4816 wrote to memory of 4148 4816 f90d49f04c62f8d43b9d8505af5abfde35120b9b5e697db3db450fe5ae3e2636.exe 72 PID 4816 wrote to memory of 4148 4816 f90d49f04c62f8d43b9d8505af5abfde35120b9b5e697db3db450fe5ae3e2636.exe 72 PID 4816 wrote to memory of 4148 4816 f90d49f04c62f8d43b9d8505af5abfde35120b9b5e697db3db450fe5ae3e2636.exe 72 PID 4816 wrote to memory of 4148 4816 f90d49f04c62f8d43b9d8505af5abfde35120b9b5e697db3db450fe5ae3e2636.exe 72 PID 4816 wrote to memory of 4148 4816 f90d49f04c62f8d43b9d8505af5abfde35120b9b5e697db3db450fe5ae3e2636.exe 72 PID 4816 wrote to memory of 4148 4816 f90d49f04c62f8d43b9d8505af5abfde35120b9b5e697db3db450fe5ae3e2636.exe 72 PID 4816 wrote to memory of 4148 4816 f90d49f04c62f8d43b9d8505af5abfde35120b9b5e697db3db450fe5ae3e2636.exe 72 PID 4816 wrote to memory of 4148 4816 f90d49f04c62f8d43b9d8505af5abfde35120b9b5e697db3db450fe5ae3e2636.exe 72 PID 4816 wrote to memory of 4148 4816 f90d49f04c62f8d43b9d8505af5abfde35120b9b5e697db3db450fe5ae3e2636.exe 72 PID 4816 wrote to memory of 4148 4816 f90d49f04c62f8d43b9d8505af5abfde35120b9b5e697db3db450fe5ae3e2636.exe 72
Processes
-
C:\Users\Admin\AppData\Local\Temp\f90d49f04c62f8d43b9d8505af5abfde35120b9b5e697db3db450fe5ae3e2636.exe"C:\Users\Admin\AppData\Local\Temp\f90d49f04c62f8d43b9d8505af5abfde35120b9b5e697db3db450fe5ae3e2636.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4816 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:1020
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:4148
-