Analysis
-
max time kernel
2s -
max time network
148s -
platform
windows10-2004_x64 -
resource
win10v2004-20231222-en -
resource tags
arch:x64arch:x86image:win10v2004-20231222-enlocale:en-usos:windows10-2004-x64system -
submitted
31/12/2023, 04:11
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
27a0db1e476d5f99524225521dce569e.exe
Resource
win7-20231215-en
6 signatures
150 seconds
Behavioral task
behavioral2
Sample
27a0db1e476d5f99524225521dce569e.exe
Resource
win10v2004-20231222-en
5 signatures
150 seconds
General
-
Target
27a0db1e476d5f99524225521dce569e.exe
-
Size
52KB
-
MD5
27a0db1e476d5f99524225521dce569e
-
SHA1
ff30d543951d7d33a8ba415945ff1b973d169e0e
-
SHA256
326b669abea961fc473bc010010cb96524bcfb5519157e55700a80f067a6d8af
-
SHA512
2864645a2e7ff65253a0cda2f3e766e6619c14f6fb08e32b9bc471a92deb92d069ccd53d2ff73a13b656d9cca378d406f620091f62d8272062ed62c133920e06
-
SSDEEP
768:C96E8n34lzc8VoE4tytrPsSm9vt51r4lzc6E8n3:Cw4Bc8+stAHl51r4Bc
Score
8/10
Malware Config
Signatures
-
Stops running service(s) 3 TTPs
-
Launches sc.exe 2 IoCs
Sc.exe is a Windows utlilty to control services on the system.
pid Process 5084 sc.exe 4228 sc.exe -
Runs net.exe
-
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 4668 27a0db1e476d5f99524225521dce569e.exe -
Suspicious use of WriteProcessMemory 18 IoCs
description pid Process procid_target PID 4668 wrote to memory of 5080 4668 27a0db1e476d5f99524225521dce569e.exe 115 PID 4668 wrote to memory of 5080 4668 27a0db1e476d5f99524225521dce569e.exe 115 PID 4668 wrote to memory of 5080 4668 27a0db1e476d5f99524225521dce569e.exe 115 PID 4668 wrote to memory of 2764 4668 27a0db1e476d5f99524225521dce569e.exe 116 PID 4668 wrote to memory of 2764 4668 27a0db1e476d5f99524225521dce569e.exe 116 PID 4668 wrote to memory of 2764 4668 27a0db1e476d5f99524225521dce569e.exe 116 PID 5080 wrote to memory of 3944 5080 sihclient.exe 44 PID 5080 wrote to memory of 3944 5080 sihclient.exe 44 PID 5080 wrote to memory of 3944 5080 sihclient.exe 44 PID 2764 wrote to memory of 2616 2764 backgroundTaskHost.exe 43 PID 2764 wrote to memory of 2616 2764 backgroundTaskHost.exe 43 PID 2764 wrote to memory of 2616 2764 backgroundTaskHost.exe 43 PID 4668 wrote to memory of 4228 4668 27a0db1e476d5f99524225521dce569e.exe 51 PID 4668 wrote to memory of 4228 4668 27a0db1e476d5f99524225521dce569e.exe 51 PID 4668 wrote to memory of 4228 4668 27a0db1e476d5f99524225521dce569e.exe 51 PID 4668 wrote to memory of 5084 4668 27a0db1e476d5f99524225521dce569e.exe 50 PID 4668 wrote to memory of 5084 4668 27a0db1e476d5f99524225521dce569e.exe 50 PID 4668 wrote to memory of 5084 4668 27a0db1e476d5f99524225521dce569e.exe 50
Processes
-
C:\Users\Admin\AppData\Local\Temp\27a0db1e476d5f99524225521dce569e.exe"C:\Users\Admin\AppData\Local\Temp\27a0db1e476d5f99524225521dce569e.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4668 -
C:\Windows\SysWOW64\net.exenet stop sharedaccess2⤵PID:2764
-
-
C:\Windows\SysWOW64\net.exenet stop wscsvc2⤵PID:5080
-
-
C:\Windows\SysWOW64\sc.exesc delete sharedaccess2⤵
- Launches sc.exe
PID:5084
-
-
C:\Windows\SysWOW64\sc.exesc delete wscsvc2⤵
- Launches sc.exe
PID:4228
-
-
C:\Windows\SysWOW64\cmd.exeC:\Windows\system32\cmd.exe /c C:\Users\Admin\AppData\Local\Temp\27a0db1e476d5f99524225521dce569e.bat C:\Users\Admin\AppData\Local\Temp\27a0db1e476d5f99524225521dce569e.exe C:\Users\Admin\AppData\Local\Temp\27a0db1e476d5f99524225521dce569e.bat2⤵PID:684
-
-
C:\Windows\SysWOW64\net1.exeC:\Windows\system32\net1 stop sharedaccess1⤵PID:2616
-
C:\Windows\SysWOW64\net1.exeC:\Windows\system32\net1 stop wscsvc1⤵PID:3944
-
C:\Windows\System32\sihclient.exeC:\Windows\System32\sihclient.exe /cv RGNuxtVvy0OUqMMGfSahNQ.0.21⤵
- Suspicious use of WriteProcessMemory
PID:5080
-
C:\Windows\system32\backgroundTaskHost.exe"C:\Windows\system32\backgroundTaskHost.exe" -ServerName:App.AppXmtcan0h2tfbfy7k9kn8hbxb6dmzz1zh0.mca1⤵
- Suspicious use of WriteProcessMemory
PID:2764