Analysis
-
max time kernel
173s -
max time network
180s -
platform
windows10-2004_x64 -
resource
win10v2004-20220414-en -
submitted
09/06/2022, 13:17
Static task
static1
Behavioral task
behavioral1
Sample
6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe
Resource
win7-20220414-en
Behavioral task
behavioral2
Sample
6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe
Resource
win10v2004-20220414-en
General
-
Target
6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe
-
Size
605KB
-
MD5
7b69e3aaba970c25b40fad29a564a0cf
-
SHA1
6af0a8634ef3003ccbc743c7ed8869ec2c560042
-
SHA256
6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049
-
SHA512
bba40d253de3c19f4c2f890c04d7482b0012f872e1198cc03882ccb08be7c0cdca9bf5b3b6a924e7f2ea337d34ee809fd3c10aa12c15bed036d828dea53e0546
Malware Config
Signatures
-
Executes dropped EXE 2 IoCs
pid Process 4384 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 564 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe -
Checks computer location settings 2 TTPs 1 IoCs
Looks up country code configured in the registry, likely geofence.
description ioc Process Key value queried \REGISTRY\USER\S-1-5-21-3751123196-3323558407-1869646069-1000\Control Panel\International\Geo\Nation 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe -
Adds Run key to start application 2 TTPs 2 IoCs
description ioc Process Set value (str) \REGISTRY\USER\S-1-5-21-3751123196-3323558407-1869646069-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\winregedit = "C:\\Users\\Admin\\AppData\\Roaming\\winlogomereg\\windowsreg.exe" 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe Set value (str) \REGISTRY\USER\S-1-5-21-3751123196-3323558407-1869646069-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\winregedit = "\\winlogomereg\\windowsreg.exe" 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe -
Suspicious use of SetThreadContext 2 IoCs
description pid Process procid_target PID 1848 set thread context of 4552 1848 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 84 PID 4384 set thread context of 564 4384 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 95 -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Runs ping.exe 1 TTPs 1 IoCs
pid Process 1732 PING.EXE -
Suspicious use of AdjustPrivilegeToken 6 IoCs
description pid Process Token: SeDebugPrivilege 1848 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe Token: SeDebugPrivilege 4552 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe Token: SeDebugPrivilege 4384 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe Token: SeDebugPrivilege 564 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe Token: 33 564 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe Token: SeIncBasePriorityPrivilege 564 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 564 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe -
Suspicious use of WriteProcessMemory 25 IoCs
description pid Process procid_target PID 1848 wrote to memory of 4552 1848 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 84 PID 1848 wrote to memory of 4552 1848 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 84 PID 1848 wrote to memory of 4552 1848 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 84 PID 1848 wrote to memory of 4552 1848 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 84 PID 1848 wrote to memory of 4552 1848 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 84 PID 1848 wrote to memory of 4552 1848 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 84 PID 1848 wrote to memory of 4552 1848 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 84 PID 1848 wrote to memory of 4552 1848 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 84 PID 4552 wrote to memory of 4384 4552 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 91 PID 4552 wrote to memory of 4384 4552 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 91 PID 4552 wrote to memory of 4384 4552 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 91 PID 4552 wrote to memory of 4340 4552 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 92 PID 4552 wrote to memory of 4340 4552 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 92 PID 4552 wrote to memory of 4340 4552 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 92 PID 4340 wrote to memory of 1732 4340 cmd.exe 94 PID 4340 wrote to memory of 1732 4340 cmd.exe 94 PID 4340 wrote to memory of 1732 4340 cmd.exe 94 PID 4384 wrote to memory of 564 4384 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 95 PID 4384 wrote to memory of 564 4384 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 95 PID 4384 wrote to memory of 564 4384 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 95 PID 4384 wrote to memory of 564 4384 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 95 PID 4384 wrote to memory of 564 4384 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 95 PID 4384 wrote to memory of 564 4384 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 95 PID 4384 wrote to memory of 564 4384 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 95 PID 4384 wrote to memory of 564 4384 6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe 95
Processes
-
C:\Users\Admin\AppData\Local\Temp\6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe"C:\Users\Admin\AppData\Local\Temp\6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:1848 -
C:\Users\Admin\AppData\Local\Temp\6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe"C:\Users\Admin\AppData\Local\Temp\6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe"2⤵
- Checks computer location settings
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:4552 -
C:\Users\Admin\AppData\Local\Temp\6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049\6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe"C:\Users\Admin\AppData\Local\Temp\6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049\6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe"3⤵
- Executes dropped EXE
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:4384 -
C:\Users\Admin\AppData\Local\Temp\6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049\6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe"C:\Users\Admin\AppData\Local\Temp\6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049\6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe"4⤵
- Executes dropped EXE
- Adds Run key to start application
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
PID:564
-
-
-
C:\Windows\SysWOW64\cmd.exe"C:\Windows\System32\cmd.exe" /C ping 1.1.1.1 -n 1 -w 1000 > Nul & Del "C:\Users\Admin\AppData\Local\Temp\6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe"3⤵
- Suspicious use of WriteProcessMemory
PID:4340 -
C:\Windows\SysWOW64\PING.EXEping 1.1.1.1 -n 1 -w 10004⤵
- Runs ping.exe
PID:1732
-
-
-
-
C:\Windows\system32\wbem\WmiApSrv.exeC:\Windows\system32\wbem\WmiApSrv.exe1⤵PID:5068
Network
MITRE ATT&CK Enterprise v6
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe.log
Filesize1KB
MD58ec831f3e3a3f77e4a7b9cd32b48384c
SHA1d83f09fd87c5bd86e045873c231c14836e76a05c
SHA2567667e538030e3f8ce2886e47a01af24cb0ea70528b1e821c5d8832c5076cb982
SHA51226bffa2406b66368bd412bf25869a792631455645992cdcade2dbc13a2e56fb546414a6a9223b94c96c38d89187add6678d4779a88b38b0c9e36be8527b213c3
-
C:\Users\Admin\AppData\Local\Temp\6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049\6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe
Filesize605KB
MD57b69e3aaba970c25b40fad29a564a0cf
SHA16af0a8634ef3003ccbc743c7ed8869ec2c560042
SHA2566d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049
SHA512bba40d253de3c19f4c2f890c04d7482b0012f872e1198cc03882ccb08be7c0cdca9bf5b3b6a924e7f2ea337d34ee809fd3c10aa12c15bed036d828dea53e0546
-
C:\Users\Admin\AppData\Local\Temp\6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049\6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe
Filesize605KB
MD57b69e3aaba970c25b40fad29a564a0cf
SHA16af0a8634ef3003ccbc743c7ed8869ec2c560042
SHA2566d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049
SHA512bba40d253de3c19f4c2f890c04d7482b0012f872e1198cc03882ccb08be7c0cdca9bf5b3b6a924e7f2ea337d34ee809fd3c10aa12c15bed036d828dea53e0546
-
C:\Users\Admin\AppData\Local\Temp\6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049\6d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049.exe
Filesize605KB
MD57b69e3aaba970c25b40fad29a564a0cf
SHA16af0a8634ef3003ccbc743c7ed8869ec2c560042
SHA2566d51c2ebe467adf6852e4a8b6d456ee696f75a970705c2ad692cb1f1e8b31049
SHA512bba40d253de3c19f4c2f890c04d7482b0012f872e1198cc03882ccb08be7c0cdca9bf5b3b6a924e7f2ea337d34ee809fd3c10aa12c15bed036d828dea53e0546