Analysis
- max time kernel
134s - max time network
147s - platform
windows10_x64 - resource
win10v20201028 - submitted
11/11/2020, 11:42
Static task
static1
Behavioral task
behavioral1
Sample
0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe
Resource
win7v20201028
0 signatures
0 seconds
General
- Target 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe
- Size 1.1MB
- Sample201111-9hr55dmahe
- SHA256 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8
- MD5 f00ae271782ebffdb9248b0277ed7fdb
- SHA1 efbf5ddbfa8565d159f58d330b1aad03727ba8c0
- SHA512 03b71686beec5bd9ae5a8f0330e2b0c234466de02715b7d2bbefa68576b68f30bae22aedf512a44f8134073ab951a44586f9115bc9bd3ea985d42075d5d204b7
- MD5 SHA1 SHA512
Malware Config
Extracted
Credentials
-
Protocol
smtp
-
Host
smtp.casalsmd.com
-
Port
587
-
Username
-
Password
Carolina123
Signatures
-
resource yara_rule behavioral2/memory/720-1-0x0000000000400000-0x000000000051D000-memory.dmp upx behavioral2/memory/720-3-0x0000000000400000-0x000000000051D000-memory.dmp upx behavioral2/memory/720-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-1985363256-3005190890-1182679451-1000\Software\Microsoft\Windows\CurrentVersion\Run\Windows Update = "C:\\Users\\Admin\\AppData\\Roaming\\WindowsUpdate.exe" 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.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 11 whatismyipaddress.com 13 whatismyipaddress.com - Suspicious use of SetThreadContext 3 IoCs
description pid Process procid_target PID 428 set thread context of 720 428 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 76 PID 720 set thread context of 3352 720 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 77 PID 720 set thread context of 2136 720 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 81 - Suspicious behavior: EnumeratesProcesses 5 IoCs
pid Process 428 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 428 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 2136 vbc.exe 2136 vbc.exe 720 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe - Suspicious behavior: MapViewOfSection 1 IoCs
pid Process 428 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe - Suspicious use of AdjustPrivilegeToken 1 IoCs
description pid Process Token: SeDebugPrivilege 720 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe - Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 720 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe - Suspicious use of WriteProcessMemory 21 IoCs
description pid Process procid_target PID 428 wrote to memory of 720 428 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 76 PID 428 wrote to memory of 720 428 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 76 PID 428 wrote to memory of 720 428 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 76 PID 720 wrote to memory of 3352 720 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 77 PID 720 wrote to memory of 3352 720 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 77 PID 720 wrote to memory of 3352 720 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 77 PID 720 wrote to memory of 3352 720 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 77 PID 720 wrote to memory of 3352 720 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 77 PID 720 wrote to memory of 3352 720 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 77 PID 720 wrote to memory of 3352 720 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 77 PID 720 wrote to memory of 3352 720 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 77 PID 720 wrote to memory of 3352 720 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 77 PID 720 wrote to memory of 2136 720 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 81 PID 720 wrote to memory of 2136 720 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 81 PID 720 wrote to memory of 2136 720 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 81 PID 720 wrote to memory of 2136 720 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 81 PID 720 wrote to memory of 2136 720 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 81 PID 720 wrote to memory of 2136 720 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 81 PID 720 wrote to memory of 2136 720 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 81 PID 720 wrote to memory of 2136 720 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 81 PID 720 wrote to memory of 2136 720 0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe 81
Processes
-
C:\Users\Admin\AppData\Local\Temp\0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe"C:\Users\Admin\AppData\Local\Temp\0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious behavior: MapViewOfSection
- Suspicious use of WriteProcessMemory
PID:428 -
C:\Users\Admin\AppData\Local\Temp\0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.exe"C:\Users\Admin\AppData\Local\Temp\0d5ff709cd566b8f8a2f26b6038306b664c7431d8bddbd90982b399b04d169e8.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:720 -
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:3352
-
-
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:2136
-
-