Analysis
-
max time kernel
149s -
max time network
140s -
platform
windows10-2004_x64 -
resource
win10v2004-20240419-en -
resource tags
arch:x64arch:x86image:win10v2004-20240419-enlocale:en-usos:windows10-2004-x64system -
submitted
07-05-2024 17:47
Static task
static1
Behavioral task
behavioral1
Sample
ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe
Resource
win7-20240215-en
General
-
Target
ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe
-
Size
241KB
-
MD5
f5df66951851f33e5035632a77c5a1cf
-
SHA1
e30fc11bdb5ede3a634b2c0106dc90041b5e6863
-
SHA256
ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971
-
SHA512
c0ddea4de3754d196af8096fe6de36e3b672e409cbb4ee46fd4456f3e6236aad9a70dd449a9d1ab4a601195f0c58147cedfb3355ba8b28d0109dfbb735b55d41
-
SSDEEP
6144:WiZukvpZlYRKu6VgVZJZosZH2I7aoFJpC3C0vArtnQQgUNbfQQUyCXcz1ychrGCm:WaumGgu6VgV/d26aoFJpHiArLgMboQDY
Malware Config
Extracted
xenorat
dns.requimacofradian.site
Xeno_rat_nd8818g
-
delay
60000
-
install_path
appdata
-
port
1243
-
startup_name
uic
Signatures
-
Detects XenoRAT malware 1 IoCs
XenoRAT is an open-source remote access tool (RAT) developed in C#.
resource yara_rule behavioral2/memory/3628-9-0x0000000000400000-0x0000000000412000-memory.dmp XenoRAT -
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-877519540-908060166-1852957295-1000\Control Panel\International\Geo\Nation ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe -
Executes dropped EXE 4 IoCs
pid Process 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 3156 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 3140 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 3496 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe -
Suspicious use of SetThreadContext 6 IoCs
description pid Process procid_target PID 208 set thread context of 3628 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 89 PID 208 set thread context of 4644 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 90 PID 208 set thread context of 3892 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 91 PID 2688 set thread context of 3156 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 97 PID 2688 set thread context of 3140 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 98 PID 2688 set thread context of 3496 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 99 -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s).
-
Program crash 1 IoCs
pid pid_target Process procid_target 3616 3892 WerFault.exe 91 -
Creates scheduled task(s) 1 TTPs 1 IoCs
Schtasks is often used by malware for persistence or to perform post-infection execution.
pid Process 3464 schtasks.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeDebugPrivilege 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe Token: SeDebugPrivilege 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe -
Suspicious use of WriteProcessMemory 54 IoCs
description pid Process procid_target PID 208 wrote to memory of 3628 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 89 PID 208 wrote to memory of 3628 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 89 PID 208 wrote to memory of 3628 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 89 PID 208 wrote to memory of 3628 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 89 PID 208 wrote to memory of 3628 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 89 PID 208 wrote to memory of 3628 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 89 PID 208 wrote to memory of 3628 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 89 PID 208 wrote to memory of 3628 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 89 PID 208 wrote to memory of 4644 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 90 PID 208 wrote to memory of 4644 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 90 PID 208 wrote to memory of 4644 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 90 PID 208 wrote to memory of 4644 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 90 PID 208 wrote to memory of 4644 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 90 PID 208 wrote to memory of 4644 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 90 PID 208 wrote to memory of 4644 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 90 PID 208 wrote to memory of 4644 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 90 PID 208 wrote to memory of 3892 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 91 PID 208 wrote to memory of 3892 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 91 PID 208 wrote to memory of 3892 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 91 PID 208 wrote to memory of 3892 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 91 PID 208 wrote to memory of 3892 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 91 PID 208 wrote to memory of 3892 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 91 PID 208 wrote to memory of 3892 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 91 PID 208 wrote to memory of 3892 208 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 91 PID 3628 wrote to memory of 2688 3628 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 94 PID 3628 wrote to memory of 2688 3628 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 94 PID 3628 wrote to memory of 2688 3628 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 94 PID 2688 wrote to memory of 3156 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 97 PID 2688 wrote to memory of 3156 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 97 PID 2688 wrote to memory of 3156 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 97 PID 2688 wrote to memory of 3156 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 97 PID 2688 wrote to memory of 3156 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 97 PID 2688 wrote to memory of 3156 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 97 PID 2688 wrote to memory of 3156 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 97 PID 2688 wrote to memory of 3156 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 97 PID 2688 wrote to memory of 3140 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 98 PID 2688 wrote to memory of 3140 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 98 PID 2688 wrote to memory of 3140 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 98 PID 2688 wrote to memory of 3140 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 98 PID 2688 wrote to memory of 3140 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 98 PID 2688 wrote to memory of 3140 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 98 PID 2688 wrote to memory of 3140 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 98 PID 2688 wrote to memory of 3140 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 98 PID 2688 wrote to memory of 3496 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 99 PID 2688 wrote to memory of 3496 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 99 PID 2688 wrote to memory of 3496 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 99 PID 2688 wrote to memory of 3496 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 99 PID 2688 wrote to memory of 3496 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 99 PID 2688 wrote to memory of 3496 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 99 PID 2688 wrote to memory of 3496 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 99 PID 2688 wrote to memory of 3496 2688 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 99 PID 4644 wrote to memory of 3464 4644 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 111 PID 4644 wrote to memory of 3464 4644 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 111 PID 4644 wrote to memory of 3464 4644 ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe 111
Processes
-
C:\Users\Admin\AppData\Local\Temp\ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe"C:\Users\Admin\AppData\Local\Temp\ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:208 -
C:\Users\Admin\AppData\Local\Temp\ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exeC:\Users\Admin\AppData\Local\Temp\ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe2⤵
- Checks computer location settings
- Suspicious use of WriteProcessMemory
PID:3628 -
C:\Users\Admin\AppData\Roaming\XenoManager\ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe"C:\Users\Admin\AppData\Roaming\XenoManager\ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe"3⤵
- Executes dropped EXE
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:2688 -
C:\Users\Admin\AppData\Roaming\XenoManager\ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exeC:\Users\Admin\AppData\Roaming\XenoManager\ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe4⤵
- Executes dropped EXE
PID:3156
-
-
C:\Users\Admin\AppData\Roaming\XenoManager\ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exeC:\Users\Admin\AppData\Roaming\XenoManager\ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe4⤵
- Executes dropped EXE
PID:3140
-
-
C:\Users\Admin\AppData\Roaming\XenoManager\ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exeC:\Users\Admin\AppData\Roaming\XenoManager\ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe4⤵
- Executes dropped EXE
PID:3496
-
-
-
-
C:\Users\Admin\AppData\Local\Temp\ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exeC:\Users\Admin\AppData\Local\Temp\ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe2⤵
- Suspicious use of WriteProcessMemory
PID:4644 -
C:\Windows\SysWOW64\schtasks.exe"schtasks.exe" /Create /TN "uic" /XML "C:\Users\Admin\AppData\Local\Temp\tmp3246.tmp" /F3⤵
- Creates scheduled task(s)
PID:3464
-
-
-
C:\Users\Admin\AppData\Local\Temp\ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exeC:\Users\Admin\AppData\Local\Temp\ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe2⤵PID:3892
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3892 -s 843⤵
- Program crash
PID:3616
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 3892 -ip 38921⤵PID:3912
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe.log
Filesize706B
MD5d95c58e609838928f0f49837cab7dfd2
SHA155e7139a1e3899195b92ed8771d1ca2c7d53c916
SHA2560407c814aef0d62aec7fd39b7c2f614746f0d8ff41f8ef957736f520f14b0339
SHA512405310b29a833604c6627063bfdcf055a197e01f633ef21da238f1a6415a02e21315d689b4a6669db23e82152bed6f3492afb60963e6b2a0e9bb2ac09a480b5d
-
Filesize
1KB
MD587b1b4884c233d6ab0a5b10ddc101a9d
SHA1a194444f1aedbf76489c904d39d93363e11c3676
SHA256e27b850bee8f4189a166de9f0bf4a044c33ef8f4ede3dc7d3735b85d473e4f6c
SHA5121e5be880c35dd6c5c49b44be53914cd36bb4f648c0390ac580597c8d3f24a598fd84c3c9617282ec453471a1f0d4fdde30fd1a097319d6959020c16b8e8a10d7
-
C:\Users\Admin\AppData\Roaming\XenoManager\ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971.exe
Filesize241KB
MD5f5df66951851f33e5035632a77c5a1cf
SHA1e30fc11bdb5ede3a634b2c0106dc90041b5e6863
SHA256ff6341544da4fddb3d6b82675a213c2107114f9a5ee57ad963ab38809e467971
SHA512c0ddea4de3754d196af8096fe6de36e3b672e409cbb4ee46fd4456f3e6236aad9a70dd449a9d1ab4a601195f0c58147cedfb3355ba8b28d0109dfbb735b55d41