Analysis
-
max time kernel
291s -
max time network
296s -
platform
windows10-1703_x64 -
resource
win10-20231215-en -
resource tags
arch:x64arch:x86image:win10-20231215-enlocale:en-usos:windows10-1703-x64system -
submitted
08-01-2024 04:56
Static task
static1
Behavioral task
behavioral1
Sample
a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exe
Resource
win7-20231215-en
Behavioral task
behavioral2
Sample
a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exe
Resource
win10-20231215-en
General
-
Target
a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exe
-
Size
324KB
-
MD5
85934bdf0c54ce3d93872595cf58cada
-
SHA1
8ca1628086eafccb4080a73bd706b54cbd9fa6b0
-
SHA256
a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315
-
SHA512
1b9871772f0e08a94552a0115faf003ac87adda0f989f7451079cd871e905d633ad4bc9ec2051dbf2aad1e6c9dc6dc29ea5d24f13305eb1685c84c8994158fe1
-
SSDEEP
6144:eKlzr1sYCzek2ciDaP9Xk6Ln1W8W/9InBSkZZmLdGcAdgdY6RKpjS:eGhQ2ciDq9ZL1W8q9InBRqELdolRKpj
Malware Config
Signatures
-
Executes dropped EXE 10 IoCs
pid Process 3492 oobeldr.exe 3800 oobeldr.exe 4388 oobeldr.exe 3940 oobeldr.exe 4120 oobeldr.exe 1944 oobeldr.exe 4152 oobeldr.exe 2792 oobeldr.exe 208 oobeldr.exe 2172 oobeldr.exe -
Suspicious use of SetThreadContext 5 IoCs
description pid Process procid_target PID 5096 set thread context of 4112 5096 a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exe 74 PID 3492 set thread context of 3800 3492 oobeldr.exe 78 PID 4388 set thread context of 3940 4388 oobeldr.exe 82 PID 4120 set thread context of 4152 4120 oobeldr.exe 85 PID 2792 set thread context of 208 2792 oobeldr.exe 89 -
Program crash 1 IoCs
pid pid_target Process procid_target 4988 4152 WerFault.exe 85 -
Creates scheduled task(s) 1 TTPs 2 IoCs
Schtasks is often used by malware for persistence or to perform post-infection execution.
pid Process 3772 schtasks.exe 4636 schtasks.exe -
Suspicious use of WriteProcessMemory 57 IoCs
description pid Process procid_target PID 5096 wrote to memory of 5080 5096 a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exe 16 PID 5096 wrote to memory of 5080 5096 a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exe 16 PID 5096 wrote to memory of 5080 5096 a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exe 16 PID 5096 wrote to memory of 4112 5096 a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exe 74 PID 5096 wrote to memory of 4112 5096 a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exe 74 PID 5096 wrote to memory of 4112 5096 a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exe 74 PID 5096 wrote to memory of 4112 5096 a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exe 74 PID 5096 wrote to memory of 4112 5096 a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exe 74 PID 5096 wrote to memory of 4112 5096 a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exe 74 PID 5096 wrote to memory of 4112 5096 a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exe 74 PID 5096 wrote to memory of 4112 5096 a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exe 74 PID 5096 wrote to memory of 4112 5096 a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exe 74 PID 4112 wrote to memory of 3772 4112 a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exe 76 PID 4112 wrote to memory of 3772 4112 a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exe 76 PID 4112 wrote to memory of 3772 4112 a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exe 76 PID 3492 wrote to memory of 3800 3492 oobeldr.exe 78 PID 3492 wrote to memory of 3800 3492 oobeldr.exe 78 PID 3492 wrote to memory of 3800 3492 oobeldr.exe 78 PID 3492 wrote to memory of 3800 3492 oobeldr.exe 78 PID 3492 wrote to memory of 3800 3492 oobeldr.exe 78 PID 3492 wrote to memory of 3800 3492 oobeldr.exe 78 PID 3492 wrote to memory of 3800 3492 oobeldr.exe 78 PID 3492 wrote to memory of 3800 3492 oobeldr.exe 78 PID 3492 wrote to memory of 3800 3492 oobeldr.exe 78 PID 3800 wrote to memory of 4636 3800 oobeldr.exe 80 PID 3800 wrote to memory of 4636 3800 oobeldr.exe 80 PID 3800 wrote to memory of 4636 3800 oobeldr.exe 80 PID 4388 wrote to memory of 3940 4388 oobeldr.exe 82 PID 4388 wrote to memory of 3940 4388 oobeldr.exe 82 PID 4388 wrote to memory of 3940 4388 oobeldr.exe 82 PID 4388 wrote to memory of 3940 4388 oobeldr.exe 82 PID 4388 wrote to memory of 3940 4388 oobeldr.exe 82 PID 4388 wrote to memory of 3940 4388 oobeldr.exe 82 PID 4388 wrote to memory of 3940 4388 oobeldr.exe 82 PID 4388 wrote to memory of 3940 4388 oobeldr.exe 82 PID 4388 wrote to memory of 3940 4388 oobeldr.exe 82 PID 4120 wrote to memory of 1944 4120 oobeldr.exe 84 PID 4120 wrote to memory of 1944 4120 oobeldr.exe 84 PID 4120 wrote to memory of 1944 4120 oobeldr.exe 84 PID 4120 wrote to memory of 4152 4120 oobeldr.exe 85 PID 4120 wrote to memory of 4152 4120 oobeldr.exe 85 PID 4120 wrote to memory of 4152 4120 oobeldr.exe 85 PID 4120 wrote to memory of 4152 4120 oobeldr.exe 85 PID 4120 wrote to memory of 4152 4120 oobeldr.exe 85 PID 4120 wrote to memory of 4152 4120 oobeldr.exe 85 PID 4120 wrote to memory of 4152 4120 oobeldr.exe 85 PID 4120 wrote to memory of 4152 4120 oobeldr.exe 85 PID 4120 wrote to memory of 4152 4120 oobeldr.exe 85 PID 2792 wrote to memory of 208 2792 oobeldr.exe 89 PID 2792 wrote to memory of 208 2792 oobeldr.exe 89 PID 2792 wrote to memory of 208 2792 oobeldr.exe 89 PID 2792 wrote to memory of 208 2792 oobeldr.exe 89 PID 2792 wrote to memory of 208 2792 oobeldr.exe 89 PID 2792 wrote to memory of 208 2792 oobeldr.exe 89 PID 2792 wrote to memory of 208 2792 oobeldr.exe 89 PID 2792 wrote to memory of 208 2792 oobeldr.exe 89 PID 2792 wrote to memory of 208 2792 oobeldr.exe 89
Processes
-
C:\Users\Admin\AppData\Local\Temp\a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exe"C:\Users\Admin\AppData\Local\Temp\a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:5096 -
C:\Users\Admin\AppData\Local\Temp\a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exeC:\Users\Admin\AppData\Local\Temp\a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exe2⤵PID:5080
-
-
C:\Users\Admin\AppData\Local\Temp\a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exeC:\Users\Admin\AppData\Local\Temp\a59abee24d946f4d3c1c4fb6d99406c72da09e7cb56e4e404328f5c39a690315.exe2⤵
- Suspicious use of WriteProcessMemory
PID:4112 -
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:3772
-
-
-
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:3492 -
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:3800 -
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:4636
-
-
-
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:4388 -
C:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exeC:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exe2⤵
- Executes dropped EXE
PID:3940
-
-
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:4120 -
C:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exeC:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exe2⤵
- Executes dropped EXE
PID:1944
-
-
C:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exeC:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exe2⤵
- Executes dropped EXE
PID:4152 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4152 -s 1523⤵
- Program crash
PID:4988
-
-
-
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:2792 -
C:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exeC:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exe2⤵
- Executes dropped EXE
PID:208
-
-
C:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exeC:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exe1⤵
- Executes dropped EXE
PID:2172 -
C:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exeC:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exe2⤵PID:4848
-
-
C:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exeC:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exe2⤵PID:1216
-