Analysis
-
max time kernel
144s -
max time network
156s -
platform
windows10-2004_x64 -
resource
win10v2004-20240508-en -
resource tags
arch:x64arch:x86image:win10v2004-20240508-enlocale:en-usos:windows10-2004-x64system -
submitted
04-07-2024 17:16
Static task
static1
Behavioral task
behavioral1
Sample
ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe
Resource
win7-20240508-en
General
-
Target
ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe
-
Size
221KB
-
MD5
6621fcab4de5fab7eac4d8d03c87f233
-
SHA1
70dd77e26e803239877b30439eb123454bc137cc
-
SHA256
ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2
-
SHA512
d132d2399c65b6b0083f7172c04d4708b28b3deceb93fd0c5dfc5bcfdfd9ee459c5b46853d176e08e99a2a8842945e6cd396e4137fac430c67abea388e83789c
-
SSDEEP
6144:WdwDpybdvNg134Gnq2YZstYaGaqjWq9441D/Kv+I:/cE134GiZ4Ya7mWq9441D/Kvj
Malware Config
Extracted
xenorat
91.92.248.167
Wolid_rat_nd8859g
-
delay
60000
-
install_path
appdata
-
port
1280
-
startup_name
cms
Signatures
-
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-4124900551-4068476067-3491212533-1000\Control Panel\International\Geo\Nation ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe -
Executes dropped EXE 4 IoCs
pid Process 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 1628 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 1624 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 3816 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe -
Suspicious use of SetThreadContext 6 IoCs
description pid Process procid_target PID 2264 set thread context of 4376 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 81 PID 2264 set thread context of 3912 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 82 PID 2264 set thread context of 1868 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 83 PID 3012 set thread context of 1628 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 88 PID 3012 set thread context of 1624 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 89 PID 3012 set thread context of 3816 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 90 -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s).
-
Program crash 2 IoCs
pid pid_target Process 2536 1868 WerFault.exe 3056 3816 WerFault.exe -
Scheduled Task/Job: Scheduled Task 1 TTPs 1 IoCs
Schtasks is often used by malware for persistence or to perform post-infection execution.
pid Process 2612 schtasks.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeDebugPrivilege 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe Token: SeDebugPrivilege 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe -
Suspicious use of WriteProcessMemory 54 IoCs
description pid Process procid_target PID 2264 wrote to memory of 4376 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 81 PID 2264 wrote to memory of 4376 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 81 PID 2264 wrote to memory of 4376 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 81 PID 2264 wrote to memory of 4376 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 81 PID 2264 wrote to memory of 4376 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 81 PID 2264 wrote to memory of 4376 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 81 PID 2264 wrote to memory of 4376 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 81 PID 2264 wrote to memory of 4376 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 81 PID 2264 wrote to memory of 3912 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 82 PID 2264 wrote to memory of 3912 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 82 PID 2264 wrote to memory of 3912 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 82 PID 2264 wrote to memory of 3912 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 82 PID 2264 wrote to memory of 3912 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 82 PID 2264 wrote to memory of 3912 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 82 PID 2264 wrote to memory of 3912 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 82 PID 2264 wrote to memory of 3912 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 82 PID 2264 wrote to memory of 1868 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 83 PID 2264 wrote to memory of 1868 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 83 PID 2264 wrote to memory of 1868 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 83 PID 2264 wrote to memory of 1868 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 83 PID 2264 wrote to memory of 1868 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 83 PID 2264 wrote to memory of 1868 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 83 PID 2264 wrote to memory of 1868 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 83 PID 2264 wrote to memory of 1868 2264 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 83 PID 3912 wrote to memory of 3012 3912 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 86 PID 3912 wrote to memory of 3012 3912 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 86 PID 3912 wrote to memory of 3012 3912 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 86 PID 3012 wrote to memory of 1628 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 88 PID 3012 wrote to memory of 1628 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 88 PID 3012 wrote to memory of 1628 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 88 PID 3012 wrote to memory of 1628 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 88 PID 3012 wrote to memory of 1628 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 88 PID 3012 wrote to memory of 1628 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 88 PID 3012 wrote to memory of 1628 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 88 PID 3012 wrote to memory of 1628 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 88 PID 3012 wrote to memory of 1624 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 89 PID 3012 wrote to memory of 1624 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 89 PID 3012 wrote to memory of 1624 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 89 PID 3012 wrote to memory of 1624 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 89 PID 3012 wrote to memory of 1624 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 89 PID 3012 wrote to memory of 1624 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 89 PID 3012 wrote to memory of 1624 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 89 PID 3012 wrote to memory of 1624 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 89 PID 3012 wrote to memory of 3816 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 90 PID 3012 wrote to memory of 3816 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 90 PID 3012 wrote to memory of 3816 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 90 PID 3012 wrote to memory of 3816 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 90 PID 3012 wrote to memory of 3816 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 90 PID 3012 wrote to memory of 3816 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 90 PID 3012 wrote to memory of 3816 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 90 PID 3012 wrote to memory of 3816 3012 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 90 PID 4376 wrote to memory of 2612 4376 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 102 PID 4376 wrote to memory of 2612 4376 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 102 PID 4376 wrote to memory of 2612 4376 ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe 102
Processes
-
C:\Users\Admin\AppData\Local\Temp\ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe"C:\Users\Admin\AppData\Local\Temp\ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:2264 -
C:\Users\Admin\AppData\Local\Temp\ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exeC:\Users\Admin\AppData\Local\Temp\ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe2⤵
- Suspicious use of WriteProcessMemory
PID:4376 -
C:\Windows\SysWOW64\schtasks.exe"schtasks.exe" /Create /TN "cms" /XML "C:\Users\Admin\AppData\Local\Temp\tmp3BDB.tmp" /F3⤵
- Scheduled Task/Job: Scheduled Task
PID:2612
-
-
-
C:\Users\Admin\AppData\Local\Temp\ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exeC:\Users\Admin\AppData\Local\Temp\ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe2⤵
- Checks computer location settings
- Suspicious use of WriteProcessMemory
PID:3912 -
C:\Users\Admin\AppData\Roaming\XenoManager\ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe"C:\Users\Admin\AppData\Roaming\XenoManager\ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe"3⤵
- Executes dropped EXE
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:3012 -
C:\Users\Admin\AppData\Roaming\XenoManager\ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exeC:\Users\Admin\AppData\Roaming\XenoManager\ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe4⤵
- Executes dropped EXE
PID:1628
-
-
C:\Users\Admin\AppData\Roaming\XenoManager\ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exeC:\Users\Admin\AppData\Roaming\XenoManager\ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe4⤵
- Executes dropped EXE
PID:1624
-
-
C:\Users\Admin\AppData\Roaming\XenoManager\ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exeC:\Users\Admin\AppData\Roaming\XenoManager\ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe4⤵
- Executes dropped EXE
PID:3816 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3816 -s 805⤵
- Program crash
PID:3056
-
-
-
-
-
C:\Users\Admin\AppData\Local\Temp\ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exeC:\Users\Admin\AppData\Local\Temp\ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe2⤵PID:1868
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1868 -s 803⤵
- Program crash
PID:2536
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 432 -p 1868 -ip 18681⤵PID:1252
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 184 -p 3816 -ip 38161⤵PID:4984
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe.log
Filesize706B
MD5d95c58e609838928f0f49837cab7dfd2
SHA155e7139a1e3899195b92ed8771d1ca2c7d53c916
SHA2560407c814aef0d62aec7fd39b7c2f614746f0d8ff41f8ef957736f520f14b0339
SHA512405310b29a833604c6627063bfdcf055a197e01f633ef21da238f1a6415a02e21315d689b4a6669db23e82152bed6f3492afb60963e6b2a0e9bb2ac09a480b5d
-
Filesize
1KB
MD583d6e89b8754d25b433641acaa2a66eb
SHA1f89d5bdae947ac5cb70fc2ab675b48081d9b0732
SHA2565616a5762d790c9d6f881095099a0adae1b5f2dee34ec1909e823d851a28f5d0
SHA512fb805ced008dc025a0e851ed0075fbc7f9f65a667e82fe68a8f434490f476d1a5bceebaadedf726ac5447f7ccfbd91ef19669ef499150960c9d4b0204cbef97f
-
C:\Users\Admin\AppData\Roaming\XenoManager\ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2.exe
Filesize221KB
MD56621fcab4de5fab7eac4d8d03c87f233
SHA170dd77e26e803239877b30439eb123454bc137cc
SHA256ac781121f63db7be4e5c79ea106118ce2c7a06f0abef01be3e54ff77351691e2
SHA512d132d2399c65b6b0083f7172c04d4708b28b3deceb93fd0c5dfc5bcfdfd9ee459c5b46853d176e08e99a2a8842945e6cd396e4137fac430c67abea388e83789c