Analysis
-
max time kernel
147s -
max time network
152s -
platform
windows10-2004_x64 -
resource
win10v2004-20240226-en -
resource tags
arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system -
submitted
14-03-2024 04:12
Behavioral task
behavioral1
Sample
559db69c65b706eaacd9c0c217ed8c7390a1978a8094a1fad5d86ccdd12f8697.exe
Resource
win7-20240221-en
Behavioral task
behavioral2
Sample
559db69c65b706eaacd9c0c217ed8c7390a1978a8094a1fad5d86ccdd12f8697.exe
Resource
win10v2004-20240226-en
General
-
Target
559db69c65b706eaacd9c0c217ed8c7390a1978a8094a1fad5d86ccdd12f8697.exe
-
Size
149KB
-
MD5
52bc4aeea814b362f8c8879d0ace5362
-
SHA1
cf77e70a6ac7b87bd6c4faf45ed0f5c1bdb3519e
-
SHA256
559db69c65b706eaacd9c0c217ed8c7390a1978a8094a1fad5d86ccdd12f8697
-
SHA512
b71298a6326e0c01f7c14a0918b86401decda9f3c0a3c31dc6d20bddc9279d618ae8c8e3f67cc2ff94958edb509e5555ceba0f444436e78ee788e4b865bb96ad
-
SSDEEP
3072:xwKLL4bKdhBdCNAtAyhrJW23/qZgF02+1ul7bx2xher8vW+C3:6KfhaAtAwJWAqiN+EH2vC8vW+S
Malware Config
Signatures
-
Lockbit
Ransomware family with multiple variants released since late 2019.
-
Rule to detect Lockbit 3.0 ransomware Windows payload 2 IoCs
Processes:
resource yara_rule behavioral2/memory/2020-0-0x0000000000400000-0x0000000000429000-memory.dmp family_lockbit behavioral2/memory/2020-1-0x0000000000400000-0x0000000000429000-memory.dmp family_lockbit -
Program crash 2 IoCs
Processes:
WerFault.exeWerFault.exepid pid_target process target process 4636 2020 WerFault.exe 559db69c65b706eaacd9c0c217ed8c7390a1978a8094a1fad5d86ccdd12f8697.exe 4708 2020 WerFault.exe 559db69c65b706eaacd9c0c217ed8c7390a1978a8094a1fad5d86ccdd12f8697.exe -
Suspicious use of WriteProcessMemory 3 IoCs
Processes:
559db69c65b706eaacd9c0c217ed8c7390a1978a8094a1fad5d86ccdd12f8697.exedescription pid process target process PID 2020 wrote to memory of 4636 2020 559db69c65b706eaacd9c0c217ed8c7390a1978a8094a1fad5d86ccdd12f8697.exe WerFault.exe PID 2020 wrote to memory of 4636 2020 559db69c65b706eaacd9c0c217ed8c7390a1978a8094a1fad5d86ccdd12f8697.exe WerFault.exe PID 2020 wrote to memory of 4636 2020 559db69c65b706eaacd9c0c217ed8c7390a1978a8094a1fad5d86ccdd12f8697.exe WerFault.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\559db69c65b706eaacd9c0c217ed8c7390a1978a8094a1fad5d86ccdd12f8697.exe"C:\Users\Admin\AppData\Local\Temp\559db69c65b706eaacd9c0c217ed8c7390a1978a8094a1fad5d86ccdd12f8697.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:2020 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2020 -s 2562⤵
- Program crash
PID:4636 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2020 -s 2562⤵
- Program crash
PID:4708
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 440 -p 2020 -ip 20201⤵PID:392
-
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=4076 --field-trial-handle=2900,i,14549994492153927475,12895178890800740987,262144 --variations-seed-version /prefetch:81⤵PID:4984