Analysis
-
max time kernel
143s -
max time network
158s -
platform
windows10-2004_x64 -
resource
win10v2004-20240226-en -
resource tags
arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system -
submitted
20-04-2024 09:04
Behavioral task
behavioral1
Sample
Loader.exe
Resource
win7-20231129-en
windows7-x64
5 signatures
150 seconds
Behavioral task
behavioral2
Sample
Loader.exe
Resource
win10v2004-20240226-en
windows10-2004-x64
6 signatures
150 seconds
General
-
Target
Loader.exe
-
Size
5.0MB
-
MD5
e9a24c7a42f9b296cc1e31dc3ea73b2b
-
SHA1
06e9607fb973400f0f110854ce90382965cd43d9
-
SHA256
03ee5437a1dad818f417db18dd50e16bc08c890b442874d841cd1a6a643c4010
-
SHA512
48af794e0042ce3cea37ff11e3f9b74d0a8e463018fc827d7ef459cc58252a5f436632c19b5d4674a6b54f02543005a294ef94f86d46d1ecff574ba6fab0464b
-
SSDEEP
98304:XrdCegVSGMzByLXMfivQayGnOht5RTc7kjRX1LNNDw7:waGMlyLXvvQdmmt5RTcGzLNe7
Score
7/10
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/1600-0-0x00007FF7C9090000-0x00007FF7C9AB0000-memory.dmp vmprotect -
Kills process with taskkill 1 IoCs
pid Process 4988 taskkill.exe -
Runs net.exe
-
Suspicious use of AdjustPrivilegeToken 1 IoCs
description pid Process Token: SeDebugPrivilege 4988 taskkill.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 1600 Loader.exe -
Suspicious use of WriteProcessMemory 14 IoCs
description pid Process procid_target PID 1600 wrote to memory of 4652 1600 Loader.exe 92 PID 1600 wrote to memory of 4652 1600 Loader.exe 92 PID 4652 wrote to memory of 4364 4652 cmd.exe 93 PID 4652 wrote to memory of 4364 4652 cmd.exe 93 PID 4364 wrote to memory of 660 4364 net.exe 94 PID 4364 wrote to memory of 660 4364 net.exe 94 PID 1600 wrote to memory of 4408 1600 Loader.exe 95 PID 1600 wrote to memory of 4408 1600 Loader.exe 95 PID 4408 wrote to memory of 4168 4408 cmd.exe 96 PID 4408 wrote to memory of 4168 4408 cmd.exe 96 PID 1600 wrote to memory of 620 1600 Loader.exe 97 PID 1600 wrote to memory of 620 1600 Loader.exe 97 PID 620 wrote to memory of 4988 620 cmd.exe 98 PID 620 wrote to memory of 4988 620 cmd.exe 98
Processes
-
C:\Users\Admin\AppData\Local\Temp\Loader.exe"C:\Users\Admin\AppData\Local\Temp\Loader.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1600 -
C:\Windows\system32\cmd.exeC:\Windows\system32\cmd.exe /c net start w32time2⤵
- Suspicious use of WriteProcessMemory
PID:4652 -
C:\Windows\system32\net.exenet start w32time3⤵
- Suspicious use of WriteProcessMemory
PID:4364 -
C:\Windows\system32\net1.exeC:\Windows\system32\net1 start w32time4⤵PID:660
-
-
-
-
C:\Windows\system32\cmd.exeC:\Windows\system32\cmd.exe /c w32tm /resync /nowait2⤵
- Suspicious use of WriteProcessMemory
PID:4408 -
C:\Windows\system32\w32tm.exew32tm /resync /nowait3⤵PID:4168
-
-
-
C:\Windows\system32\cmd.exeC:\Windows\system32\cmd.exe /c taskkill /IM RainbowSix.exe /f2⤵
- Suspicious use of WriteProcessMemory
PID:620 -
C:\Windows\system32\taskkill.exetaskkill /IM RainbowSix.exe /f3⤵
- Kills process with taskkill
- Suspicious use of AdjustPrivilegeToken
PID:4988
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --type=utility --utility-sub-type=asset_store.mojom.AssetStoreService --lang=en-US --service-sandbox-type=asset_store_service --no-appcompat-clear --mojo-platform-channel-handle=4060 --field-trial-handle=3240,i,13319578961094268484,16557498665191861597,262144 --variations-seed-version /prefetch:81⤵PID:3136