Analysis
-
max time kernel
121s -
max time network
122s -
platform
windows7_x64 -
resource
win7-20231130-en -
resource tags
arch:x64arch:x86image:win7-20231130-enlocale:en-usos:windows7-x64system -
submitted
02-12-2023 07:40
Static task
static1
Behavioral task
behavioral1
Sample
126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe
Resource
win7-20231130-en
Behavioral task
behavioral2
Sample
126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe
Resource
win10v2004-20231201-en
General
-
Target
126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe
-
Size
577KB
-
MD5
009a10fd65c1d1a0381878eed34e0788
-
SHA1
b955284c838741c89f96bdc40b0f5d06ff7106ce
-
SHA256
126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db
-
SHA512
eff107b6c3f1e6e04114473186c5312252c375cda59dc30e3fa757d755c91abc90d5e16c91bc3d1c8b652744fa08cab4054a922ef020bd5253e1a4b9f9a61e78
-
SSDEEP
12288:f6copox4KSdWdblH9xrN+IW2+iaYke6G:pe5d+bl9hN+CBN1
Malware Config
Signatures
-
Snake Keylogger
Keylogger and Infostealer first seen in November 2020.
-
Snake Keylogger payload 7 IoCs
Processes:
resource yara_rule behavioral1/memory/2672-13-0x0000000000400000-0x0000000000426000-memory.dmp family_snakekeylogger behavioral1/memory/2672-15-0x0000000000400000-0x0000000000426000-memory.dmp family_snakekeylogger behavioral1/memory/2672-19-0x0000000000400000-0x0000000000426000-memory.dmp family_snakekeylogger behavioral1/memory/2672-21-0x0000000000400000-0x0000000000426000-memory.dmp family_snakekeylogger behavioral1/memory/2672-23-0x0000000000400000-0x0000000000426000-memory.dmp family_snakekeylogger behavioral1/memory/2672-26-0x00000000021E0000-0x0000000002220000-memory.dmp family_snakekeylogger behavioral1/memory/2672-28-0x00000000021E0000-0x0000000002220000-memory.dmp family_snakekeylogger -
Looks up external IP address via web service 1 IoCs
Uses a legitimate IP lookup service to find the infected system's external IP.
Processes:
flow ioc 2 checkip.dyndns.org -
Suspicious use of SetThreadContext 1 IoCs
Processes:
126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exedescription pid process target process PID 1932 set thread context of 2672 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 2596 2672 WerFault.exe 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe -
Suspicious behavior: EnumeratesProcesses 20 IoCs
Processes:
126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exepid process 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 2672 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
Processes:
126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exedescription pid process Token: SeDebugPrivilege 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe Token: SeDebugPrivilege 2672 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe -
Suspicious use of WriteProcessMemory 13 IoCs
Processes:
126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exedescription pid process target process PID 1932 wrote to memory of 2672 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe PID 1932 wrote to memory of 2672 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe PID 1932 wrote to memory of 2672 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe PID 1932 wrote to memory of 2672 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe PID 1932 wrote to memory of 2672 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe PID 1932 wrote to memory of 2672 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe PID 1932 wrote to memory of 2672 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe PID 1932 wrote to memory of 2672 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe PID 1932 wrote to memory of 2672 1932 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe PID 2672 wrote to memory of 2596 2672 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe WerFault.exe PID 2672 wrote to memory of 2596 2672 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe WerFault.exe PID 2672 wrote to memory of 2596 2672 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe WerFault.exe PID 2672 wrote to memory of 2596 2672 126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe WerFault.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe"C:\Users\Admin\AppData\Local\Temp\126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:1932 -
C:\Users\Admin\AppData\Local\Temp\126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe"C:\Users\Admin\AppData\Local\Temp\126f126044e4b0e1c30955f9ec9f1f7a72956af7ff274e7533575e11e78272db.exe"2⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:2672 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2672 -s 9723⤵
- Program crash
PID:2596