Analysis
-
max time kernel
152s -
max time network
151s -
platform
windows10-2004_x64 -
resource
win10v2004-20240226-en -
resource tags
arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system -
submitted
10-03-2024 14:14
Behavioral task
behavioral1
Sample
becfe4901318441232f0ec4415f748db.exe
Resource
win7-20240221-en
windows7-x64
4 signatures
150 seconds
Behavioral task
behavioral2
Sample
becfe4901318441232f0ec4415f748db.exe
Resource
win10v2004-20240226-en
windows10-2004-x64
4 signatures
150 seconds
General
-
Target
becfe4901318441232f0ec4415f748db.exe
-
Size
175KB
-
MD5
becfe4901318441232f0ec4415f748db
-
SHA1
d56ca6f47ca026bb367aff92c5ccacf3ff169fb0
-
SHA256
904ce94f5e9aad4a0c3432071857db5cf787b8059a37ad2b7e9e3f4be5406655
-
SHA512
674549195b047d787c9c9fbe961cb142ef4d4c0321e9d969e1639e1e11dc97c1e4c3811dd84faf344c06f32584fca568de37a65df504cd76241082eee2a43817
-
SSDEEP
3072:mlOpMhGUjEWDw7yqKuZ+yQbDCaaCT6ocaHZgsfBBZdbM:kOcgWbLuHQvdlB5npBZO
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3700 set thread context of 2900 3700 becfe4901318441232f0ec4415f748db.exe 97 -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 2900 becfe4901318441232f0ec4415f748db.exe 2900 becfe4901318441232f0ec4415f748db.exe 2900 becfe4901318441232f0ec4415f748db.exe 2900 becfe4901318441232f0ec4415f748db.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 3700 becfe4901318441232f0ec4415f748db.exe -
Suspicious use of WriteProcessMemory 11 IoCs
description pid Process procid_target PID 3700 wrote to memory of 2900 3700 becfe4901318441232f0ec4415f748db.exe 97 PID 3700 wrote to memory of 2900 3700 becfe4901318441232f0ec4415f748db.exe 97 PID 3700 wrote to memory of 2900 3700 becfe4901318441232f0ec4415f748db.exe 97 PID 3700 wrote to memory of 2900 3700 becfe4901318441232f0ec4415f748db.exe 97 PID 3700 wrote to memory of 2900 3700 becfe4901318441232f0ec4415f748db.exe 97 PID 3700 wrote to memory of 2900 3700 becfe4901318441232f0ec4415f748db.exe 97 PID 3700 wrote to memory of 2900 3700 becfe4901318441232f0ec4415f748db.exe 97 PID 2900 wrote to memory of 3336 2900 becfe4901318441232f0ec4415f748db.exe 56 PID 2900 wrote to memory of 3336 2900 becfe4901318441232f0ec4415f748db.exe 56 PID 2900 wrote to memory of 3336 2900 becfe4901318441232f0ec4415f748db.exe 56 PID 2900 wrote to memory of 3336 2900 becfe4901318441232f0ec4415f748db.exe 56
Processes
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:3336
-
C:\Users\Admin\AppData\Local\Temp\becfe4901318441232f0ec4415f748db.exe"C:\Users\Admin\AppData\Local\Temp\becfe4901318441232f0ec4415f748db.exe"2⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3700 -
C:\Users\Admin\AppData\Local\Temp\becfe4901318441232f0ec4415f748db.exe"C:\Users\Admin\AppData\Local\Temp\becfe4901318441232f0ec4415f748db.exe"3⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:2900
-
-
-
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=1328 --field-trial-handle=3060,i,1774866140584649235,8085848018931772189,262144 --variations-seed-version /prefetch:81⤵PID:4132