Analysis
- max time kernel
136s - max time network
148s - platform
windows10_x64 - resource
win10v20201028 - submitted
09/11/2020, 20:49
Static task
static1
Behavioral task
behavioral1
Sample
48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe
Resource
win7v20201028
0 signatures
0 seconds
General
- Target 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe
- Size 938KB
- Sample201109-467peqtkcs
- SHA256 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb
- MD5 b5f175e433dadf0aa860e725e97772bf
- SHA1 253630762dd8b05d021c103600de3e578b6b7ff9
- SHA512 ddf8d44f65e139ca33f93e707b18b8f23f9efda5f7470b9f2e8f1ef16b6f3d9121634354c8eaf220107d7f8ee33621c7932260c16035d147f447b164415e6fc3
- MD5 SHA1 SHA512
Malware Config
Signatures
- Identifies VirtualBox via ACPI registry values (likely anti-VM) 2 TTPs
-
resource yara_rule behavioral2/memory/216-4-0x0000000000C80000-0x0000000000C96000-memory.dmp upx behavioral2/memory/216-6-0x0000000000C80000-0x0000000000C96000-memory.dmp upx behavioral2/memory/216-7-0x0000000000C80000-0x0000000000C96000-memory.dmp upx behavioral2/memory/1508-8-0x0000000000C80000-0x0000000000C96000-memory.dmp upx - Drops startup file 2 IoCs
description ioc Process File created C:\Users\Admin\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\WindowsDefender.exe 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe File opened for modification C:\Users\Admin\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\WindowsDefender.exe 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe - Identifies Wine through registry keys 2 TTPs 1 IoCs
Wine is a compatibility layer capable of running Windows applications, which can be used as sandboxing environment.
description ioc Process Key opened \REGISTRY\USER\S-1-5-21-3341490333-719741536-2920803124-1000\Software\Wine 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe - Suspicious use of NtSetInformationThreadHideFromDebugger 1 IoCs
pid Process 3408 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe - Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3408 set thread context of 216 3408 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe 76 - Suspicious behavior: EnumeratesProcesses 2 IoCs
pid Process 3408 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe 3408 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe - Suspicious use of SetWindowsHookEx 2 IoCs
pid Process 3408 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe 1508 calc.exe - Suspicious use of WriteProcessMemory 18 IoCs
description pid Process procid_target PID 3408 wrote to memory of 216 3408 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe 76 PID 3408 wrote to memory of 216 3408 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe 76 PID 3408 wrote to memory of 216 3408 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe 76 PID 3408 wrote to memory of 216 3408 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe 76 PID 3408 wrote to memory of 216 3408 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe 76 PID 3408 wrote to memory of 216 3408 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe 76 PID 3408 wrote to memory of 216 3408 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe 76 PID 3408 wrote to memory of 216 3408 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe 76 PID 216 wrote to memory of 1952 216 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe 77 PID 216 wrote to memory of 1952 216 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe 77 PID 216 wrote to memory of 1952 216 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe 77 PID 216 wrote to memory of 3288 216 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe 78 PID 216 wrote to memory of 3288 216 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe 78 PID 216 wrote to memory of 3288 216 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe 78 PID 216 wrote to memory of 1508 216 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe 79 PID 216 wrote to memory of 1508 216 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe 79 PID 216 wrote to memory of 1508 216 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe 79 PID 216 wrote to memory of 1508 216 48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe 79
Processes
-
C:\Users\Admin\AppData\Local\Temp\48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe"C:\Users\Admin\AppData\Local\Temp\48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe"1⤵
- Drops startup file
- Identifies Wine through registry keys
- Suspicious use of NtSetInformationThreadHideFromDebugger
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3408 -
C:\Users\Admin\AppData\Local\Temp\48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe"C:\Users\Admin\AppData\Local\Temp\48236bb4fa38724fb0a368673e14c364fde3fa5e95ba42db44a0193ba4c13beb.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:216 -
C:\Windows\SysWOW64\calc.execalc.exe3⤵PID:1952
-
-
C:\Windows\SysWOW64\calc.execalc.exe3⤵PID:3288
-
-
C:\Windows\SysWOW64\calc.execalc.exe3⤵
- Suspicious use of SetWindowsHookEx
PID:1508
-
-