Analysis
-
max time kernel
42s -
max time network
47s -
platform
windows7_x64 -
resource
win7-20220901-en -
resource tags
arch:x64arch:x86image:win7-20220901-enlocale:en-usos:windows7-x64system -
submitted
24-11-2022 09:02
Static task
static1
Behavioral task
behavioral1
Sample
3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe
Resource
win7-20220901-en
Behavioral task
behavioral2
Sample
3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe
Resource
win10v2004-20221111-en
General
-
Target
3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe
-
Size
470KB
-
MD5
17098ec6304ab82894d4921a319e26f4
-
SHA1
f46f62d4e0d066fae37e24b7afb24fbeab704205
-
SHA256
3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822
-
SHA512
34bb005574a357e4d1e91b6dcec22f9c98d7b3c4a47e463a47d2708e8a43ee996c8f71de74bacb337b27ba1e18f5fd94927cef3317381adefba8e6e50ee9a1f9
-
SSDEEP
12288:Fn1jdB0YqAxghPO6X0NYOZvpiUDr+dIFTy9gT6Y:Fn1jIYDIPjkGOmUDr+KFTy9gT6Y
Malware Config
Extracted
fickerstealer
alogsme.link:8080
Signatures
-
Fickerstealer
Ficker is an infostealer written in Rust and ASM.
-
Reads local data of messenger clients 2 TTPs
Infostealers often target stored data of messaging applications, which can include saved credentials and account information.
-
Reads user/profile data of web browsers 2 TTPs
Infostealers often target stored browser data, which can include saved credentials etc.
-
Accesses cryptocurrency files/wallets, possible credential harvesting 2 TTPs
-
Checks installed software on the system 1 TTPs
Looks up Uninstall key entries in the registry to enumerate software on the system.
-
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 3 api.ipify.org -
Suspicious use of SetThreadContext 1 IoCs
Processes:
3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exedescription pid Process procid_target PID 1760 set thread context of 1332 1760 3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe 27 -
Checks processor information in registry 2 TTPs 2 IoCs
Processor information is often read in order to detect sandboxing environments.
Processes:
3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exedescription ioc Process Key opened \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0 3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\ProcessorNameString 3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe -
Suspicious behavior: EnumeratesProcesses 1 IoCs
Processes:
3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exepid Process 1332 3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe -
Suspicious use of WriteProcessMemory 14 IoCs
Processes:
3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exedescription pid Process procid_target PID 1760 wrote to memory of 1332 1760 3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe 27 PID 1760 wrote to memory of 1332 1760 3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe 27 PID 1760 wrote to memory of 1332 1760 3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe 27 PID 1760 wrote to memory of 1332 1760 3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe 27 PID 1760 wrote to memory of 1332 1760 3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe 27 PID 1760 wrote to memory of 1332 1760 3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe 27 PID 1760 wrote to memory of 1332 1760 3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe 27 PID 1760 wrote to memory of 1332 1760 3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe 27 PID 1760 wrote to memory of 1332 1760 3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe 27 PID 1760 wrote to memory of 1332 1760 3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe 27 PID 1760 wrote to memory of 1332 1760 3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe 27 PID 1760 wrote to memory of 1332 1760 3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe 27 PID 1760 wrote to memory of 1332 1760 3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe 27 PID 1760 wrote to memory of 1332 1760 3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe 27
Processes
-
C:\Users\Admin\AppData\Local\Temp\3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe"C:\Users\Admin\AppData\Local\Temp\3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1760 -
C:\Users\Admin\AppData\Local\Temp\3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe"C:\Users\Admin\AppData\Local\Temp\3e455eb86a62a185bb0c5446df337d6823c71b743f7ee16d3e2ee643c476d822.exe"2⤵
- Checks processor information in registry
- Suspicious behavior: EnumeratesProcesses
PID:1332
-