Analysis
- max time kernel
157s - max time network
161s - platform
windows10-2004_x64 - resource
win10v2004-en-20220113 - submitted
26/03/2022, 14:56
Static task
static1
Behavioral task
behavioral1
Sample
b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe
Resource
win7-20220311-en
0 signatures
0 seconds
Behavioral task
behavioral2
Sample
b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe
Resource
win10v2004-en-20220113
0 signatures
0 seconds
General
- Target b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe
- Size 2.0MB
- Sample220326-sa2nmsead7
- SHA256 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673
- MD5 bb1d4c1dc1504a8b8d43cc4f5ba24a12
- SHA1 c7b26cd57552a8413f0d09f65ed04cb3a7f2029a
- SHA512 385d2414233263b672aff3f086f2fe328316e442a4bebedf76fd81f6a41b446b0862678c8f65d066af2bca234ef1b7f19039640a0a141922eef9e5a88605d262
- MD5 SHA1 SHA512
Score
10/10
Malware Config
Extracted
Family
-
bitrat
Version
-
1.32
C2
-
2.56.213.183:1234
Attributes
-
communication_password
81dc9bdb52d04dc20036dbd8313ed055
-
install_dir
jabber
-
install_file
jabber.exe
-
tor_process
tor
Signatures
- Adds Run key to start application 2 TTPs 2 IoCs
description ioc Process Set value (str) \REGISTRY\USER\S-1-5-21-1346565761-3498240568-4147300184-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\jabber = "C:\\Users\\Admin\\AppData\\Local\\jabber\\jabber.exe" b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe Set value (str) \REGISTRY\USER\S-1-5-21-1346565761-3498240568-4147300184-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\jabber = "C:\\Users\\Admin\\AppData\\Local\\jabber\\jabber.exeЀ" b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe - Suspicious use of NtSetInformationThreadHideFromDebugger 4 IoCs
pid Process 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe - Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3144 set thread context of 4296 3144 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 80 - Suspicious behavior: EnumeratesProcesses 2 IoCs
pid Process 3144 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 3144 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe - Suspicious behavior: RenamesItself 29 IoCs
pid Process 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe - Suspicious use of AdjustPrivilegeToken 3 IoCs
description pid Process Token: SeDebugPrivilege 3144 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe Token: SeDebugPrivilege 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe Token: SeShutdownPrivilege 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe - Suspicious use of SetWindowsHookEx 2 IoCs
pid Process 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 4296 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe - Suspicious use of WriteProcessMemory 13 IoCs
description pid Process procid_target PID 3144 wrote to memory of 4172 3144 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 79 PID 3144 wrote to memory of 4172 3144 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 79 PID 3144 wrote to memory of 4172 3144 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 79 PID 3144 wrote to memory of 4296 3144 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 80 PID 3144 wrote to memory of 4296 3144 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 80 PID 3144 wrote to memory of 4296 3144 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 80 PID 3144 wrote to memory of 4296 3144 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 80 PID 3144 wrote to memory of 4296 3144 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 80 PID 3144 wrote to memory of 4296 3144 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 80 PID 3144 wrote to memory of 4296 3144 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 80 PID 3144 wrote to memory of 4296 3144 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 80 PID 3144 wrote to memory of 4296 3144 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 80 PID 3144 wrote to memory of 4296 3144 b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe 80
Processes
-
C:\Users\Admin\AppData\Local\Temp\b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe"C:\Users\Admin\AppData\Local\Temp\b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:3144 -
C:\Users\Admin\AppData\Local\Temp\b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe"C:\Users\Admin\AppData\Local\Temp\b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe"2⤵PID:4172
-
-
C:\Users\Admin\AppData\Local\Temp\b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe"C:\Users\Admin\AppData\Local\Temp\b7494a4405860081e00232c5f8eb497bfdda3eb4e45e85276ed4eca369f08673.exe"2⤵
- Adds Run key to start application
- Suspicious use of NtSetInformationThreadHideFromDebugger
- Suspicious behavior: RenamesItself
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
PID:4296
-