Analysis
-
max time kernel
137s -
max time network
94s -
platform
windows7_x64 -
resource
win7v200430 -
submitted
24-06-2020 14:56
Static task
static1
Behavioral task
behavioral1
Sample
f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe
Resource
win7v200430
Behavioral task
behavioral2
Sample
f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe
Resource
win10
General
-
Target
f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe
-
Size
321KB
-
MD5
967a32731bbb80347c2f17a1f3d630e3
-
SHA1
a3260961fb13ca51180cfaca64c3702655b93e89
-
SHA256
f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d
-
SHA512
85da7652ed22dcaa06d0432f0a0c5e7376b5dce29bd28347e4e7f94343260541698b1ebc4090abaf84e16934a26ae7193db8cd1da2eb3847b67f3801b8b384c2
Malware Config
Signatures
-
404 Keylogger
Information stealer and keylogger first seen in 2019.
-
404 Keylogger Main Executable 7 IoCs
Processes:
resource yara_rule behavioral1/memory/1752-5-0x0000000000400000-0x0000000000422000-memory.dmp family_404keylogger behavioral1/memory/1752-5-0x0000000000400000-0x0000000000422000-memory.dmp family_404keylogger behavioral1/memory/1752-6-0x000000000041CB6E-mapping.dmp family_404keylogger behavioral1/memory/1752-7-0x0000000000400000-0x0000000000422000-memory.dmp family_404keylogger behavioral1/memory/1752-7-0x0000000000400000-0x0000000000422000-memory.dmp family_404keylogger behavioral1/memory/1752-8-0x0000000000400000-0x0000000000422000-memory.dmp family_404keylogger behavioral1/memory/1752-8-0x0000000000400000-0x0000000000422000-memory.dmp family_404keylogger -
Reads data files stored by FTP clients 2 TTPs
Tries to access configuration files associated with programs like FileZilla.
-
Reads user/profile data of local email clients 2 TTPs
Email clients store some user data on disk where infostealers will often target it.
-
Reads user/profile data of web browsers 2 TTPs
Infostealers often target stored browser data, which can include saved credentials etc.
-
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 4 checkip.dyndns.org -
Suspicious use of SetThreadContext 1 IoCs
Processes:
f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exedescription pid process target process PID 240 set thread context of 1752 240 f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe -
Creates scheduled task(s) 1 TTPs 1 IoCs
Schtasks is often used by malware for persistence or to perform post-infection execution.
-
Suspicious behavior: EnumeratesProcesses 3 IoCs
Processes:
f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exef2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exepid process 240 f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe 240 f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe 1752 f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
Processes:
f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exef2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exedescription pid process Token: SeDebugPrivilege 240 f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe Token: SeDebugPrivilege 1752 f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
Processes:
f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exepid process 1752 f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe -
Suspicious use of WriteProcessMemory 17 IoCs
Processes:
f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exedescription pid process target process PID 240 wrote to memory of 1864 240 f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe schtasks.exe PID 240 wrote to memory of 1864 240 f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe schtasks.exe PID 240 wrote to memory of 1864 240 f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe schtasks.exe PID 240 wrote to memory of 1864 240 f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe schtasks.exe PID 240 wrote to memory of 1764 240 f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe PID 240 wrote to memory of 1764 240 f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe PID 240 wrote to memory of 1764 240 f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe PID 240 wrote to memory of 1764 240 f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe PID 240 wrote to memory of 1752 240 f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe PID 240 wrote to memory of 1752 240 f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe PID 240 wrote to memory of 1752 240 f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe PID 240 wrote to memory of 1752 240 f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe PID 240 wrote to memory of 1752 240 f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe PID 240 wrote to memory of 1752 240 f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe PID 240 wrote to memory of 1752 240 f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe PID 240 wrote to memory of 1752 240 f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe PID 240 wrote to memory of 1752 240 f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe"C:\Users\Admin\AppData\Local\Temp\f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:240 -
C:\Windows\SysWOW64\schtasks.exe"C:\Windows\System32\schtasks.exe" /Create /TN "Updates\QfsWgvANVJrOqG" /XML "C:\Users\Admin\AppData\Local\Temp\tmp2D85.tmp"2⤵
- Creates scheduled task(s)
PID:1864
-
-
C:\Users\Admin\AppData\Local\Temp\f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe"{path}"2⤵PID:1764
-
-
C:\Users\Admin\AppData\Local\Temp\f2adad4441d13ec7c7bc39f25f5606b1b8a64f08b80d6646c97d36e1932c598d.exe"{path}"2⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
PID:1752
-