Analysis
-
max time kernel
133s -
max time network
166s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
24-11-2022 18:05
Static task
static1
Behavioral task
behavioral1
Sample
e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe
Resource
win10v2004-20220812-en
General
-
Target
e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe
-
Size
101KB
-
MD5
fafc6f295096ba82efd30c487e3da22f
-
SHA1
b2ec6ced1ef9ced7b24edf8248f3801fe7a10d2a
-
SHA256
e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d
-
SHA512
d57c9e6b26d9c8c6d97877ec14757db2ae83879ec01144f03c862f720ab31ede2634933bf8d5b24dc831643c3db9f545ad217d3f3dd7d8812f15910027edfac0
-
SSDEEP
1536:+3PzsBqymiNodrRppqBBRK6xkkfqXS7247HnGyd75qnnk86YSzA6Y/Y+2KARNDas:+3rsQypNoG4X147HGyV5j867KODZ
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:
e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exedescription ioc process Set value (str) \REGISTRY\MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Run\aaaaaaaa = "C:\\Windows\\System32\\aaaaaaaa.exe" e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe Set value (str) \REGISTRY\USER\S-1-5-21-2295526160-1155304984-640977766-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\aaaaaaaa = "C:\\Users\\Admin\\aaaaaaaa.exe" e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe -
Drops file in System32 directory 1 IoCs
Processes:
e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exedescription ioc process File created C:\Windows\SysWOW64\aaaaaaaa.exe e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe -
Suspicious use of SetThreadContext 2 IoCs
Processes:
e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exee025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exedescription pid process target process PID 704 set thread context of 4080 704 e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe PID 4080 set thread context of 3256 4080 e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.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 opened \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0 svchost.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\Identifier 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:
e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exepid process 704 e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe 704 e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe 704 e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe 704 e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe -
Suspicious use of WriteProcessMemory 16 IoCs
Processes:
e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exee025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exedescription pid process target process PID 704 wrote to memory of 4080 704 e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe PID 704 wrote to memory of 4080 704 e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe PID 704 wrote to memory of 4080 704 e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe PID 704 wrote to memory of 4080 704 e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe PID 704 wrote to memory of 4080 704 e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe PID 704 wrote to memory of 4080 704 e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe PID 704 wrote to memory of 4080 704 e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe PID 704 wrote to memory of 4080 704 e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe PID 4080 wrote to memory of 3256 4080 e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe svchost.exe PID 4080 wrote to memory of 3256 4080 e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe svchost.exe PID 4080 wrote to memory of 3256 4080 e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe svchost.exe PID 4080 wrote to memory of 3256 4080 e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe svchost.exe PID 4080 wrote to memory of 3256 4080 e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe svchost.exe PID 4080 wrote to memory of 3256 4080 e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe svchost.exe PID 4080 wrote to memory of 3256 4080 e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe svchost.exe PID 4080 wrote to memory of 3256 4080 e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe svchost.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe"C:\Users\Admin\AppData\Local\Temp\e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
-
C:\Users\Admin\AppData\Local\Temp\e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.exe"C:\Users\Admin\AppData\Local\Temp\e025910fa48113e7329a435993656dbd6186db777ac554f9e7469277e17f3f5d.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/704-138-0x00000000005B0000-0x00000000005B5000-memory.dmpFilesize
20KB
-
memory/3256-136-0x0000000000000000-mapping.dmp
-
memory/3256-137-0x0000000009500000-0x0000000009508000-memory.dmpFilesize
32KB
-
memory/3256-141-0x0000000009500000-0x0000000009508000-memory.dmpFilesize
32KB
-
memory/3256-142-0x0000000009500000-0x0000000009508000-memory.dmpFilesize
32KB
-
memory/4080-132-0x0000000000000000-mapping.dmp
-
memory/4080-133-0x0000000013100000-0x000000001310A000-memory.dmpFilesize
40KB
-
memory/4080-135-0x0000000013100000-0x000000001310A000-memory.dmpFilesize
40KB
-
memory/4080-139-0x0000000013100000-0x000000001310A000-memory.dmpFilesize
40KB