Analysis
-
max time kernel
142s -
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
05/03/2024, 04:07
Behavioral task
behavioral1
Sample
b3bd4994b3221f99fd345f4c2117d219.exe
Resource
win7-20240221-en
2 signatures
150 seconds
Behavioral task
behavioral2
Sample
b3bd4994b3221f99fd345f4c2117d219.exe
Resource
win10v2004-20240226-en
3 signatures
150 seconds
General
-
Target
b3bd4994b3221f99fd345f4c2117d219.exe
-
Size
70KB
-
MD5
b3bd4994b3221f99fd345f4c2117d219
-
SHA1
20e07cec530914d6d9ff296bfb8d4ba77ab888b2
-
SHA256
9cd46f06c4282008ba9f65b536490d8688b130424a9af782131261aad18dfecb
-
SHA512
36241bdccb584ddbce616d26381f50e1e98a72ba29f4444b9d54030317fe8b877de09aa03113b3367ba8162c22676201a712ec536c097c204779956639f747f8
-
SSDEEP
1536:5plWqz4gaOSDTYSOdaNHSdQtUdx5PKK3UqpqEH:9itOSDsSOOSdQ6PKD6q
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3620 set thread context of 4260 3620 b3bd4994b3221f99fd345f4c2117d219.exe 95 -
Program crash 1 IoCs
pid pid_target Process procid_target 4088 4260 WerFault.exe 95 -
Suspicious use of WriteProcessMemory 9 IoCs
description pid Process procid_target PID 3620 wrote to memory of 4260 3620 b3bd4994b3221f99fd345f4c2117d219.exe 95 PID 3620 wrote to memory of 4260 3620 b3bd4994b3221f99fd345f4c2117d219.exe 95 PID 3620 wrote to memory of 4260 3620 b3bd4994b3221f99fd345f4c2117d219.exe 95 PID 3620 wrote to memory of 4260 3620 b3bd4994b3221f99fd345f4c2117d219.exe 95 PID 3620 wrote to memory of 4260 3620 b3bd4994b3221f99fd345f4c2117d219.exe 95 PID 3620 wrote to memory of 4260 3620 b3bd4994b3221f99fd345f4c2117d219.exe 95 PID 3620 wrote to memory of 4260 3620 b3bd4994b3221f99fd345f4c2117d219.exe 95 PID 3620 wrote to memory of 4260 3620 b3bd4994b3221f99fd345f4c2117d219.exe 95 PID 3620 wrote to memory of 4260 3620 b3bd4994b3221f99fd345f4c2117d219.exe 95
Processes
-
C:\Users\Admin\AppData\Local\Temp\b3bd4994b3221f99fd345f4c2117d219.exe"C:\Users\Admin\AppData\Local\Temp\b3bd4994b3221f99fd345f4c2117d219.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3620 -
C:\Users\Admin\AppData\Local\Temp\b3bd4994b3221f99fd345f4c2117d219.exe"C:\Users\Admin\AppData\Local\Temp\b3bd4994b3221f99fd345f4c2117d219.exe"2⤵PID:4260
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4260 -s 123⤵
- Program crash
PID:4088
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 192 -p 4260 -ip 42601⤵PID:4392
-
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=1416 --field-trial-handle=3240,i,13319578961094268484,16557498665191861597,262144 --variations-seed-version /prefetch:81⤵PID:676