smokeloader | 75edb521bbb0ae12b7c2c52fa6e3ed769f4e764e26b92ef2dc4d7cb78ed92fd9

Analysis

max time kernel
118s
max time network
120s
platform
windows7_x64
resource
win7-20240508-en
resource tags

arch:x64arch:x86image:win7-20240508-enlocale:en-usos:windows7-x64system
submitted
23-05-2024 18:30

Sharing

Copy URL

Twitter E-mail

Report Analysis Logs

General

Target

0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe
Size

270KB
MD5

7eeca2cbaccbd7eb357bfa4f623fbf97
SHA1

67c43af2316b5b307922d952a0e48680b8270802
SHA256

0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2
SHA512

e986d779f9bc7de5c627e487ad3fa87921b2b404a25e2eec6cb85d2e7cac73660c354e0ebcb134a03fb809e8054f2f20538160343f53c315f620a8f5cbf5f401
SSDEEP

3072:VJGkimM7usspGahWcy23rT1YCj2AFnKFCWWCMLfCpBJqs6uRtNeAg0FujCn8odDh:PapK3RlYo26KFCW8m3JqxAOO8+SVT

Score

10^/10

smokeloader backdoor trojan

Malware Config

Signatures

SmokeLoader
Modular backdoor trojan in use since 2014.
trojan backdoor smokeloader

Suspicious use of SetThreadContext 1 IoCs

description	pid	Process	procid_target
PID 1712 set thread context of 2980	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	66

Program crash 1 IoCs

pid	pid_target	Process	procid_target
1884	1712	WerFault.exe	27

Suspicious use of WriteProcessMemory 64 IoCs

description	pid	Process	procid_target
PID 1712 wrote to memory of 1808	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	28
PID 1712 wrote to memory of 1808	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	28
PID 1712 wrote to memory of 1808	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	28
PID 1712 wrote to memory of 1808	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	28
PID 1712 wrote to memory of 1808	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	28
PID 1712 wrote to memory of 1808	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	28
PID 1712 wrote to memory of 1808	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	28
PID 1712 wrote to memory of 2472	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	29
PID 1712 wrote to memory of 2472	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	29
PID 1712 wrote to memory of 2472	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	29
PID 1712 wrote to memory of 2472	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	29
PID 1712 wrote to memory of 2472	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	29
PID 1712 wrote to memory of 2472	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	29
PID 1712 wrote to memory of 2472	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	29
PID 1712 wrote to memory of 2216	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	30
PID 1712 wrote to memory of 2216	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	30
PID 1712 wrote to memory of 2216	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	30
PID 1712 wrote to memory of 2216	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	30
PID 1712 wrote to memory of 2216	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	30
PID 1712 wrote to memory of 2216	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	30
PID 1712 wrote to memory of 2216	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	30
PID 1712 wrote to memory of 2904	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	31
PID 1712 wrote to memory of 2904	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	31
PID 1712 wrote to memory of 2904	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	31
PID 1712 wrote to memory of 2904	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	31
PID 1712 wrote to memory of 2904	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	31
PID 1712 wrote to memory of 2904	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	31
PID 1712 wrote to memory of 2904	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	31
PID 1712 wrote to memory of 1328	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	32
PID 1712 wrote to memory of 1328	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	32
PID 1712 wrote to memory of 1328	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	32
PID 1712 wrote to memory of 1328	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	32
PID 1712 wrote to memory of 1328	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	32
PID 1712 wrote to memory of 1328	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	32
PID 1712 wrote to memory of 1328	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	32
PID 1712 wrote to memory of 2600	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	33
PID 1712 wrote to memory of 2600	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	33
PID 1712 wrote to memory of 2600	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	33
PID 1712 wrote to memory of 2600	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	33
PID 1712 wrote to memory of 2600	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	33
PID 1712 wrote to memory of 2600	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	33
PID 1712 wrote to memory of 2600	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	33
PID 1712 wrote to memory of 2428	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	34
PID 1712 wrote to memory of 2428	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	34
PID 1712 wrote to memory of 2428	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	34
PID 1712 wrote to memory of 2428	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	34
PID 1712 wrote to memory of 2428	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	34
PID 1712 wrote to memory of 2428	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	34
PID 1712 wrote to memory of 2428	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	34
PID 1712 wrote to memory of 2860	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	35
PID 1712 wrote to memory of 2860	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	35
PID 1712 wrote to memory of 2860	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	35
PID 1712 wrote to memory of 2860	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	35
PID 1712 wrote to memory of 2860	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	35
PID 1712 wrote to memory of 2860	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	35
PID 1712 wrote to memory of 2860	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	35
PID 1712 wrote to memory of 3020	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	36
PID 1712 wrote to memory of 3020	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	36
PID 1712 wrote to memory of 3020	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	36
PID 1712 wrote to memory of 3020	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	36
PID 1712 wrote to memory of 3020	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	36
PID 1712 wrote to memory of 3020	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	36
PID 1712 wrote to memory of 3020	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	36
PID 1712 wrote to memory of 3036	1712	0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe	37

C:\Users\Admin\AppData\Local\Temp\0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe
"C:\Users\Admin\AppData\Local\Temp\0fd60696a37853b9112e009b88f4a66eb9d6f837b4b77cfe28e58110267409b2.exe"
1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1712
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:1808
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2472
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2216
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2904
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:1328
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2600
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2428
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2860
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:3020
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:3036
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2612
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:3032
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:860
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:3044
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2624
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2664
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2668
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2812
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2800
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2792
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2828
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2908
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2672
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2840
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2528
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2656
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2576
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2780
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2524
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2532
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2540
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2564
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2584
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2596
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:1696
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2976
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2972
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2164
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2980
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 1712 -s 452
  2⤵
  - Program crash
  PID:1884

Network

MITRE ATT&CK Matrix

Replay Monitor

Loading Replay Monitor...

Downloads

memory/2980-0-0x0000000000400000-0x0000000000409000-memory.dmp

Filesize
36KB

Download
memory/2980-4-0x0000000000400000-0x0000000000409000-memory.dmp

Filesize
36KB

Download
memory/2980-3-0x00000000FFFDE000-0x00000000FFFDF000-memory.dmp

Filesize
4KB

Download
memory/2980-2-0x0000000000400000-0x0000000000409000-memory.dmp

Filesize
36KB

Download

Analysis

Sharing

General

Malware Config

Signatures

Processes

Network

MITRE ATT&CK Matrix

Replay Monitor

Loading Replay Monitor...

Downloads