Analysis
-
max time kernel
141s -
max time network
152s -
platform
windows10-2004_x64 -
resource
win10v2004-20240226-en -
resource tags
arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system -
submitted
22-05-2024 01:16
Static task
static1
Behavioral task
behavioral1
Sample
2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe
Resource
win7-20240221-en
Behavioral task
behavioral2
Sample
2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe
Resource
win10v2004-20240226-en
General
-
Target
2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe
-
Size
791KB
-
MD5
c4a6297b79141d28849a7d5c3a7f046c
-
SHA1
65fc3f8aff2aade19bc0a9c4fbd6ecaf9f94d071
-
SHA256
2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3
-
SHA512
b96822fb3bc8abca6c4d2301a20e730b73ab93306ee22f408a05910eb6904a9db186134986384f7a1a5462f532760d39f6bb20885e5801472726af328e166015
-
SSDEEP
12288:xIlWET/mr9K+22BEEzFatnv1KakJkeYXrluEyfXfKDhOJodTVWWUjy0CUTrLJXgX:KWtb3BEN1QCrEEESDh9TVWFy0CQy
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exedescription pid process target process PID 4076 set thread context of 2720 4076 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 3816 2720 WerFault.exe 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe -
Suspicious behavior: EnumeratesProcesses 4 IoCs
Processes:
2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exepid process 4076 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe 4076 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe 2720 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe 2720 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
Processes:
2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exedescription pid process Token: SeDebugPrivilege 4076 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe -
Suspicious use of WriteProcessMemory 9 IoCs
Processes:
2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exedescription pid process target process PID 4076 wrote to memory of 2588 4076 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe PID 4076 wrote to memory of 2588 4076 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe PID 4076 wrote to memory of 2588 4076 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe PID 4076 wrote to memory of 2720 4076 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe PID 4076 wrote to memory of 2720 4076 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe PID 4076 wrote to memory of 2720 4076 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe PID 4076 wrote to memory of 2720 4076 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe PID 4076 wrote to memory of 2720 4076 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe PID 4076 wrote to memory of 2720 4076 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe 2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe"C:\Users\Admin\AppData\Local\Temp\2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:4076 -
C:\Users\Admin\AppData\Local\Temp\2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe"C:\Users\Admin\AppData\Local\Temp\2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe"2⤵PID:2588
-
C:\Users\Admin\AppData\Local\Temp\2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe"C:\Users\Admin\AppData\Local\Temp\2dad4966cfeff750760dbac52eb1db02b77515fe06599a756bf4bdfb6a7e9df3.exe"2⤵
- Suspicious behavior: EnumeratesProcesses
PID:2720 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2720 -s 1843⤵
- Program crash
PID:3816
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 428 -p 2720 -ip 27201⤵PID:4900
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --type=utility --utility-sub-type=asset_store.mojom.AssetStoreService --lang=en-US --service-sandbox-type=asset_store_service --no-appcompat-clear --mojo-platform-channel-handle=4264 --field-trial-handle=2656,i,16940681401824032220,151921362336696246,262144 --variations-seed-version /prefetch:81⤵PID:4760