Analysis
-
max time kernel
141s -
max time network
148s -
platform
windows10-2004_x64 -
resource
win10v2004-20240704-en -
resource tags
arch:x64arch:x86image:win10v2004-20240704-enlocale:en-usos:windows10-2004-x64system -
submitted
05-07-2024 01:31
Static task
static1
Behavioral task
behavioral1
Sample
85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe
Resource
win7-20240221-en
General
-
Target
85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe
-
Size
239KB
-
MD5
3464c6b50ffdf4e9cad35a423868fa17
-
SHA1
4911e2fd81a78c402c0638b6705e26af73deb3d1
-
SHA256
85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db
-
SHA512
86750a9c8b4221075fc133301502ebae2d138bc153463afd368afd0999661343d8e0585d72247e0ac000d0a7cf9e6d0e6a167a2eb7ab07abda030cdcc3214394
-
SSDEEP
6144:ZcGxpvsROEOLDqckHsbCzHGthxud5jJX/bCvqiyXSVI:rvsoDdkHRjSs5/+vqiyXn
Malware Config
Extracted
xenorat
91.92.248.167
Dolid_rat_nd8859g
-
delay
60000
-
install_path
appdata
-
port
1280
-
startup_name
dms
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-2494989678-839960665-2515455429-1000\Control Panel\International\Geo\Nation 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe -
Executes dropped EXE 4 IoCs
pid Process 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 1992 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 1372 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 4600 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe -
Suspicious use of SetThreadContext 6 IoCs
description pid Process procid_target PID 3060 set thread context of 2944 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 83 PID 3060 set thread context of 3120 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 84 PID 3060 set thread context of 1488 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 85 PID 1476 set thread context of 1992 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 92 PID 1476 set thread context of 1372 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 93 PID 1476 set thread context of 4600 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 94 -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s).
-
Program crash 2 IoCs
pid pid_target Process procid_target 932 3120 WerFault.exe 84 3484 1488 WerFault.exe 85 -
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 1492 schtasks.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeDebugPrivilege 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe Token: SeDebugPrivilege 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe -
Suspicious use of UnmapMainImage 1 IoCs
pid Process 3120 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe -
Suspicious use of WriteProcessMemory 54 IoCs
description pid Process procid_target PID 3060 wrote to memory of 2944 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 83 PID 3060 wrote to memory of 2944 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 83 PID 3060 wrote to memory of 2944 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 83 PID 3060 wrote to memory of 2944 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 83 PID 3060 wrote to memory of 2944 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 83 PID 3060 wrote to memory of 2944 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 83 PID 3060 wrote to memory of 2944 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 83 PID 3060 wrote to memory of 2944 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 83 PID 3060 wrote to memory of 3120 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 84 PID 3060 wrote to memory of 3120 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 84 PID 3060 wrote to memory of 3120 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 84 PID 3060 wrote to memory of 3120 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 84 PID 3060 wrote to memory of 3120 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 84 PID 3060 wrote to memory of 3120 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 84 PID 3060 wrote to memory of 3120 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 84 PID 3060 wrote to memory of 3120 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 84 PID 3060 wrote to memory of 1488 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 85 PID 3060 wrote to memory of 1488 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 85 PID 3060 wrote to memory of 1488 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 85 PID 3060 wrote to memory of 1488 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 85 PID 3060 wrote to memory of 1488 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 85 PID 3060 wrote to memory of 1488 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 85 PID 3060 wrote to memory of 1488 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 85 PID 3060 wrote to memory of 1488 3060 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 85 PID 2944 wrote to memory of 1476 2944 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 91 PID 2944 wrote to memory of 1476 2944 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 91 PID 2944 wrote to memory of 1476 2944 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 91 PID 1476 wrote to memory of 1992 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 92 PID 1476 wrote to memory of 1992 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 92 PID 1476 wrote to memory of 1992 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 92 PID 1476 wrote to memory of 1992 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 92 PID 1476 wrote to memory of 1992 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 92 PID 1476 wrote to memory of 1992 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 92 PID 1476 wrote to memory of 1992 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 92 PID 1476 wrote to memory of 1992 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 92 PID 1476 wrote to memory of 1372 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 93 PID 1476 wrote to memory of 1372 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 93 PID 1476 wrote to memory of 1372 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 93 PID 1476 wrote to memory of 1372 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 93 PID 1476 wrote to memory of 1372 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 93 PID 1476 wrote to memory of 1372 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 93 PID 1476 wrote to memory of 1372 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 93 PID 1476 wrote to memory of 1372 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 93 PID 1476 wrote to memory of 4600 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 94 PID 1476 wrote to memory of 4600 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 94 PID 1476 wrote to memory of 4600 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 94 PID 1476 wrote to memory of 4600 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 94 PID 1476 wrote to memory of 4600 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 94 PID 1476 wrote to memory of 4600 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 94 PID 1476 wrote to memory of 4600 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 94 PID 1476 wrote to memory of 4600 1476 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 94 PID 1992 wrote to memory of 1492 1992 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 97 PID 1992 wrote to memory of 1492 1992 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 97 PID 1992 wrote to memory of 1492 1992 85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe 97
Processes
-
C:\Users\Admin\AppData\Local\Temp\85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe"C:\Users\Admin\AppData\Local\Temp\85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:3060 -
C:\Users\Admin\AppData\Local\Temp\85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exeC:\Users\Admin\AppData\Local\Temp\85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe2⤵
- Checks computer location settings
- Suspicious use of WriteProcessMemory
PID:2944 -
C:\Users\Admin\AppData\Roaming\XenoManager\85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe"C:\Users\Admin\AppData\Roaming\XenoManager\85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe"3⤵
- Executes dropped EXE
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:1476 -
C:\Users\Admin\AppData\Roaming\XenoManager\85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exeC:\Users\Admin\AppData\Roaming\XenoManager\85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe4⤵
- Executes dropped EXE
- Suspicious use of WriteProcessMemory
PID:1992 -
C:\Windows\SysWOW64\schtasks.exe"schtasks.exe" /Create /TN "dms" /XML "C:\Users\Admin\AppData\Local\Temp\tmp98D0.tmp" /F5⤵
- Scheduled Task/Job: Scheduled Task
PID:1492
-
-
-
C:\Users\Admin\AppData\Roaming\XenoManager\85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exeC:\Users\Admin\AppData\Roaming\XenoManager\85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe4⤵
- Executes dropped EXE
PID:1372
-
-
C:\Users\Admin\AppData\Roaming\XenoManager\85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exeC:\Users\Admin\AppData\Roaming\XenoManager\85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe4⤵
- Executes dropped EXE
PID:4600
-
-
-
-
C:\Users\Admin\AppData\Local\Temp\85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exeC:\Users\Admin\AppData\Local\Temp\85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe2⤵
- Suspicious use of UnmapMainImage
PID:3120 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3120 -s 123⤵
- Program crash
PID:932
-
-
-
C:\Users\Admin\AppData\Local\Temp\85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exeC:\Users\Admin\AppData\Local\Temp\85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe2⤵PID:1488
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1488 -s 803⤵
- Program crash
PID:3484
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 432 -p 3120 -ip 31201⤵PID:2908
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 416 -p 1488 -ip 14881⤵PID:3972
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe.log
Filesize522B
MD58334a471a4b492ece225b471b8ad2fc8
SHA11cb24640f32d23e8f7800bd0511b7b9c3011d992
SHA2565612afe347d8549cc95a0c710602bcc7d7b224361b613c0a6ba362092300c169
SHA51256ae2e83355c331b00d782797f5664c2f373eac240e811aab978732503ae05eb20b08730d2427ed90efa5a706d71b42b57153596a45a6b5592e3dd9128b81c36
-
Filesize
1KB
MD5acb7f704bb45606121288777ffcbb148
SHA11c36bf1e63a32a5178ccda10e0d6b759e903877f
SHA256af28055804dc2c7e082591db739b04e820bfb4cf0f8a60d05b5a7951ac5a3e62
SHA512ba1c22e4841329e69478ce9f733bb1637686e9aeefc00e0b7f74a73e99f2d7f9ca2b852cdf0ec12c680b6a9d9b7793b76d449d93d8872c576fb598bdf937e150
-
C:\Users\Admin\AppData\Roaming\XenoManager\85eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db.exe
Filesize239KB
MD53464c6b50ffdf4e9cad35a423868fa17
SHA14911e2fd81a78c402c0638b6705e26af73deb3d1
SHA25685eeb40d3c63e7452b85dd1f64ad8c6a959baf5f392719ee709d8093404782db
SHA51286750a9c8b4221075fc133301502ebae2d138bc153463afd368afd0999661343d8e0585d72247e0ac000d0a7cf9e6d0e6a167a2eb7ab07abda030cdcc3214394