Analysis
-
max time kernel
196s -
max time network
208s -
platform
windows10-2004_x64 -
resource
win10v2004-20220414-en -
submitted
01-07-2022 05:42
Static task
static1
Behavioral task
behavioral1
Sample
25040c35d20171f24a057fa11719af5fe9d65333a5ada111af8ff45e17df5934.exe
Resource
win7-20220414-en
Behavioral task
behavioral2
Sample
25040c35d20171f24a057fa11719af5fe9d65333a5ada111af8ff45e17df5934.exe
Resource
win10v2004-20220414-en
General
-
Target
25040c35d20171f24a057fa11719af5fe9d65333a5ada111af8ff45e17df5934.exe
-
Size
1.4MB
-
MD5
bcf252bdff29159c7c15233718df745d
-
SHA1
20a382a1290377255239782dbb107c552c33f3e8
-
SHA256
25040c35d20171f24a057fa11719af5fe9d65333a5ada111af8ff45e17df5934
-
SHA512
b36ae019a56236370d0ad583a7cd4912f3fca49b3fdb6461f718ed5c9912f68410671573daa6ceec500f4754fcc3379f26057742b9675b4b8907287d483b6d46
Malware Config
Signatures
-
404 Keylogger
Information stealer and keylogger first seen in 2019.
-
404 Keylogger Main Executable 1 IoCs
Processes:
resource yara_rule behavioral2/memory/3872-133-0x0000000000400000-0x0000000000422000-memory.dmp family_404keylogger -
Suspicious use of SetThreadContext 1 IoCs
Processes:
25040c35d20171f24a057fa11719af5fe9d65333a5ada111af8ff45e17df5934.exedescription pid process target process PID 4116 set thread context of 3872 4116 25040c35d20171f24a057fa11719af5fe9d65333a5ada111af8ff45e17df5934.exe MSBuild.exe -
Drops file in Windows directory 1 IoCs
Processes:
MSBuild.exedescription ioc process File opened for modification C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe MSBuild.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 4748 3872 WerFault.exe MSBuild.exe -
Suspicious behavior: MapViewOfSection 1 IoCs
Processes:
25040c35d20171f24a057fa11719af5fe9d65333a5ada111af8ff45e17df5934.exepid process 4116 25040c35d20171f24a057fa11719af5fe9d65333a5ada111af8ff45e17df5934.exe -
Suspicious use of FindShellTrayWindow 3 IoCs
Processes:
25040c35d20171f24a057fa11719af5fe9d65333a5ada111af8ff45e17df5934.exepid process 4116 25040c35d20171f24a057fa11719af5fe9d65333a5ada111af8ff45e17df5934.exe 4116 25040c35d20171f24a057fa11719af5fe9d65333a5ada111af8ff45e17df5934.exe 4116 25040c35d20171f24a057fa11719af5fe9d65333a5ada111af8ff45e17df5934.exe -
Suspicious use of SendNotifyMessage 3 IoCs
Processes:
25040c35d20171f24a057fa11719af5fe9d65333a5ada111af8ff45e17df5934.exepid process 4116 25040c35d20171f24a057fa11719af5fe9d65333a5ada111af8ff45e17df5934.exe 4116 25040c35d20171f24a057fa11719af5fe9d65333a5ada111af8ff45e17df5934.exe 4116 25040c35d20171f24a057fa11719af5fe9d65333a5ada111af8ff45e17df5934.exe -
Suspicious use of WriteProcessMemory 4 IoCs
Processes:
25040c35d20171f24a057fa11719af5fe9d65333a5ada111af8ff45e17df5934.exedescription pid process target process PID 4116 wrote to memory of 3872 4116 25040c35d20171f24a057fa11719af5fe9d65333a5ada111af8ff45e17df5934.exe MSBuild.exe PID 4116 wrote to memory of 3872 4116 25040c35d20171f24a057fa11719af5fe9d65333a5ada111af8ff45e17df5934.exe MSBuild.exe PID 4116 wrote to memory of 3872 4116 25040c35d20171f24a057fa11719af5fe9d65333a5ada111af8ff45e17df5934.exe MSBuild.exe PID 4116 wrote to memory of 3872 4116 25040c35d20171f24a057fa11719af5fe9d65333a5ada111af8ff45e17df5934.exe MSBuild.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\25040c35d20171f24a057fa11719af5fe9d65333a5ada111af8ff45e17df5934.exe"C:\Users\Admin\AppData\Local\Temp\25040c35d20171f24a057fa11719af5fe9d65333a5ada111af8ff45e17df5934.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious behavior: MapViewOfSection
- Suspicious use of FindShellTrayWindow
- Suspicious use of SendNotifyMessage
- Suspicious use of WriteProcessMemory
PID:4116 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe"C:\\\\Windows\\\\Microsoft.NET\\\\Framework\\\\v4.0.30319\\\\MSBuild.exe"2⤵
- Drops file in Windows directory
PID:3872 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3872 -s 7963⤵
- Program crash
PID:4748
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 200 -p 3872 -ip 38721⤵PID:4664