Analysis
-
max time kernel
14s -
max time network
33s -
platform
windows7_x64 -
resource
win7-20221111-en -
resource tags
arch:x64arch:x86image:win7-20221111-enlocale:en-usos:windows7-x64system -
submitted
06/12/2022, 13:04
Behavioral task
behavioral1
Sample
f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe
Resource
win7-20221111-en
windows7-x64
4 signatures
150 seconds
Behavioral task
behavioral2
Sample
f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe
Resource
win10v2004-20221111-en
windows10-2004-x64
4 signatures
150 seconds
General
-
Target
f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe
-
Size
428KB
-
MD5
de166e4001cc3b02fcc17c7c3eea2c1e
-
SHA1
884c29e5e8bbf30574444933c3bcffc31eeef3d4
-
SHA256
f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8
-
SHA512
a6201181f1f3d845126f9fad77b288c75e36213940933e70584b267c98aec4463b29f15699c3ed29eed20c05090e3481ec956b211ea7345d4ed109831f64589a
-
SSDEEP
3072:FOHR5+GXqxdXMTUplBTAn7vIiiR8m8af8fE4Y1QcdD4DAhnGlgndY+cWbI5LIkw8:FRLChgndY+c6mB
Score
8/10
Malware Config
Signatures
-
resource yara_rule behavioral1/memory/1640-61-0x0000000000400000-0x000000000046D000-memory.dmp upx behavioral1/memory/1640-67-0x0000000000400000-0x000000000046D000-memory.dmp upx -
Suspicious use of SetThreadContext 6 IoCs
description pid Process procid_target PID 1640 set thread context of 1736 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe 28 PID 1640 set thread context of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe PID 1640 set thread context of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe PID 1640 set thread context of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe PID 1640 set thread context of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe PID 1640 set thread context of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe -
Suspicious use of WriteProcessMemory 28 IoCs
description pid Process procid_target PID 1640 wrote to memory of 1736 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe 28 PID 1640 wrote to memory of 1736 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe 28 PID 1640 wrote to memory of 1736 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe 28 PID 1640 wrote to memory of 1736 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe 28 PID 1640 wrote to memory of 1736 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe 28 PID 1640 wrote to memory of 1736 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe 28 PID 1640 wrote to memory of 1736 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe 28 PID 1640 wrote to memory of 1736 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe 28 PID 1640 wrote to memory of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe PID 1640 wrote to memory of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe PID 1640 wrote to memory of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe PID 1640 wrote to memory of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe PID 1640 wrote to memory of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe PID 1640 wrote to memory of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe PID 1640 wrote to memory of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe PID 1640 wrote to memory of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe PID 1640 wrote to memory of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe PID 1640 wrote to memory of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe PID 1640 wrote to memory of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe PID 1640 wrote to memory of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe PID 1640 wrote to memory of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe PID 1640 wrote to memory of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe PID 1640 wrote to memory of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe PID 1640 wrote to memory of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe PID 1640 wrote to memory of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe PID 1640 wrote to memory of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe PID 1640 wrote to memory of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe PID 1640 wrote to memory of 0 1640 f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe"C:\Users\Admin\AppData\Local\Temp\f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1640 -
C:\Users\Admin\AppData\Local\Temp\f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe"C:\Users\Admin\AppData\Local\Temp\f798bdf94a531eb8afc373342dc0c3a6b845d5900d1a9169865237dcd5a442a8.exe"2⤵PID:1736
-