Analysis
-
max time kernel
12s -
max time network
34s -
platform
windows7_x64 -
resource
win7-20221111-en -
resource tags
arch:x64arch:x86image:win7-20221111-enlocale:en-usos:windows7-x64system -
submitted
23-11-2022 18:49
Static task
static1
Behavioral task
behavioral1
Sample
d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe
Resource
win10v2004-20221111-en
General
-
Target
d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe
-
Size
134KB
-
MD5
5c9886c5640c5e125e6640314db6d216
-
SHA1
b5ecf8c1bfcc8550644b3fe78ff07a344f95ec1c
-
SHA256
d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473
-
SHA512
a16d5d68f8cdc726cdb4d77cbb0a3ec41bd8b51aedb06c206cab3eae904fd321323085cc7f65afee354fb8f9d0615e87830cb2f2a61ba3b62058560a9ce2e8df
-
SSDEEP
3072:ncw9JIpFWgCcw2OPdZm+UyidxE9oVjB1jz4oUSod2oewM:RJIpFWgCP/Pb2ymxQK/lSgp
Malware Config
Signatures
-
Modifies WinLogon for persistence 2 TTPs 1 IoCs
Processes:
d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exedescription ioc process Set value (str) \REGISTRY\MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell = "explorer.exe ,C:\\Users\\Admin\\AppData\\Local\\Temp\\d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe" d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe -
Disables use of System Restore points 1 TTPs
-
Processes:
resource yara_rule behavioral1/memory/1528-57-0x0000000000400000-0x0000000000427000-memory.dmp upx behavioral1/memory/1528-60-0x0000000000400000-0x0000000000427000-memory.dmp upx behavioral1/memory/1528-61-0x0000000000400000-0x0000000000427000-memory.dmp upx behavioral1/memory/1528-65-0x0000000000400000-0x0000000000427000-memory.dmp upx behavioral1/memory/1528-71-0x0000000000400000-0x0000000000427000-memory.dmp upx -
Suspicious use of SetThreadContext 2 IoCs
Processes:
d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exed83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exedescription pid process target process PID 1792 set thread context of 1528 1792 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe PID 1528 set thread context of 1924 1528 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe -
Suspicious behavior: EnumeratesProcesses 2 IoCs
Processes:
d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exepid process 1924 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe 1924 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe -
Suspicious use of SetWindowsHookEx 2 IoCs
Processes:
d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exed83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exepid process 1792 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe 1528 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe -
Suspicious use of WriteProcessMemory 21 IoCs
Processes:
d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exed83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exed83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exedescription pid process target process PID 1792 wrote to memory of 1528 1792 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe PID 1792 wrote to memory of 1528 1792 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe PID 1792 wrote to memory of 1528 1792 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe PID 1792 wrote to memory of 1528 1792 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe PID 1792 wrote to memory of 1528 1792 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe PID 1792 wrote to memory of 1528 1792 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe PID 1792 wrote to memory of 1528 1792 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe PID 1792 wrote to memory of 1528 1792 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe PID 1792 wrote to memory of 1528 1792 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe PID 1528 wrote to memory of 1924 1528 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe PID 1528 wrote to memory of 1924 1528 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe PID 1528 wrote to memory of 1924 1528 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe PID 1528 wrote to memory of 1924 1528 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe PID 1528 wrote to memory of 1924 1528 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe PID 1528 wrote to memory of 1924 1528 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe PID 1528 wrote to memory of 1924 1528 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe PID 1528 wrote to memory of 1924 1528 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe PID 1924 wrote to memory of 1228 1924 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe Explorer.EXE PID 1924 wrote to memory of 1228 1924 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe Explorer.EXE PID 1924 wrote to memory of 1228 1924 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe Explorer.EXE PID 1924 wrote to memory of 1228 1924 d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe Explorer.EXE
Processes
-
C:\Users\Admin\AppData\Local\Temp\d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe"C:\Users\Admin\AppData\Local\Temp\d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1792 -
C:\Users\Admin\AppData\Local\Temp\d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe"C:\Users\Admin\AppData\Local\Temp\d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe"2⤵
- Modifies WinLogon for persistence
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1528 -
C:\Users\Admin\AppData\Local\Temp\d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe"C:\Users\Admin\AppData\Local\Temp\d83275ce64fbca91202817bcc2cb23031484f7f13627277d84e5761e9ff0b473.exe"3⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:1924
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:1228