Analysis
-
max time kernel
149s -
max time network
124s -
platform
windows7_x64 -
resource
win7-20240221-en -
resource tags
arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system -
submitted
22-05-2024 13:58
Behavioral task
behavioral1
Sample
4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe
Resource
win7-20240221-en
Behavioral task
behavioral2
Sample
4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe
Resource
win10v2004-20240508-en
General
-
Target
4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe
-
Size
3.5MB
-
MD5
764fb6348921a9d3d33b6b6185b634e1
-
SHA1
f2a76ea9089a4e3a6a38410c2c44397fd5f1599b
-
SHA256
4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895
-
SHA512
3f98d24939493a9ea0066e38eb795ef4a4df985babe67405c07817675b4b280b879f6e1694337163cc17c2556cd00a70ccb77c1c2275631a001f8ba6e152ad27
-
SSDEEP
98304:UCKgfgVvJ5foXQ5c3Jm16HzpuEk4fzP3dfa:UCKgOvJ5foAO0tOb1fa
Malware Config
Signatures
-
MetaSploit
Detected malicious payload which is part of the Metasploit Framework, likely generated with msfvenom or similar.
-
Suspicious behavior: EnumeratesProcesses 64 IoCs
Processes:
4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exewinlogon.exepid process 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 424 winlogon.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
Processes:
4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exewinlogon.exedescription pid process Token: SeDebugPrivilege 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe Token: SeDebugPrivilege 424 winlogon.exe -
Suspicious use of FindShellTrayWindow 2 IoCs
Processes:
4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exepid process 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe -
Suspicious use of SendNotifyMessage 1 IoCs
Processes:
4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exepid process 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
Processes:
4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exepid process 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe -
Suspicious use of WriteProcessMemory 1 IoCs
Processes:
4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exedescription pid process target process PID 1704 wrote to memory of 424 1704 4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe winlogon.exe
Processes
-
C:\Windows\system32\winlogon.exewinlogon.exe1⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
-
C:\Users\Admin\AppData\Local\Temp\4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe"C:\Users\Admin\AppData\Local\Temp\4c7b0ce20ddaf84679851e350ec83ecc2604adf5edcd976e823c79f08b49d895.exe"1⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of FindShellTrayWindow
- Suspicious use of SendNotifyMessage
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
Network
MITRE ATT&CK Matrix
Replay Monitor
Loading Replay Monitor...
Downloads
-
memory/424-3-0x0000000180000000-0x0000000180119000-memory.dmpFilesize
1.1MB
-
memory/424-2-0x0000000000B20000-0x0000000000BB4000-memory.dmpFilesize
592KB
-
memory/424-1-0x0000000000B20000-0x0000000000BB4000-memory.dmpFilesize
592KB
-
memory/424-14-0x0000000180000000-0x0000000180119000-memory.dmpFilesize
1.1MB
-
memory/424-9-0x0000000180000000-0x0000000180119000-memory.dmpFilesize
1.1MB
-
memory/1704-12-0x0000000000910000-0x0000000000911000-memory.dmpFilesize
4KB
-
memory/1704-0-0x0000000000400000-0x0000000000910000-memory.dmpFilesize
5.1MB
-
memory/1704-11-0x00000000003F0000-0x00000000003F1000-memory.dmpFilesize
4KB
-
memory/1704-13-0x0000000000920000-0x0000000000921000-memory.dmpFilesize
4KB
-
memory/1704-17-0x0000000000400000-0x0000000000910000-memory.dmpFilesize
5.1MB
-
memory/1704-20-0x0000000000920000-0x0000000000921000-memory.dmpFilesize
4KB
-
memory/1704-19-0x0000000000910000-0x0000000000911000-memory.dmpFilesize
4KB
-
memory/1704-18-0x00000000003F0000-0x00000000003F1000-memory.dmpFilesize
4KB