Analysis
-
max time kernel
122s -
max time network
145s -
platform
windows7_x64 -
resource
win7-20231215-en -
resource tags
arch:x64arch:x86image:win7-20231215-enlocale:en-usos:windows7-x64system -
submitted
02-01-2024 17:16
Static task
static1
Behavioral task
behavioral1
Sample
3e8e29ab05cb639a6400da227edcb95d.exe
Resource
win7-20231215-en
Behavioral task
behavioral2
Sample
3e8e29ab05cb639a6400da227edcb95d.exe
Resource
win10v2004-20231215-en
General
-
Target
3e8e29ab05cb639a6400da227edcb95d.exe
-
Size
801KB
-
MD5
3e8e29ab05cb639a6400da227edcb95d
-
SHA1
2025890310d262b7ed6a9ef278ad31451408e497
-
SHA256
f97f6b0ddaeec2698ad2d2403031fab366438bc8a046a7d29b3f0ae801c41f37
-
SHA512
306f5b94f8a91021cf60acde59059089c392b0a89082a1de881dc6974bbd8d21416a117574ae24882aa203aa99473e83bc369887880d422f866b646ae2450dba
-
SSDEEP
12288:4ooR65AXwgFvuSSPsLk0mvqc/YZUKQ4cnXbbb9qnkMqIwaCYKQYFCD8:JoR6qgnvq+n74+DokMqZFvtCY
Malware Config
Extracted
oski
marbellacabs.com/hao/
Signatures
-
Oski
Oski is an infostealer targeting browser data, crypto wallets.
-
Reads user/profile data of web browsers 2 TTPs
Infostealers often target stored browser data, which can include saved credentials etc.
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2248 set thread context of 2140 2248 3e8e29ab05cb639a6400da227edcb95d.exe 30 -
Program crash 1 IoCs
pid pid_target Process procid_target 3008 2140 WerFault.exe 30 -
Suspicious use of WriteProcessMemory 14 IoCs
description pid Process procid_target PID 2248 wrote to memory of 2140 2248 3e8e29ab05cb639a6400da227edcb95d.exe 30 PID 2248 wrote to memory of 2140 2248 3e8e29ab05cb639a6400da227edcb95d.exe 30 PID 2248 wrote to memory of 2140 2248 3e8e29ab05cb639a6400da227edcb95d.exe 30 PID 2248 wrote to memory of 2140 2248 3e8e29ab05cb639a6400da227edcb95d.exe 30 PID 2248 wrote to memory of 2140 2248 3e8e29ab05cb639a6400da227edcb95d.exe 30 PID 2248 wrote to memory of 2140 2248 3e8e29ab05cb639a6400da227edcb95d.exe 30 PID 2248 wrote to memory of 2140 2248 3e8e29ab05cb639a6400da227edcb95d.exe 30 PID 2248 wrote to memory of 2140 2248 3e8e29ab05cb639a6400da227edcb95d.exe 30 PID 2248 wrote to memory of 2140 2248 3e8e29ab05cb639a6400da227edcb95d.exe 30 PID 2248 wrote to memory of 2140 2248 3e8e29ab05cb639a6400da227edcb95d.exe 30 PID 2140 wrote to memory of 3008 2140 3e8e29ab05cb639a6400da227edcb95d.exe 32 PID 2140 wrote to memory of 3008 2140 3e8e29ab05cb639a6400da227edcb95d.exe 32 PID 2140 wrote to memory of 3008 2140 3e8e29ab05cb639a6400da227edcb95d.exe 32 PID 2140 wrote to memory of 3008 2140 3e8e29ab05cb639a6400da227edcb95d.exe 32
Processes
-
C:\Users\Admin\AppData\Local\Temp\3e8e29ab05cb639a6400da227edcb95d.exe"C:\Users\Admin\AppData\Local\Temp\3e8e29ab05cb639a6400da227edcb95d.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2248 -
C:\Users\Admin\AppData\Local\Temp\3e8e29ab05cb639a6400da227edcb95d.exe"C:\Users\Admin\AppData\Local\Temp\3e8e29ab05cb639a6400da227edcb95d.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:2140 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2140 -s 8643⤵
- Program crash
PID:3008
-
-