Analysis
-
max time kernel
125s -
max time network
128s -
platform
windows10-2004_x64 -
resource
win10v2004-20220414-en -
submitted
20/04/2022, 02:10
Static task
static1
Behavioral task
behavioral1
Sample
f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe
Resource
win7-20220414-en
Behavioral task
behavioral2
Sample
f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe
Resource
win10v2004-20220414-en
General
-
Target
f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe
-
Size
818KB
-
MD5
72159f6de42ef2d65fee42a31bbbfcee
-
SHA1
0fa0a3ec1f1772cba492316866f578c5db09adbd
-
SHA256
f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b
-
SHA512
5daea2a9995b9330cd17a2c4676c6aa8eacf18f15f54919b406fdccc1bcbfc74f24ac3656c24dc33734db7e62a022448b767e626ca7faa6a31a4026b29852534
Malware Config
Signatures
-
MassLogger
Masslogger is a .NET stealer targeting passwords from browsers, email and cryptocurrency clients.
-
MassLogger Main Payload 1 IoCs
resource yara_rule behavioral2/memory/2328-138-0x0000000000400000-0x0000000000486000-memory.dmp family_masslogger -
Looks for VirtualBox Guest Additions in registry 2 TTPs
-
Looks for VMWare Tools registry key 2 TTPs
-
Checks BIOS information in registry 2 TTPs 2 IoCs
BIOS information is often read in order to detect sandboxing environments.
description ioc Process Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\SystemBiosVersion f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\VideoBiosVersion f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe -
Maps connected drives based on registry 3 TTPs 2 IoCs
Disk information is often read in order to detect sandboxing environments.
description ioc Process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\Disk\Enum f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\disk\Enum\0 f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2424 set thread context of 2328 2424 f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe 81 -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 2328 f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe 2328 f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe 3676 powershell.exe 3676 powershell.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeDebugPrivilege 2328 f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe Token: SeDebugPrivilege 3676 powershell.exe -
Suspicious use of WriteProcessMemory 11 IoCs
description pid Process procid_target PID 2424 wrote to memory of 2328 2424 f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe 81 PID 2424 wrote to memory of 2328 2424 f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe 81 PID 2424 wrote to memory of 2328 2424 f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe 81 PID 2424 wrote to memory of 2328 2424 f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe 81 PID 2424 wrote to memory of 2328 2424 f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe 81 PID 2424 wrote to memory of 2328 2424 f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe 81 PID 2424 wrote to memory of 2328 2424 f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe 81 PID 2424 wrote to memory of 2328 2424 f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe 81 PID 2328 wrote to memory of 3676 2328 f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe 82 PID 2328 wrote to memory of 3676 2328 f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe 82 PID 2328 wrote to memory of 3676 2328 f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe 82
Processes
-
C:\Users\Admin\AppData\Local\Temp\f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe"C:\Users\Admin\AppData\Local\Temp\f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe"1⤵
- Checks BIOS information in registry
- Maps connected drives based on registry
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2424 -
C:\Users\Admin\AppData\Local\Temp\f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe"{path}"2⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:2328 -
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe"powershell" Start-Sleep -Seconds 2; Remove-Item -path 'C:\Users\Admin\AppData\Local\Temp\f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe'3⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
PID:3676
-
-
Network
MITRE ATT&CK Enterprise v6
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\f850f8dbc4d481d6fe6357e4ecc67d2a576542a63c3ff3561b55905fa5e0786b.exe.log
Filesize1KB
MD5ddde88120da5a6e61cf1c0d1fc3f5c99
SHA1aef94de11f90c3e6a99478c03d24aa355a6d0e52
SHA256353067996dbacb8d3ae38dcc754d06b92e34b8511ebe2fda8c2358bbf6b79924
SHA51264994ad92b4751bf3d580ec683e9387d9f05fe44bcb80c343470e992ac793f94f4811ab7c4f2e7240d40d5fe49df8191b781ef994a7c30df1f80940c7b06e8bd