Analysis
-
max time kernel
119s -
max time network
122s -
platform
windows7_x64 -
resource
win7-20240508-en -
resource tags
arch:x64arch:x86image:win7-20240508-enlocale:en-usos:windows7-x64system -
submitted
22-05-2024 01:58
Static task
static1
Behavioral task
behavioral1
Sample
8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe
Resource
win7-20240508-en
Behavioral task
behavioral2
Sample
8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe
Resource
win10v2004-20240426-en
General
-
Target
8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe
-
Size
1.2MB
-
MD5
7a2a3cc24199f86f3095d329335742bf
-
SHA1
115f14e5c083de1d3281fe7bb9d2f995813fd185
-
SHA256
8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2
-
SHA512
3de4a926d34953fcd9171b45670e5f4be8c933da76b630e5e0f94dbe2c3995e50859057ca48d3a3e20a08038bdcf56e4905c1fd3fd2b3f65c8cabb257c76bbee
-
SSDEEP
24576:USu1S82mBVrIiudq1WvX17XxUgbpVUxHZsPYE7C:USuU82mTV6l1UYpeHC
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exedescription pid process target process PID 2240 set thread context of 2016 2240 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 2412 2016 WerFault.exe 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe -
Suspicious behavior: EnumeratesProcesses 1 IoCs
Processes:
8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exepid process 2016 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe -
Suspicious use of WriteProcessMemory 14 IoCs
Processes:
8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exedescription pid process target process PID 2240 wrote to memory of 2016 2240 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe PID 2240 wrote to memory of 2016 2240 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe PID 2240 wrote to memory of 2016 2240 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe PID 2240 wrote to memory of 2016 2240 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe PID 2240 wrote to memory of 2016 2240 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe PID 2240 wrote to memory of 2016 2240 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe PID 2240 wrote to memory of 2016 2240 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe PID 2240 wrote to memory of 2016 2240 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe PID 2240 wrote to memory of 2016 2240 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe PID 2240 wrote to memory of 2016 2240 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe PID 2016 wrote to memory of 2412 2016 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe WerFault.exe PID 2016 wrote to memory of 2412 2016 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe WerFault.exe PID 2016 wrote to memory of 2412 2016 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe WerFault.exe PID 2016 wrote to memory of 2412 2016 8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe WerFault.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe"C:\Users\Admin\AppData\Local\Temp\8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2240 -
C:\Users\Admin\AppData\Local\Temp\8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe"C:\Users\Admin\AppData\Local\Temp\8e68d12aa3dbfabcfc25976e7c1d441121e22b3b0c06c500f03cb6af35ee4ed2.exe"2⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:2016 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2016 -s 363⤵
- Program crash
PID:2412