Analysis
-
max time kernel
195s -
max time network
256s -
platform
windows10-1703_x64 -
resource
win10-20240404-en -
resource tags
arch:x64arch:x86image:win10-20240404-enlocale:en-usos:windows10-1703-x64system -
submitted
04-07-2024 22:46
Static task
static1
Behavioral task
behavioral1
Sample
cf2ef8eaab958f358b6f1adaaa60c1e94f3817e8a57cccd8b988af007fa8a57d.exe
Resource
win7-20240419-en
General
-
Target
cf2ef8eaab958f358b6f1adaaa60c1e94f3817e8a57cccd8b988af007fa8a57d.exe
-
Size
507KB
-
MD5
0f9b8c6500c040df8aee110cac74225a
-
SHA1
51892cdff9f9afa873c096e372053f669792bb70
-
SHA256
cf2ef8eaab958f358b6f1adaaa60c1e94f3817e8a57cccd8b988af007fa8a57d
-
SHA512
651a7e9580880ba8ece3d345555f0765ed3ded259d88dd40501ccde326bebc01128c1d3653cda721c7fec3f7091781feb43c7be29ac54d1c1070caae4bd71fa9
-
SSDEEP
12288:KLo2tQgRiP9bu1ircdlgkXfzYJvNrXWoaVS4SZn:ikOiRzQdRuNLWoaVS4S
Malware Config
Extracted
lumma
https://bitchsafettyudjwu.shop/api
Signatures
-
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.
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
cf2ef8eaab958f358b6f1adaaa60c1e94f3817e8a57cccd8b988af007fa8a57d.exedescription pid process target process PID 2796 set thread context of 2284 2796 cf2ef8eaab958f358b6f1adaaa60c1e94f3817e8a57cccd8b988af007fa8a57d.exe RegAsm.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 4748 2796 WerFault.exe cf2ef8eaab958f358b6f1adaaa60c1e94f3817e8a57cccd8b988af007fa8a57d.exe -
Suspicious behavior: EnumeratesProcesses 4 IoCs
Processes:
RegAsm.exepid process 2284 RegAsm.exe 2284 RegAsm.exe 2284 RegAsm.exe 2284 RegAsm.exe -
Suspicious use of WriteProcessMemory 12 IoCs
Processes:
cf2ef8eaab958f358b6f1adaaa60c1e94f3817e8a57cccd8b988af007fa8a57d.exedescription pid process target process PID 2796 wrote to memory of 1076 2796 cf2ef8eaab958f358b6f1adaaa60c1e94f3817e8a57cccd8b988af007fa8a57d.exe RegAsm.exe PID 2796 wrote to memory of 1076 2796 cf2ef8eaab958f358b6f1adaaa60c1e94f3817e8a57cccd8b988af007fa8a57d.exe RegAsm.exe PID 2796 wrote to memory of 1076 2796 cf2ef8eaab958f358b6f1adaaa60c1e94f3817e8a57cccd8b988af007fa8a57d.exe RegAsm.exe PID 2796 wrote to memory of 2284 2796 cf2ef8eaab958f358b6f1adaaa60c1e94f3817e8a57cccd8b988af007fa8a57d.exe RegAsm.exe PID 2796 wrote to memory of 2284 2796 cf2ef8eaab958f358b6f1adaaa60c1e94f3817e8a57cccd8b988af007fa8a57d.exe RegAsm.exe PID 2796 wrote to memory of 2284 2796 cf2ef8eaab958f358b6f1adaaa60c1e94f3817e8a57cccd8b988af007fa8a57d.exe RegAsm.exe PID 2796 wrote to memory of 2284 2796 cf2ef8eaab958f358b6f1adaaa60c1e94f3817e8a57cccd8b988af007fa8a57d.exe RegAsm.exe PID 2796 wrote to memory of 2284 2796 cf2ef8eaab958f358b6f1adaaa60c1e94f3817e8a57cccd8b988af007fa8a57d.exe RegAsm.exe PID 2796 wrote to memory of 2284 2796 cf2ef8eaab958f358b6f1adaaa60c1e94f3817e8a57cccd8b988af007fa8a57d.exe RegAsm.exe PID 2796 wrote to memory of 2284 2796 cf2ef8eaab958f358b6f1adaaa60c1e94f3817e8a57cccd8b988af007fa8a57d.exe RegAsm.exe PID 2796 wrote to memory of 2284 2796 cf2ef8eaab958f358b6f1adaaa60c1e94f3817e8a57cccd8b988af007fa8a57d.exe RegAsm.exe PID 2796 wrote to memory of 2284 2796 cf2ef8eaab958f358b6f1adaaa60c1e94f3817e8a57cccd8b988af007fa8a57d.exe RegAsm.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\cf2ef8eaab958f358b6f1adaaa60c1e94f3817e8a57cccd8b988af007fa8a57d.exe"C:\Users\Admin\AppData\Local\Temp\cf2ef8eaab958f358b6f1adaaa60c1e94f3817e8a57cccd8b988af007fa8a57d.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2796 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:1076
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵
- Suspicious behavior: EnumeratesProcesses
PID:2284 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2796 -s 3242⤵
- Program crash
PID:4748