Analysis
-
max time kernel
74s -
max time network
79s -
platform
windows7_x64 -
resource
win7-20220414-en -
submitted
24-05-2022 01:21
Static task
static1
Behavioral task
behavioral1
Sample
74fed62553501ee21a1ec9bfd2e0d3785dec401249c9da3154fbe6b10c713038.exe
Resource
win7-20220414-en
Behavioral task
behavioral2
Sample
74fed62553501ee21a1ec9bfd2e0d3785dec401249c9da3154fbe6b10c713038.exe
Resource
win10v2004-20220414-en
General
-
Target
74fed62553501ee21a1ec9bfd2e0d3785dec401249c9da3154fbe6b10c713038.exe
-
Size
1.2MB
-
MD5
0040b750f231f0eeb175a48aebab5b48
-
SHA1
b5446600d2df181c644f9ab582f6d99440727616
-
SHA256
74fed62553501ee21a1ec9bfd2e0d3785dec401249c9da3154fbe6b10c713038
-
SHA512
58504c6b4be1c801a68d7d0339254bdf9e49a2ca8865ab7cfb9e7791fe1cf0447ed52ca395b2b160d31f7ab8ea5baff10e60a33dcce708d65b3e896bdd0f5532
Malware Config
Signatures
-
Oski
Oski is an infostealer targeting browser data, crypto wallets.
-
resource yara_rule behavioral1/memory/1620-54-0x0000000001070000-0x0000000001176000-memory.dmp vmprotect -
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 1620 set thread context of 1356 1620 74fed62553501ee21a1ec9bfd2e0d3785dec401249c9da3154fbe6b10c713038.exe 26 -
Program crash 1 IoCs
pid pid_target Process procid_target 1320 1356 WerFault.exe 26 -
Checks processor information in registry 2 TTPs 2 IoCs
Processor information is often read in order to detect sandboxing environments.
description ioc Process Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\ProcessorNameString RegAsm.exe Key opened \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0 RegAsm.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
description pid Process Token: SeDebugPrivilege 1620 74fed62553501ee21a1ec9bfd2e0d3785dec401249c9da3154fbe6b10c713038.exe -
Suspicious use of WriteProcessMemory 17 IoCs
description pid Process procid_target PID 1620 wrote to memory of 1356 1620 74fed62553501ee21a1ec9bfd2e0d3785dec401249c9da3154fbe6b10c713038.exe 26 PID 1620 wrote to memory of 1356 1620 74fed62553501ee21a1ec9bfd2e0d3785dec401249c9da3154fbe6b10c713038.exe 26 PID 1620 wrote to memory of 1356 1620 74fed62553501ee21a1ec9bfd2e0d3785dec401249c9da3154fbe6b10c713038.exe 26 PID 1620 wrote to memory of 1356 1620 74fed62553501ee21a1ec9bfd2e0d3785dec401249c9da3154fbe6b10c713038.exe 26 PID 1620 wrote to memory of 1356 1620 74fed62553501ee21a1ec9bfd2e0d3785dec401249c9da3154fbe6b10c713038.exe 26 PID 1620 wrote to memory of 1356 1620 74fed62553501ee21a1ec9bfd2e0d3785dec401249c9da3154fbe6b10c713038.exe 26 PID 1620 wrote to memory of 1356 1620 74fed62553501ee21a1ec9bfd2e0d3785dec401249c9da3154fbe6b10c713038.exe 26 PID 1620 wrote to memory of 1356 1620 74fed62553501ee21a1ec9bfd2e0d3785dec401249c9da3154fbe6b10c713038.exe 26 PID 1620 wrote to memory of 1356 1620 74fed62553501ee21a1ec9bfd2e0d3785dec401249c9da3154fbe6b10c713038.exe 26 PID 1620 wrote to memory of 1356 1620 74fed62553501ee21a1ec9bfd2e0d3785dec401249c9da3154fbe6b10c713038.exe 26 PID 1620 wrote to memory of 1356 1620 74fed62553501ee21a1ec9bfd2e0d3785dec401249c9da3154fbe6b10c713038.exe 26 PID 1620 wrote to memory of 1356 1620 74fed62553501ee21a1ec9bfd2e0d3785dec401249c9da3154fbe6b10c713038.exe 26 PID 1620 wrote to memory of 1356 1620 74fed62553501ee21a1ec9bfd2e0d3785dec401249c9da3154fbe6b10c713038.exe 26 PID 1356 wrote to memory of 1320 1356 RegAsm.exe 29 PID 1356 wrote to memory of 1320 1356 RegAsm.exe 29 PID 1356 wrote to memory of 1320 1356 RegAsm.exe 29 PID 1356 wrote to memory of 1320 1356 RegAsm.exe 29
Processes
-
C:\Users\Admin\AppData\Local\Temp\74fed62553501ee21a1ec9bfd2e0d3785dec401249c9da3154fbe6b10c713038.exe"C:\Users\Admin\AppData\Local\Temp\74fed62553501ee21a1ec9bfd2e0d3785dec401249c9da3154fbe6b10c713038.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:1620 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵
- Checks processor information in registry
- Suspicious use of WriteProcessMemory
PID:1356 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1356 -s 9003⤵
- Program crash
PID:1320
-
-