Analysis
-
max time kernel
138s -
max time network
149s -
platform
windows10-2004_x64 -
resource
win10v2004-20220901-en -
resource tags
arch:x64arch:x86image:win10v2004-20220901-enlocale:en-usos:windows10-2004-x64system -
submitted
25-11-2022 15:33
Static task
static1
Behavioral task
behavioral1
Sample
b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe
Resource
win10v2004-20220901-en
General
-
Target
b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe
-
Size
178KB
-
MD5
37486e8286684ec19f8967b257d2ccf6
-
SHA1
b80b9703783f74253c9c87081ce630f6b84e40ba
-
SHA256
b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59
-
SHA512
bda33e80ced874c0281cdfc658214a5d0ccb1f1247876b0da3afdd6f6c3664300d9939a36698df093f5c1bd2d6fd5ffbbd4a73b888c9fdb43cc87f6a42b1ea81
-
SSDEEP
3072:lm1FRLpe2ltbhH5CiB4MhWXsL2RKvSBdAXy:cvRNe2ltCQhWXsGKkf
Malware Config
Signatures
-
Checks BIOS information in registry 2 TTPs 1 IoCs
BIOS information is often read in order to detect sandboxing environments.
Processes:
svchost.exedescription ioc process Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\SystemBiosdate svchost.exe -
Adds Run key to start application 2 TTPs 2 IoCs
Processes:
b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exedescription ioc process Set value (str) \REGISTRY\MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Run\aaaaaaaa = "C:\\Windows\\System32\\aaaaaaaa.exe" b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe Set value (str) \REGISTRY\USER\S-1-5-21-929662420-1054238289-2961194603-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\aaaaaaaa = "C:\\Users\\Admin\\aaaaaaaa.exe" b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe -
Drops file in System32 directory 1 IoCs
Processes:
b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exedescription ioc process File created C:\Windows\SysWOW64\aaaaaaaa.exe b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe -
Suspicious use of SetThreadContext 2 IoCs
Processes:
b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exeb2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exedescription pid process target process PID 4640 set thread context of 1560 4640 b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe PID 1560 set thread context of 1852 1560 b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe svchost.exe -
Checks processor information in registry 2 TTPs 2 IoCs
Processor information is often read in order to detect sandboxing environments.
Processes:
svchost.exedescription ioc process Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\Identifier svchost.exe Key opened \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0 svchost.exe -
Enumerates system info in registry 2 TTPs 1 IoCs
Processes:
svchost.exedescription ioc process Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\VideoBiosDate svchost.exe -
Suspicious behavior: EnumeratesProcesses 4 IoCs
Processes:
b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exepid process 4640 b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe 4640 b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe 4640 b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe 4640 b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe -
Suspicious use of WriteProcessMemory 16 IoCs
Processes:
b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exeb2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exedescription pid process target process PID 4640 wrote to memory of 1560 4640 b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe PID 4640 wrote to memory of 1560 4640 b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe PID 4640 wrote to memory of 1560 4640 b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe PID 4640 wrote to memory of 1560 4640 b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe PID 4640 wrote to memory of 1560 4640 b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe PID 4640 wrote to memory of 1560 4640 b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe PID 4640 wrote to memory of 1560 4640 b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe PID 4640 wrote to memory of 1560 4640 b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe PID 1560 wrote to memory of 1852 1560 b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe svchost.exe PID 1560 wrote to memory of 1852 1560 b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe svchost.exe PID 1560 wrote to memory of 1852 1560 b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe svchost.exe PID 1560 wrote to memory of 1852 1560 b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe svchost.exe PID 1560 wrote to memory of 1852 1560 b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe svchost.exe PID 1560 wrote to memory of 1852 1560 b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe svchost.exe PID 1560 wrote to memory of 1852 1560 b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe svchost.exe PID 1560 wrote to memory of 1852 1560 b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe svchost.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe"C:\Users\Admin\AppData\Local\Temp\b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
-
C:\Users\Admin\AppData\Local\Temp\b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe"C:\Users\Admin\AppData\Local\Temp\b2216689bc98c78464ecd32132fbeb267084fdbbdef5c23ce06bc35b18564a59.exe"2⤵
- Adds Run key to start application
- Drops file in System32 directory
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
-
C:\Windows\SysWOW64\svchost.exeC:\Windows\System32\svchost.exe3⤵
- Checks BIOS information in registry
- Checks processor information in registry
- Enumerates system info in registry
Network
MITRE ATT&CK Matrix ATT&CK v6
Replay Monitor
Loading Replay Monitor...
Downloads
-
memory/1560-132-0x0000000000000000-mapping.dmp
-
memory/1560-133-0x0000000013100000-0x000000001310A000-memory.dmpFilesize
40KB
-
memory/1560-136-0x0000000013100000-0x000000001310A000-memory.dmpFilesize
40KB
-
memory/1560-139-0x0000000013100000-0x000000001310A000-memory.dmpFilesize
40KB
-
memory/1852-138-0x0000000009500000-0x0000000009508000-memory.dmpFilesize
32KB
-
memory/1852-137-0x0000000000000000-mapping.dmp
-
memory/1852-141-0x0000000009500000-0x0000000009508000-memory.dmpFilesize
32KB
-
memory/1852-142-0x0000000009500000-0x0000000009508000-memory.dmpFilesize
32KB
-
memory/4640-134-0x00000000005B0000-0x00000000005B5000-memory.dmpFilesize
20KB