Analysis
-
max time kernel
151s -
max time network
140s -
platform
windows7_x64 -
resource
win7-en-20211208 -
submitted
21-01-2022 23:48
Static task
static1
Behavioral task
behavioral1
Sample
5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe
Resource
win7-en-20211208
Behavioral task
behavioral2
Sample
5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe
Resource
win10-en-20211208
General
-
Target
5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe
-
Size
2.1MB
-
MD5
9bf79297f1cb4d4558df34df6543629c
-
SHA1
93773632d065436990bec5c67cf06bd552149dd7
-
SHA256
5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68
-
SHA512
16113979fde18e5556ab2dfaa12febda59928816109d50649232ee89045260bbd0a91a0917a93e70aee1e9cc52ab54388ae3b2a1f514aba401fa475f694e57f6
Malware Config
Extracted
bitrat
1.38
jairoandresotalvarorend.linkpc.net:9086
-
communication_password
bfdba24ee3d61f0260c4dc1034c3ee43
-
install_dir
windowsdefenderinitservices
-
install_file
windowsdefenderinitservice.exe
-
tor_process
tor
Signatures
-
Processes:
resource yara_rule behavioral1/memory/464-61-0x0000000000400000-0x00000000007E4000-memory.dmp upx behavioral1/memory/464-62-0x0000000000400000-0x00000000007E4000-memory.dmp upx behavioral1/memory/464-63-0x0000000000400000-0x00000000007E4000-memory.dmp upx behavioral1/memory/464-64-0x0000000000400000-0x00000000007E4000-memory.dmp upx behavioral1/memory/464-66-0x0000000000400000-0x00000000007E4000-memory.dmp upx -
Adds Run key to start application 2 TTPs 1 IoCs
Processes:
5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exedescription ioc process Set value (str) \REGISTRY\USER\S-1-5-21-3846991908-3261386348-1409841751-1000\Software\Microsoft\Windows\CurrentVersion\Run\windowsdefenderinitservice = "C:\\Users\\Admin\\AppData\\Local\\windowsdefenderinitservices\\windowsdefenderinitservice.exe" 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe -
Suspicious use of NtSetInformationThreadHideFromDebugger 4 IoCs
Processes:
5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exepid process 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe -
Suspicious use of SetThreadContext 1 IoCs
Processes:
5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exedescription pid process target process PID 868 set thread context of 464 868 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe -
Suspicious behavior: RenamesItself 17 IoCs
Processes:
5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exepid process 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
Processes:
5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exedescription pid process Token: SeDebugPrivilege 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe Token: SeShutdownPrivilege 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe -
Suspicious use of SetWindowsHookEx 2 IoCs
Processes:
5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exepid process 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 464 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe -
Suspicious use of WriteProcessMemory 8 IoCs
Processes:
5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exedescription pid process target process PID 868 wrote to memory of 464 868 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe PID 868 wrote to memory of 464 868 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe PID 868 wrote to memory of 464 868 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe PID 868 wrote to memory of 464 868 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe PID 868 wrote to memory of 464 868 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe PID 868 wrote to memory of 464 868 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe PID 868 wrote to memory of 464 868 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe PID 868 wrote to memory of 464 868 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe 5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe"C:\Users\Admin\AppData\Local\Temp\5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
-
C:\Users\Admin\AppData\Local\Temp\5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe"C:\Users\Admin\AppData\Local\Temp\5cada311c0db4a8fe87a377b82f4ba9f686953ae98b59dd493d66da8927d9e68.exe"2⤵
- Adds Run key to start application
- Suspicious use of NtSetInformationThreadHideFromDebugger
- Suspicious behavior: RenamesItself
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
Network
MITRE ATT&CK Matrix ATT&CK v6
Replay Monitor
Loading Replay Monitor...
Downloads
-
memory/464-63-0x0000000000400000-0x00000000007E4000-memory.dmpFilesize
3.9MB
-
memory/464-60-0x0000000000400000-0x00000000007E4000-memory.dmpFilesize
3.9MB
-
memory/464-61-0x0000000000400000-0x00000000007E4000-memory.dmpFilesize
3.9MB
-
memory/464-62-0x0000000000400000-0x00000000007E4000-memory.dmpFilesize
3.9MB
-
memory/464-64-0x0000000000400000-0x00000000007E4000-memory.dmpFilesize
3.9MB
-
memory/464-66-0x0000000000400000-0x00000000007E4000-memory.dmpFilesize
3.9MB
-
memory/464-67-0x0000000000401000-0x00000000007E4000-memory.dmpFilesize
3.9MB
-
memory/868-55-0x0000000075761000-0x0000000075763000-memory.dmpFilesize
8KB
-
memory/868-56-0x0000000004F10000-0x0000000004F11000-memory.dmpFilesize
4KB
-
memory/868-57-0x0000000000300000-0x0000000000322000-memory.dmpFilesize
136KB
-
memory/868-58-0x0000000008690000-0x0000000008856000-memory.dmpFilesize
1.8MB
-
memory/868-59-0x0000000008850000-0x00000000089CE000-memory.dmpFilesize
1.5MB
-
memory/868-54-0x0000000001170000-0x000000000139A000-memory.dmpFilesize
2.2MB