Analysis
-
max time kernel
151s -
max time network
138s -
platform
windows7_x64 -
resource
win7-20220812-en -
resource tags
arch:x64arch:x86image:win7-20220812-enlocale:en-usos:windows7-x64system -
submitted
13-10-2022 17:54
Static task
static1
Behavioral task
behavioral1
Sample
c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe
Resource
win7-20220812-en
General
-
Target
c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe
-
Size
239KB
-
MD5
6e33fdd3d5343b3cb9095dfb03a003f0
-
SHA1
a01a2e8d6dd2b3c69066a7e55c8f3374933eec4f
-
SHA256
c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f
-
SHA512
42efe24a7a22434c9717ee2d6e103e856c64399f58a66eae8dee0b264942ff2d737582319c614a7c7ef78add1e4b385d5cf590b290188b1c1b7279deb157fb24
-
SSDEEP
3072:HnFKUZojE4O+1XX/3wVwTfjgfaZozrVP4I+n6ItAw94H5oJSg1QoMn3:Qg4jx4aZ+JwOdwagPMn
Malware Config
Extracted
nanocore
-
activate_away_mode
false
- backup_connection_host
- backup_dns_server
-
buffer_size
0
-
build_time
0001-01-01T00:00:00Z
-
bypass_user_account_control
false
- bypass_user_account_control_data
-
clear_access_control
false
-
clear_zone_identifier
false
-
connect_delay
0
-
connection_port
0
- default_group
-
enable_debug_mode
false
-
gc_threshold
0
-
keep_alive_timeout
0
-
keyboard_logging
false
-
lan_timeout
0
-
max_packet_size
0
- mutex
-
mutex_timeout
0
-
prevent_system_sleep
false
- primary_connection_host
- primary_dns_server
-
request_elevation
false
-
restart_delay
0
-
run_delay
0
-
run_on_startup
false
-
set_critical_process
false
-
timeout_interval
0
-
use_custom_dns_server
false
- version
-
wan_timeout
0
Signatures
-
Processes:
c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exedescription ioc process Key value queried \REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\EnableLUA c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe -
Suspicious use of SetThreadContext 1 IoCs
Processes:
c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exedescription pid process target process PID 576 set thread context of 2036 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe -
Runs ping.exe 1 TTPs 10 IoCs
Processes:
ping.exeping.exeping.exeping.exeping.exeping.exeping.exeping.exeping.exeping.exepid process 1672 ping.exe 956 ping.exe 960 ping.exe 1068 ping.exe 948 ping.exe 1784 ping.exe 1108 ping.exe 1980 ping.exe 1756 ping.exe 1940 ping.exe -
Suspicious behavior: EnumeratesProcesses 1 IoCs
Processes:
c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exepid process 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
Processes:
c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exedescription pid process Token: SeDebugPrivilege 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe -
Suspicious use of WriteProcessMemory 49 IoCs
Processes:
c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exedescription pid process target process PID 576 wrote to memory of 2036 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe PID 576 wrote to memory of 2036 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe PID 576 wrote to memory of 2036 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe PID 576 wrote to memory of 2036 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe PID 576 wrote to memory of 2036 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe PID 576 wrote to memory of 2036 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe PID 576 wrote to memory of 2036 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe PID 576 wrote to memory of 2036 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe PID 576 wrote to memory of 2036 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe PID 576 wrote to memory of 948 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 948 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 948 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 948 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1756 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1756 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1756 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1756 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1784 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1784 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1784 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1784 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1672 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1672 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1672 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1672 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 956 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 956 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 956 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 956 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1940 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1940 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1940 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1940 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 960 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 960 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 960 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 960 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1108 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1108 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1108 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1108 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1980 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1980 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1980 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1980 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1068 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1068 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1068 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe PID 576 wrote to memory of 1068 576 c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe ping.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe"C:\Users\Admin\AppData\Local\Temp\c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:576 -
C:\Users\Admin\AppData\Local\Temp\c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe"C:\Users\Admin\AppData\Local\Temp\c4302b6122f11439c0ba321e80d67e5fa04d940f84bd738644203bd4a299f42f.exe"2⤵
- Checks whether UAC is enabled
PID:2036 -
C:\Windows\SysWOW64\ping.exeping google.com2⤵
- Runs ping.exe
PID:948 -
C:\Windows\SysWOW64\ping.exeping google.com2⤵
- Runs ping.exe
PID:1756 -
C:\Windows\SysWOW64\ping.exeping google.com2⤵
- Runs ping.exe
PID:1784 -
C:\Windows\SysWOW64\ping.exeping google.com2⤵
- Runs ping.exe
PID:1672 -
C:\Windows\SysWOW64\ping.exeping google.com2⤵
- Runs ping.exe
PID:956 -
C:\Windows\SysWOW64\ping.exeping google.com2⤵
- Runs ping.exe
PID:1940 -
C:\Windows\SysWOW64\ping.exeping google.com2⤵
- Runs ping.exe
PID:960 -
C:\Windows\SysWOW64\ping.exeping google.com2⤵
- Runs ping.exe
PID:1108 -
C:\Windows\SysWOW64\ping.exeping google.com2⤵
- Runs ping.exe
PID:1980 -
C:\Windows\SysWOW64\ping.exeping google.com2⤵
- Runs ping.exe
PID:1068