Analysis
-
max time kernel
150s -
max time network
152s -
platform
windows10-2004_x64 -
resource
win10v2004-20230220-en -
resource tags
arch:x64arch:x86image:win10v2004-20230220-enlocale:en-usos:windows10-2004-x64system -
submitted
28/03/2023, 09:44
Static task
static1
Behavioral task
behavioral1
Sample
4c5068ae1dc37622834d2e84dd827040d0aeed3aac17560bf731ec79f5793037.exe
Resource
win10v2004-20230220-en
General
-
Target
4c5068ae1dc37622834d2e84dd827040d0aeed3aac17560bf731ec79f5793037.exe
-
Size
269KB
-
MD5
74db21999e569840b49b51d5bd28bc7f
-
SHA1
2a50cb2b7a96d75177a0d064254e57d5f0f0ce7b
-
SHA256
4c5068ae1dc37622834d2e84dd827040d0aeed3aac17560bf731ec79f5793037
-
SHA512
05cae2f2532911c4a1252b4f2363d322e5f97567c407464e350d93f6cdec1d9c86a775608ac53587b737a098cee04bec3f1047b2dba9fae77737b66d592541e7
-
SSDEEP
3072:2rRDQ9fQD0uqhKFeP+XS/sG8XrHCk3fUCnlb6iY0mDyLYSPfjmyhyolmSZ:wWQfkKW/s3S/oYi
Malware Config
Extracted
smokeloader
lab
Extracted
smokeloader
2020
http://host-file-host6.com/
http://host-host-file8.com/
Signatures
-
SmokeLoader
Modular backdoor trojan in use since 2014.
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1664 set thread context of 5040 1664 4c5068ae1dc37622834d2e84dd827040d0aeed3aac17560bf731ec79f5793037.exe 83 -
Checks SCSI registry key(s) 3 TTPs 3 IoCs
SCSI information is often read in order to detect sandboxing environments.
description ioc Process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI 4c5068ae1dc37622834d2e84dd827040d0aeed3aac17560bf731ec79f5793037.exe Key queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI 4c5068ae1dc37622834d2e84dd827040d0aeed3aac17560bf731ec79f5793037.exe Key enumerated \REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\SCSI 4c5068ae1dc37622834d2e84dd827040d0aeed3aac17560bf731ec79f5793037.exe -
Suspicious behavior: EnumeratesProcesses 64 IoCs
pid Process 5040 4c5068ae1dc37622834d2e84dd827040d0aeed3aac17560bf731ec79f5793037.exe 5040 4c5068ae1dc37622834d2e84dd827040d0aeed3aac17560bf731ec79f5793037.exe 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found 2680 Process not Found -
Suspicious behavior: GetForegroundWindowSpam 1 IoCs
pid Process 2680 Process not Found -
Suspicious behavior: MapViewOfSection 1 IoCs
pid Process 5040 4c5068ae1dc37622834d2e84dd827040d0aeed3aac17560bf731ec79f5793037.exe -
Suspicious use of WriteProcessMemory 6 IoCs
description pid Process procid_target PID 1664 wrote to memory of 5040 1664 4c5068ae1dc37622834d2e84dd827040d0aeed3aac17560bf731ec79f5793037.exe 83 PID 1664 wrote to memory of 5040 1664 4c5068ae1dc37622834d2e84dd827040d0aeed3aac17560bf731ec79f5793037.exe 83 PID 1664 wrote to memory of 5040 1664 4c5068ae1dc37622834d2e84dd827040d0aeed3aac17560bf731ec79f5793037.exe 83 PID 1664 wrote to memory of 5040 1664 4c5068ae1dc37622834d2e84dd827040d0aeed3aac17560bf731ec79f5793037.exe 83 PID 1664 wrote to memory of 5040 1664 4c5068ae1dc37622834d2e84dd827040d0aeed3aac17560bf731ec79f5793037.exe 83 PID 1664 wrote to memory of 5040 1664 4c5068ae1dc37622834d2e84dd827040d0aeed3aac17560bf731ec79f5793037.exe 83 -
Uses Task Scheduler COM API 1 TTPs
The Task Scheduler COM API can be used to schedule applications to run on boot or at set times.
Processes
-
C:\Users\Admin\AppData\Local\Temp\4c5068ae1dc37622834d2e84dd827040d0aeed3aac17560bf731ec79f5793037.exe"C:\Users\Admin\AppData\Local\Temp\4c5068ae1dc37622834d2e84dd827040d0aeed3aac17560bf731ec79f5793037.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1664 -
C:\Users\Admin\AppData\Local\Temp\4c5068ae1dc37622834d2e84dd827040d0aeed3aac17560bf731ec79f5793037.exe"C:\Users\Admin\AppData\Local\Temp\4c5068ae1dc37622834d2e84dd827040d0aeed3aac17560bf731ec79f5793037.exe"2⤵
- Checks SCSI registry key(s)
- Suspicious behavior: EnumeratesProcesses
- Suspicious behavior: MapViewOfSection
PID:5040
-