Analysis
-
max time kernel
53s -
max time network
147s -
platform
windows10-1703_x64 -
resource
win10-20220812-en -
resource tags
arch:x64arch:x86image:win10-20220812-enlocale:en-usos:windows10-1703-x64system -
submitted
01-11-2022 20:44
Static task
static1
Behavioral task
behavioral1
Sample
30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d.exe
Resource
win10-20220812-en
windows10-1703-x64
3 signatures
150 seconds
General
-
Target
30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d.exe
-
Size
325KB
-
MD5
48349ba91d79b3e02e8590674813e0e5
-
SHA1
edf0a7b3fc7d96369510c814c1597a96685ae5dc
-
SHA256
30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d
-
SHA512
03c7051fdd5021eb064f18ccac18aba7bfdd288065df6dc90200b401f9fd7625f054cb2fbe08421020ccc8181633156a2f64ad2ed7bbc3c99a70a7b958ccb2b1
-
SSDEEP
6144:eKlzr1sYCzek2ciDaP9Xk6Ln1W8W/9InBSkZZmLdGcAdgdY6RKpjS:eGhQ2ciDq9ZL1W8q9InBRqELdolRKpj
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4368 set thread context of 1412 4368 30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d.exe 68 -
Creates scheduled task(s) 1 TTPs 1 IoCs
Schtasks is often used by malware for persistence or to perform post-infection execution.
pid Process 5084 schtasks.exe -
Suspicious use of WriteProcessMemory 15 IoCs
description pid Process procid_target PID 4368 wrote to memory of 4600 4368 30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d.exe 67 PID 4368 wrote to memory of 4600 4368 30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d.exe 67 PID 4368 wrote to memory of 4600 4368 30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d.exe 67 PID 4368 wrote to memory of 1412 4368 30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d.exe 68 PID 4368 wrote to memory of 1412 4368 30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d.exe 68 PID 4368 wrote to memory of 1412 4368 30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d.exe 68 PID 4368 wrote to memory of 1412 4368 30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d.exe 68 PID 4368 wrote to memory of 1412 4368 30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d.exe 68 PID 4368 wrote to memory of 1412 4368 30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d.exe 68 PID 4368 wrote to memory of 1412 4368 30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d.exe 68 PID 4368 wrote to memory of 1412 4368 30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d.exe 68 PID 4368 wrote to memory of 1412 4368 30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d.exe 68 PID 1412 wrote to memory of 5084 1412 30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d.exe 69 PID 1412 wrote to memory of 5084 1412 30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d.exe 69 PID 1412 wrote to memory of 5084 1412 30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d.exe 69
Processes
-
C:\Users\Admin\AppData\Local\Temp\30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d.exe"C:\Users\Admin\AppData\Local\Temp\30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4368 -
C:\Users\Admin\AppData\Local\Temp\30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d.exeC:\Users\Admin\AppData\Local\Temp\30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d.exe2⤵PID:4600
-
-
C:\Users\Admin\AppData\Local\Temp\30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d.exeC:\Users\Admin\AppData\Local\Temp\30ff4a0ff40b16c383af9a4fe2d6b265347423657de73e7f0992737389c08d1d.exe2⤵
- Suspicious use of WriteProcessMemory
PID:1412 -
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:5084
-
-