Analysis
- max time kernel
153s - max time network
158s - platform
windows10-2004_x64 - resource
win10v2004-20220812-en - resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system - submitted
01/12/2022, 23:09
Static task
static1
Behavioral task
behavioral1
Sample
69353c431e5f32f591c4fd144ee9af57eec0a58ead5d2254616fc6bd8764f830.exe
Resource
win7-20220812-en
5 signatures
150 seconds
General
- Target 69353c431e5f32f591c4fd144ee9af57eec0a58ead5d2254616fc6bd8764f830.exe
- Size 1.0MB
- Sample221201-25ea9sag99
- SHA256 69353c431e5f32f591c4fd144ee9af57eec0a58ead5d2254616fc6bd8764f830
- MD5 ae32425a29d800960376c0b1368d6434
- SHA1 d9057e2eb37d59493702cdc1e64f4a1233a3d936
- SHA512 9bcc3f3b19fcbd257680affda9f030f7233bd7d514053c65621ff1ba655c414cd9900805e11e36e603564554c137c03a6a25228148be37a23868aba926135269
- SSDEEP 24576:J4bVUFIbQDuggc3clq/XvH8THaWSN3XlfMqbiSly/T/:JEeKQDNSQv2HDE3XL3Y
- MD5 SHA1 SHA512 SSDEEP
Malware Config
Signatures
- 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 4864 set thread context of 2100 4864 69353c431e5f32f591c4fd144ee9af57eec0a58ead5d2254616fc6bd8764f830.exe 80 - Program crash 1 IoCs
pid pid_target Process procid_target 4156 3292 WerFault.exe 81 - Suspicious behavior: EnumeratesProcesses 2 IoCs
pid Process 2100 69353c431e5f32f591c4fd144ee9af57eec0a58ead5d2254616fc6bd8764f830.exe 2100 69353c431e5f32f591c4fd144ee9af57eec0a58ead5d2254616fc6bd8764f830.exe - Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 2100 69353c431e5f32f591c4fd144ee9af57eec0a58ead5d2254616fc6bd8764f830.exe 2100 69353c431e5f32f591c4fd144ee9af57eec0a58ead5d2254616fc6bd8764f830.exe 2100 69353c431e5f32f591c4fd144ee9af57eec0a58ead5d2254616fc6bd8764f830.exe 2100 69353c431e5f32f591c4fd144ee9af57eec0a58ead5d2254616fc6bd8764f830.exe - Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 4864 wrote to memory of 2100 4864 69353c431e5f32f591c4fd144ee9af57eec0a58ead5d2254616fc6bd8764f830.exe 80 PID 4864 wrote to memory of 2100 4864 69353c431e5f32f591c4fd144ee9af57eec0a58ead5d2254616fc6bd8764f830.exe 80 PID 4864 wrote to memory of 2100 4864 69353c431e5f32f591c4fd144ee9af57eec0a58ead5d2254616fc6bd8764f830.exe 80 PID 4864 wrote to memory of 2100 4864 69353c431e5f32f591c4fd144ee9af57eec0a58ead5d2254616fc6bd8764f830.exe 80 PID 4864 wrote to memory of 2100 4864 69353c431e5f32f591c4fd144ee9af57eec0a58ead5d2254616fc6bd8764f830.exe 80 PID 4864 wrote to memory of 2100 4864 69353c431e5f32f591c4fd144ee9af57eec0a58ead5d2254616fc6bd8764f830.exe 80 PID 4864 wrote to memory of 2100 4864 69353c431e5f32f591c4fd144ee9af57eec0a58ead5d2254616fc6bd8764f830.exe 80 PID 4864 wrote to memory of 2100 4864 69353c431e5f32f591c4fd144ee9af57eec0a58ead5d2254616fc6bd8764f830.exe 80 PID 4864 wrote to memory of 2100 4864 69353c431e5f32f591c4fd144ee9af57eec0a58ead5d2254616fc6bd8764f830.exe 80 PID 4864 wrote to memory of 2100 4864 69353c431e5f32f591c4fd144ee9af57eec0a58ead5d2254616fc6bd8764f830.exe 80
Processes
-
C:\Users\Admin\AppData\Local\Temp\69353c431e5f32f591c4fd144ee9af57eec0a58ead5d2254616fc6bd8764f830.exe"C:\Users\Admin\AppData\Local\Temp\69353c431e5f32f591c4fd144ee9af57eec0a58ead5d2254616fc6bd8764f830.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4864 -
C:\Users\Admin\AppData\Local\Temp\69353c431e5f32f591c4fd144ee9af57eec0a58ead5d2254616fc6bd8764f830.exe"C:\Users\Admin\AppData\Local\Temp\69353c431e5f32f591c4fd144ee9af57eec0a58ead5d2254616fc6bd8764f830.exe"2⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
PID:2100
-
-
C:\Windows\system32\WerFault.exeC:\Windows\system32\WerFault.exe -pss -s 444 -p 3292 -ip 32921⤵PID:2704
-
C:\Windows\system32\WerFault.exeC:\Windows\system32\WerFault.exe -u -p 3292 -s 11081⤵
- Program crash
PID:4156