Analysis
-
max time kernel
150s -
max time network
156s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
23-11-2022 19:13
Behavioral task
behavioral1
Sample
562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe
Resource
win10v2004-20221111-en
General
-
Target
562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe
-
Size
196KB
-
MD5
16d44320c7764009285aab4b5b035288
-
SHA1
9114fc10207107963196a98ba66da640c0f9a83b
-
SHA256
562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e
-
SHA512
1072931394f072e36960bccc575d8af2ea4131184d97676f4852f9256a888ddfe7243aaac48b4d0e1b1c045f2dd039d0d8503e48ee07b172da2e18c4ce793765
-
SSDEEP
3072:Dk7lSn6KYO2NeKfj6xw2V9k7lSn6KYO2NeKfj6xw2SU:DcS6hNeKfsVcS6hNeKfsn
Malware Config
Signatures
-
Processes:
resource yara_rule behavioral2/memory/5012-140-0x0000000000400000-0x0000000000433000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
Processes:
562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exedescription pid process target process PID 5012 set thread context of 4900 5012 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe -
Suspicious behavior: EnumeratesProcesses 4 IoCs
Processes:
562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exepid process 4900 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe 4900 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe 4900 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe 4900 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
Processes:
562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exepid process 5012 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe -
Suspicious use of WriteProcessMemory 11 IoCs
Processes:
562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exedescription pid process target process PID 5012 wrote to memory of 4900 5012 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe PID 5012 wrote to memory of 4900 5012 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe PID 5012 wrote to memory of 4900 5012 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe PID 5012 wrote to memory of 4900 5012 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe PID 5012 wrote to memory of 4900 5012 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe PID 5012 wrote to memory of 4900 5012 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe PID 5012 wrote to memory of 4900 5012 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe PID 4900 wrote to memory of 3080 4900 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe Explorer.EXE PID 4900 wrote to memory of 3080 4900 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe Explorer.EXE PID 4900 wrote to memory of 3080 4900 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe Explorer.EXE PID 4900 wrote to memory of 3080 4900 562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe Explorer.EXE
Processes
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵
-
C:\Users\Admin\AppData\Local\Temp\562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe"C:\Users\Admin\AppData\Local\Temp\562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe"2⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
-
C:\Users\Admin\AppData\Local\Temp\562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exeC:\Users\Admin\AppData\Local\Temp\562b8a29a2f395ab25e086470b0bb8aa0fec9efc61b3c8854cda58568f5f8a7e.exe3⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
Network
MITRE ATT&CK Matrix
Replay Monitor
Loading Replay Monitor...
Downloads
-
memory/3080-142-0x000000007FFF0000-0x000000007FFF7000-memory.dmpFilesize
28KB
-
memory/4900-137-0x0000000000000000-mapping.dmp
-
memory/4900-138-0x0000000000400000-0x0000000000409000-memory.dmpFilesize
36KB
-
memory/4900-141-0x0000000000400000-0x00000000004083A0-memory.dmpFilesize
32KB
-
memory/4900-143-0x0000000010000000-0x0000000010012000-memory.dmpFilesize
72KB
-
memory/5012-140-0x0000000000400000-0x0000000000433000-memory.dmpFilesize
204KB