Analysis
-
max time kernel
149s -
max time network
175s -
platform
windows10-2004_x64 -
resource
win10v2004-20220414-en -
submitted
08-07-2022 07:33
Static task
static1
Behavioral task
behavioral1
Sample
11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe
Resource
win7-20220414-en
General
-
Target
11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe
-
Size
434KB
-
MD5
efb61fa61dbec5252ddefef9d91d30be
-
SHA1
e36c298cd6fce8554737a623f65b8ea2051ff750
-
SHA256
11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528
-
SHA512
b3d8aa251b330103cb5bc39ead6d8bbb09a104373b7bb12e90820c174317828792087b5afef7892598a6d0e5870be6ff63ec3b6d3f3967196117328baf9f1e50
Malware Config
Signatures
-
Taurus Stealer payload 3 IoCs
Processes:
resource yara_rule behavioral2/memory/2516-142-0x0000000004C60000-0x0000000004C96000-memory.dmp family_taurus_stealer behavioral2/memory/2516-143-0x0000000000400000-0x00000000047D3000-memory.dmp family_taurus_stealer behavioral2/memory/2516-146-0x0000000000400000-0x00000000047D3000-memory.dmp family_taurus_stealer -
Processes:
resource yara_rule behavioral2/memory/4456-130-0x0000000000400000-0x0000000004DC7000-memory.dmp upx behavioral2/memory/2516-134-0x0000000000400000-0x00000000047D3000-memory.dmp upx behavioral2/memory/4456-137-0x0000000000400000-0x0000000004DC7000-memory.dmp upx behavioral2/memory/2516-136-0x0000000000400000-0x00000000047D3000-memory.dmp upx behavioral2/memory/2516-139-0x0000000000400000-0x00000000047D3000-memory.dmp upx behavioral2/memory/2516-140-0x0000000000400000-0x00000000047D3000-memory.dmp upx -
Reads user/profile data of web browsers 2 TTPs
Infostealers often target stored browser data, which can include saved credentials etc.
-
Checks installed software on the system 1 TTPs
Looks up Uninstall key entries in the registry to enumerate software on the system.
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exedescription pid process target process PID 4456 set thread context of 2516 4456 11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe 11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 4580 2516 WerFault.exe 11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe -
Delays execution with timeout.exe 1 IoCs
Processes:
timeout.exepid process 3328 timeout.exe -
Suspicious use of WriteProcessMemory 14 IoCs
Processes:
11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.execmd.exedescription pid process target process PID 4456 wrote to memory of 2516 4456 11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe 11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe PID 4456 wrote to memory of 2516 4456 11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe 11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe PID 4456 wrote to memory of 2516 4456 11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe 11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe PID 4456 wrote to memory of 2516 4456 11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe 11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe PID 4456 wrote to memory of 2516 4456 11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe 11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe PID 4456 wrote to memory of 2516 4456 11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe 11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe PID 4456 wrote to memory of 2516 4456 11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe 11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe PID 4456 wrote to memory of 2516 4456 11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe 11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe PID 2516 wrote to memory of 4492 2516 11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe cmd.exe PID 2516 wrote to memory of 4492 2516 11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe cmd.exe PID 2516 wrote to memory of 4492 2516 11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe cmd.exe PID 4492 wrote to memory of 3328 4492 cmd.exe timeout.exe PID 4492 wrote to memory of 3328 4492 cmd.exe timeout.exe PID 4492 wrote to memory of 3328 4492 cmd.exe timeout.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe"C:\Users\Admin\AppData\Local\Temp\11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4456 -
C:\Users\Admin\AppData\Local\Temp\11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe"C:\Users\Admin\AppData\Local\Temp\11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:2516 -
C:\Windows\SysWOW64\cmd.exe/c timeout /t 3 & del /f /q C:\Users\Admin\AppData\Local\Temp\11652a522645a5127f7d5a2e8e9acef96cdb89fd4cc649752da37381d70b9528.exe3⤵
- Suspicious use of WriteProcessMemory
PID:4492 -
C:\Windows\SysWOW64\timeout.exetimeout /t 34⤵
- Delays execution with timeout.exe
PID:3328
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2516 -s 12843⤵
- Program crash
PID:4580
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 440 -p 2516 -ip 25161⤵PID:4596