Analysis
-
max time kernel
116s -
max time network
127s -
platform
windows10-2004_x64 -
resource
win10v2004-20220901-en -
resource tags
arch:x64arch:x86image:win10v2004-20220901-enlocale:en-usos:windows10-2004-x64system -
submitted
31/10/2022, 22:56
Static task
static1
Behavioral task
behavioral1
Sample
108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7.exe
Resource
win10v2004-20220901-en
General
-
Target
108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7.exe
-
Size
322KB
-
MD5
cb4b8ce7c6b3fdecfb11f9ee650f7178
-
SHA1
72d43e6de17cdca67d5dbe14ac33f56b44972e2d
-
SHA256
108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7
-
SHA512
afe3ac38963a29fff69447e96bdb8ad861f704e84ac24eb6a1579f17ac57bdb24a50218bfb079b3a0d4126a5f1b10257f67772e1f4974c1a62a7edc2d30db7f1
-
SSDEEP
6144:eKlzr1sYCzek2ciDaP9Xk6Ln1W8W/9InBSkZZmLdGcAdgdY6RKpjS:eGhQ2ciDq9ZL1W8q9InBRqELdolRKpj
Malware Config
Signatures
-
Executes dropped EXE 4 IoCs
pid Process 1796 oobeldr.exe 1000 oobeldr.exe 2776 oobeldr.exe 3080 oobeldr.exe -
Suspicious use of SetThreadContext 3 IoCs
description pid Process procid_target PID 4996 set thread context of 1476 4996 108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7.exe 86 PID 1796 set thread context of 1000 1796 oobeldr.exe 94 PID 2776 set thread context of 3080 2776 oobeldr.exe 98 -
Creates scheduled task(s) 1 TTPs 2 IoCs
Schtasks is often used by malware for persistence or to perform post-infection execution.
pid Process 3488 schtasks.exe 3716 schtasks.exe -
Suspicious use of WriteProcessMemory 36 IoCs
description pid Process procid_target PID 4996 wrote to memory of 4092 4996 108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7.exe 82 PID 4996 wrote to memory of 4092 4996 108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7.exe 82 PID 4996 wrote to memory of 4092 4996 108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7.exe 82 PID 4996 wrote to memory of 1476 4996 108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7.exe 86 PID 4996 wrote to memory of 1476 4996 108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7.exe 86 PID 4996 wrote to memory of 1476 4996 108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7.exe 86 PID 4996 wrote to memory of 1476 4996 108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7.exe 86 PID 4996 wrote to memory of 1476 4996 108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7.exe 86 PID 4996 wrote to memory of 1476 4996 108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7.exe 86 PID 4996 wrote to memory of 1476 4996 108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7.exe 86 PID 4996 wrote to memory of 1476 4996 108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7.exe 86 PID 4996 wrote to memory of 1476 4996 108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7.exe 86 PID 1476 wrote to memory of 3488 1476 108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7.exe 88 PID 1476 wrote to memory of 3488 1476 108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7.exe 88 PID 1476 wrote to memory of 3488 1476 108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7.exe 88 PID 1796 wrote to memory of 1000 1796 oobeldr.exe 94 PID 1796 wrote to memory of 1000 1796 oobeldr.exe 94 PID 1796 wrote to memory of 1000 1796 oobeldr.exe 94 PID 1796 wrote to memory of 1000 1796 oobeldr.exe 94 PID 1796 wrote to memory of 1000 1796 oobeldr.exe 94 PID 1796 wrote to memory of 1000 1796 oobeldr.exe 94 PID 1796 wrote to memory of 1000 1796 oobeldr.exe 94 PID 1796 wrote to memory of 1000 1796 oobeldr.exe 94 PID 1796 wrote to memory of 1000 1796 oobeldr.exe 94 PID 1000 wrote to memory of 3716 1000 oobeldr.exe 95 PID 1000 wrote to memory of 3716 1000 oobeldr.exe 95 PID 1000 wrote to memory of 3716 1000 oobeldr.exe 95 PID 2776 wrote to memory of 3080 2776 oobeldr.exe 98 PID 2776 wrote to memory of 3080 2776 oobeldr.exe 98 PID 2776 wrote to memory of 3080 2776 oobeldr.exe 98 PID 2776 wrote to memory of 3080 2776 oobeldr.exe 98 PID 2776 wrote to memory of 3080 2776 oobeldr.exe 98 PID 2776 wrote to memory of 3080 2776 oobeldr.exe 98 PID 2776 wrote to memory of 3080 2776 oobeldr.exe 98 PID 2776 wrote to memory of 3080 2776 oobeldr.exe 98 PID 2776 wrote to memory of 3080 2776 oobeldr.exe 98
Processes
-
C:\Users\Admin\AppData\Local\Temp\108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7.exe"C:\Users\Admin\AppData\Local\Temp\108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4996 -
C:\Users\Admin\AppData\Local\Temp\108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7.exeC:\Users\Admin\AppData\Local\Temp\108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7.exe2⤵PID:4092
-
-
C:\Users\Admin\AppData\Local\Temp\108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7.exeC:\Users\Admin\AppData\Local\Temp\108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7.exe2⤵
- Suspicious use of WriteProcessMemory
PID:1476 -
C:\Windows\SysWOW64\schtasks.exe/C /create /F /sc minute /mo 1 /tn "Telemetry Logging" /tr "C:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exe"3⤵
- Creates scheduled task(s)
PID:3488
-
-
-
C:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exeC:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exe1⤵
- Executes dropped EXE
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1796 -
C:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exeC:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exe2⤵
- Executes dropped EXE
- Suspicious use of WriteProcessMemory
PID:1000 -
C:\Windows\SysWOW64\schtasks.exe/C /create /F /sc minute /mo 1 /tn "Telemetry Logging" /tr "C:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exe"3⤵
- Creates scheduled task(s)
PID:3716
-
-
-
C:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exeC:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exe1⤵
- Executes dropped EXE
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2776 -
C:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exeC:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exe2⤵
- Executes dropped EXE
PID:3080
-
Network
MITRE ATT&CK Enterprise v6
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
789B
MD503d2df1e8834bc4ec1756735429b458c
SHA14ee6c0f5b04c8e0c5076219c5724032daab11d40
SHA256745ab70552d9a0463b791fd8dc1942838ac3e34fb1a68f09ed3766c7e3b05631
SHA5122482c3d4478125ccbc7f224f50e86b7bf925ed438b59f4dce57b9b6bcdb59df51417049096b131b6b911173550eed98bc92aba7050861de303a692f0681b197b
-
Filesize
322KB
MD5cb4b8ce7c6b3fdecfb11f9ee650f7178
SHA172d43e6de17cdca67d5dbe14ac33f56b44972e2d
SHA256108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7
SHA512afe3ac38963a29fff69447e96bdb8ad861f704e84ac24eb6a1579f17ac57bdb24a50218bfb079b3a0d4126a5f1b10257f67772e1f4974c1a62a7edc2d30db7f1
-
Filesize
322KB
MD5cb4b8ce7c6b3fdecfb11f9ee650f7178
SHA172d43e6de17cdca67d5dbe14ac33f56b44972e2d
SHA256108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7
SHA512afe3ac38963a29fff69447e96bdb8ad861f704e84ac24eb6a1579f17ac57bdb24a50218bfb079b3a0d4126a5f1b10257f67772e1f4974c1a62a7edc2d30db7f1
-
Filesize
322KB
MD5cb4b8ce7c6b3fdecfb11f9ee650f7178
SHA172d43e6de17cdca67d5dbe14ac33f56b44972e2d
SHA256108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7
SHA512afe3ac38963a29fff69447e96bdb8ad861f704e84ac24eb6a1579f17ac57bdb24a50218bfb079b3a0d4126a5f1b10257f67772e1f4974c1a62a7edc2d30db7f1
-
Filesize
322KB
MD5cb4b8ce7c6b3fdecfb11f9ee650f7178
SHA172d43e6de17cdca67d5dbe14ac33f56b44972e2d
SHA256108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7
SHA512afe3ac38963a29fff69447e96bdb8ad861f704e84ac24eb6a1579f17ac57bdb24a50218bfb079b3a0d4126a5f1b10257f67772e1f4974c1a62a7edc2d30db7f1
-
Filesize
322KB
MD5cb4b8ce7c6b3fdecfb11f9ee650f7178
SHA172d43e6de17cdca67d5dbe14ac33f56b44972e2d
SHA256108e48d0a83407bb7e4d5fad8807ae298b641de11439a43bdb6f86c4d4b64eb7
SHA512afe3ac38963a29fff69447e96bdb8ad861f704e84ac24eb6a1579f17ac57bdb24a50218bfb079b3a0d4126a5f1b10257f67772e1f4974c1a62a7edc2d30db7f1