Analysis
- max time kernel
149s - max time network
148s - platform
windows10_x64 - resource
win10v20201028 - submitted
11/11/2020, 11:29
Static task
static1
Behavioral task
behavioral1
Sample
f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe
Resource
win7v20201028
0 signatures
0 seconds
General
- Target f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe
- Size 1.1MB
- Sample201111-95x2zce27j
- SHA256 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3
- MD5 6f315f335430f24f4a3b3d77eeff2768
- SHA1 69cf7fc7a7d8334b804dbde1a7942388a4f9dde1
- SHA512 90ba482b48257437bd1e37f143345d3110498cdd366ea12c6b940bbfe17e7a365cbd2d2a6526b2277be8b1234370f648564fb4b776e6307c4b1f44c2c24de8e1
- MD5 SHA1 SHA512
Malware Config
Extracted
Credentials
-
Protocol
smtp
-
Host
smtp.casalsmd.com
-
Port
587
-
Username
-
Password
Carolina123
Signatures
-
resource yara_rule behavioral2/memory/3100-1-0x0000000000400000-0x000000000051D000-memory.dmp upx behavioral2/memory/3100-3-0x0000000000400000-0x000000000051D000-memory.dmp upx behavioral2/memory/3100-4-0x0000000000400000-0x000000000051D000-memory.dmp upx - Reads user/profile data of web browsers 2 TTPs
Infostealers often target stored browser data, which can include saved credentials etc.
- Uses the VBS compiler for execution 1 TTPs
- Adds Run key to start application 2 TTPs 1 IoCs
description ioc Process Set value (str) \REGISTRY\USER\S-1-5-21-3341490333-719741536-2920803124-1000\Software\Microsoft\Windows\CurrentVersion\Run\Windows Update = "C:\\Users\\Admin\\AppData\\Roaming\\WindowsUpdate.exe" f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe - Looks up external IP address via web service 2 IoCs
Uses a legitimate IP lookup service to find the infected system's external IP.
flow ioc 7 whatismyipaddress.com 9 whatismyipaddress.com - Suspicious use of SetThreadContext 3 IoCs
description pid Process procid_target PID 1148 set thread context of 3100 1148 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 74 PID 3100 set thread context of 684 3100 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 79 PID 3100 set thread context of 2180 3100 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 81 - Suspicious behavior: EnumeratesProcesses 5 IoCs
pid Process 1148 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 1148 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 2180 vbc.exe 2180 vbc.exe 3100 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe - Suspicious behavior: MapViewOfSection 1 IoCs
pid Process 1148 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe - Suspicious use of AdjustPrivilegeToken 1 IoCs
description pid Process Token: SeDebugPrivilege 3100 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe - Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 3100 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe - Suspicious use of WriteProcessMemory 21 IoCs
description pid Process procid_target PID 1148 wrote to memory of 3100 1148 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 74 PID 1148 wrote to memory of 3100 1148 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 74 PID 1148 wrote to memory of 3100 1148 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 74 PID 3100 wrote to memory of 684 3100 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 79 PID 3100 wrote to memory of 684 3100 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 79 PID 3100 wrote to memory of 684 3100 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 79 PID 3100 wrote to memory of 684 3100 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 79 PID 3100 wrote to memory of 684 3100 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 79 PID 3100 wrote to memory of 684 3100 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 79 PID 3100 wrote to memory of 684 3100 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 79 PID 3100 wrote to memory of 684 3100 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 79 PID 3100 wrote to memory of 684 3100 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 79 PID 3100 wrote to memory of 2180 3100 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 81 PID 3100 wrote to memory of 2180 3100 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 81 PID 3100 wrote to memory of 2180 3100 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 81 PID 3100 wrote to memory of 2180 3100 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 81 PID 3100 wrote to memory of 2180 3100 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 81 PID 3100 wrote to memory of 2180 3100 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 81 PID 3100 wrote to memory of 2180 3100 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 81 PID 3100 wrote to memory of 2180 3100 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 81 PID 3100 wrote to memory of 2180 3100 f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe 81
Processes
-
C:\Users\Admin\AppData\Local\Temp\f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe"C:\Users\Admin\AppData\Local\Temp\f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious behavior: MapViewOfSection
- Suspicious use of WriteProcessMemory
PID:1148 -
C:\Users\Admin\AppData\Local\Temp\f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe"C:\Users\Admin\AppData\Local\Temp\f59f15bba5a4fe8df9441253eda4e8f85f411bdbe492d9f39f23bbf7969bacd3.exe"2⤵
- Adds Run key to start application
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3100 -
C:\Windows\Microsoft.NET\Framework\v2.0.50727\vbc.exeC:\Windows\Microsoft.NET\Framework\v2.0.50727\vbc.exe /stext "C:\Users\Admin\AppData\Local\Temp\holdermail.txt"3⤵PID:684
-
-
C:\Windows\Microsoft.NET\Framework\v2.0.50727\vbc.exeC:\Windows\Microsoft.NET\Framework\v2.0.50727\vbc.exe /stext "C:\Users\Admin\AppData\Local\Temp\holderwb.txt"3⤵
- Suspicious behavior: EnumeratesProcesses
PID:2180
-
-