Analysis
-
max time kernel
99s -
max time network
126s -
platform
windows10-2004_x64 -
resource
win10v2004-en-20220112 -
submitted
08-03-2022 00:58
Static task
static1
Behavioral task
behavioral1
Sample
e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe
Resource
win7-20220223-en
Behavioral task
behavioral2
Sample
e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe
Resource
win10v2004-en-20220112
General
-
Target
e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe
-
Size
260KB
-
MD5
6959c253bf5fab6a54f7b9b9aeb58603
-
SHA1
7fdbf00332ed5882d774567356493fb0b369dce6
-
SHA256
e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734
-
SHA512
1b61d19314c979c551a94b490cee53c5e6d44c3d25aaab3a61ba5d99744ee440436b63798f6ebaeeecc47b38782a1c398c2aa9a58ae9f1d95a2fb7620ef05529
Malware Config
Signatures
-
NirSoft MailPassView 1 IoCs
Password recovery tool for various email clients
resource yara_rule behavioral2/memory/3704-140-0x0000000000400000-0x000000000041F000-memory.dmp MailPassView -
Nirsoft 1 IoCs
resource yara_rule behavioral2/memory/3704-140-0x0000000000400000-0x000000000041F000-memory.dmp Nirsoft -
resource yara_rule behavioral2/memory/1360-132-0x0000000000400000-0x0000000000453000-memory.dmp upx behavioral2/memory/1360-134-0x0000000000400000-0x0000000000453000-memory.dmp upx behavioral2/memory/1360-135-0x0000000000400000-0x0000000000453000-memory.dmp upx behavioral2/memory/3704-137-0x0000000000400000-0x000000000041F000-memory.dmp upx behavioral2/memory/3704-139-0x0000000000400000-0x000000000041F000-memory.dmp upx behavioral2/memory/3704-140-0x0000000000400000-0x000000000041F000-memory.dmp upx -
Reads user/profile data of web browsers 2 TTPs
Infostealers often target stored browser data, which can include saved credentials etc.
-
Accesses Microsoft Outlook accounts 1 TTPs 1 IoCs
description ioc Process Key opened \REGISTRY\USER\S-1-5-21-790714498-1549421491-1643397139-1000\Software\Microsoft\Office\Outlook\OMI Account Manager\Accounts e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe -
Suspicious use of SetThreadContext 2 IoCs
description pid Process procid_target PID 4036 set thread context of 1360 4036 e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe 56 PID 4036 set thread context of 3704 4036 e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe 65 -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 4036 e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe -
Suspicious use of WriteProcessMemory 16 IoCs
description pid Process procid_target PID 4036 wrote to memory of 1360 4036 e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe 56 PID 4036 wrote to memory of 1360 4036 e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe 56 PID 4036 wrote to memory of 1360 4036 e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe 56 PID 4036 wrote to memory of 1360 4036 e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe 56 PID 4036 wrote to memory of 1360 4036 e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe 56 PID 4036 wrote to memory of 1360 4036 e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe 56 PID 4036 wrote to memory of 1360 4036 e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe 56 PID 4036 wrote to memory of 1360 4036 e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe 56 PID 4036 wrote to memory of 3704 4036 e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe 65 PID 4036 wrote to memory of 3704 4036 e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe 65 PID 4036 wrote to memory of 3704 4036 e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe 65 PID 4036 wrote to memory of 3704 4036 e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe 65 PID 4036 wrote to memory of 3704 4036 e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe 65 PID 4036 wrote to memory of 3704 4036 e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe 65 PID 4036 wrote to memory of 3704 4036 e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe 65 PID 4036 wrote to memory of 3704 4036 e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe 65
Processes
-
C:\Users\Admin\AppData\Local\Temp\e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe"C:\Users\Admin\AppData\Local\Temp\e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4036 -
C:\Users\Admin\AppData\Local\Temp\e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe/scomma "C:\Users\Admin\AppData\Local\Temp\11LppO8x5p.ini"2⤵PID:1360
-
-
C:\Users\Admin\AppData\Local\Temp\e1ed12cde6d3b9b52ca99b7824978ecf90dd15eb717162556f1397d3f9b17734.exe/scomma "C:\Users\Admin\AppData\Local\Temp\ewqerqn7rx.ini"2⤵
- Accesses Microsoft Outlook accounts
PID:3704
-