Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
149s -
max time network
157s -
platform
windows10-2004_x64 -
resource
win10v2004-20240226-en -
resource tags
arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system -
submitted
15/05/2024, 01:44
Static task
static1
Behavioral task
behavioral1
Sample
b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe
Resource
win7-20240221-en
General
-
Target
b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe
-
Size
243KB
-
MD5
675943378edf65821651532354a211f7
-
SHA1
bb3ad849880cc1ca9f946e7c3d56b605132cab68
-
SHA256
b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46
-
SHA512
6d6ea3b7503d4be8b14217cb1f919404eb5cdfd2d546535c14ed75835293bfd9c2a6564b54cb8ea4487b7d49a4db75d1aafc5f022ea01c58c96d60d8b2ee0bc9
-
SSDEEP
6144:1surFANhoBJbRZlFOKC1XozQ9I1Qcti4a/ME46/QqBwdhHGPxMNI:KurFANSLdpOb14zQ9wI/Mf6tBwdhHGPZ
Malware Config
Extracted
xenorat
dns.dobiamfollollc.online
Solid_rat_nd8889g
-
delay
61000
-
install_path
appdata
-
port
1283
-
startup_name
bns
Signatures
-
Detects executables packed with ConfuserEx Mod 3 IoCs
resource yara_rule behavioral2/memory/4140-1-0x0000000000370000-0x00000000003B6000-memory.dmp INDICATOR_EXE_Packed_ConfuserEx behavioral2/memory/4140-4-0x0000000004DA0000-0x0000000004DE0000-memory.dmp INDICATOR_EXE_Packed_ConfuserEx behavioral2/files/0x0008000000023242-21.dat INDICATOR_EXE_Packed_ConfuserEx -
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-3808065738-1666277613-1125846146-1000\Control Panel\International\Geo\Nation b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe -
Executes dropped EXE 4 IoCs
pid Process 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 1212 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 3584 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 1864 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe -
Suspicious use of SetThreadContext 6 IoCs
description pid Process procid_target PID 4140 set thread context of 1108 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 90 PID 4140 set thread context of 1096 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 91 PID 4140 set thread context of 2340 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 92 PID 4176 set thread context of 1212 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 97 PID 4176 set thread context of 3584 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 98 PID 4176 set thread context of 1864 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.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 3380 2340 WerFault.exe 92 -
Creates scheduled task(s) 1 TTPs 1 IoCs
Schtasks is often used by malware for persistence or to perform post-infection execution.
pid Process 1968 schtasks.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeDebugPrivilege 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe Token: SeDebugPrivilege 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe -
Suspicious use of WriteProcessMemory 54 IoCs
description pid Process procid_target PID 4140 wrote to memory of 1108 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 90 PID 4140 wrote to memory of 1108 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 90 PID 4140 wrote to memory of 1108 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 90 PID 4140 wrote to memory of 1108 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 90 PID 4140 wrote to memory of 1108 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 90 PID 4140 wrote to memory of 1108 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 90 PID 4140 wrote to memory of 1108 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 90 PID 4140 wrote to memory of 1108 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 90 PID 4140 wrote to memory of 1096 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 91 PID 4140 wrote to memory of 1096 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 91 PID 4140 wrote to memory of 1096 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 91 PID 4140 wrote to memory of 1096 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 91 PID 4140 wrote to memory of 1096 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 91 PID 4140 wrote to memory of 1096 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 91 PID 4140 wrote to memory of 1096 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 91 PID 4140 wrote to memory of 1096 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 91 PID 4140 wrote to memory of 2340 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 92 PID 4140 wrote to memory of 2340 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 92 PID 4140 wrote to memory of 2340 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 92 PID 4140 wrote to memory of 2340 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 92 PID 4140 wrote to memory of 2340 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 92 PID 4140 wrote to memory of 2340 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 92 PID 4140 wrote to memory of 2340 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 92 PID 4140 wrote to memory of 2340 4140 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 92 PID 1096 wrote to memory of 4176 1096 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 96 PID 1096 wrote to memory of 4176 1096 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 96 PID 1096 wrote to memory of 4176 1096 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 96 PID 4176 wrote to memory of 1212 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 97 PID 4176 wrote to memory of 1212 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 97 PID 4176 wrote to memory of 1212 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 97 PID 4176 wrote to memory of 1212 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 97 PID 4176 wrote to memory of 1212 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 97 PID 4176 wrote to memory of 1212 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 97 PID 4176 wrote to memory of 1212 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 97 PID 4176 wrote to memory of 1212 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 97 PID 4176 wrote to memory of 3584 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 98 PID 4176 wrote to memory of 3584 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 98 PID 4176 wrote to memory of 3584 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 98 PID 4176 wrote to memory of 3584 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 98 PID 4176 wrote to memory of 3584 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 98 PID 4176 wrote to memory of 3584 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 98 PID 4176 wrote to memory of 3584 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 98 PID 4176 wrote to memory of 3584 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 98 PID 4176 wrote to memory of 1864 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 99 PID 4176 wrote to memory of 1864 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 99 PID 4176 wrote to memory of 1864 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 99 PID 4176 wrote to memory of 1864 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 99 PID 4176 wrote to memory of 1864 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 99 PID 4176 wrote to memory of 1864 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 99 PID 4176 wrote to memory of 1864 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 99 PID 4176 wrote to memory of 1864 4176 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 99 PID 1108 wrote to memory of 1968 1108 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 109 PID 1108 wrote to memory of 1968 1108 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 109 PID 1108 wrote to memory of 1968 1108 b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe 109
Processes
-
C:\Users\Admin\AppData\Local\Temp\b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe"C:\Users\Admin\AppData\Local\Temp\b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:4140 -
C:\Users\Admin\AppData\Local\Temp\b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exeC:\Users\Admin\AppData\Local\Temp\b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe2⤵
- Suspicious use of WriteProcessMemory
PID:1108 -
C:\Windows\SysWOW64\schtasks.exe"schtasks.exe" /Create /TN "bns" /XML "C:\Users\Admin\AppData\Local\Temp\tmpB7F.tmp" /F3⤵
- Creates scheduled task(s)
PID:1968
-
-
-
C:\Users\Admin\AppData\Local\Temp\b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exeC:\Users\Admin\AppData\Local\Temp\b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe2⤵
- Checks computer location settings
- Suspicious use of WriteProcessMemory
PID:1096 -
C:\Users\Admin\AppData\Roaming\XenoManager\b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe"C:\Users\Admin\AppData\Roaming\XenoManager\b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe"3⤵
- Executes dropped EXE
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:4176 -
C:\Users\Admin\AppData\Roaming\XenoManager\b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exeC:\Users\Admin\AppData\Roaming\XenoManager\b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe4⤵
- Executes dropped EXE
PID:1212
-
-
C:\Users\Admin\AppData\Roaming\XenoManager\b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exeC:\Users\Admin\AppData\Roaming\XenoManager\b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe4⤵
- Executes dropped EXE
PID:3584
-
-
C:\Users\Admin\AppData\Roaming\XenoManager\b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exeC:\Users\Admin\AppData\Roaming\XenoManager\b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe4⤵
- Executes dropped EXE
PID:1864
-
-
-
-
C:\Users\Admin\AppData\Local\Temp\b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exeC:\Users\Admin\AppData\Local\Temp\b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe2⤵PID:2340
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2340 -s 1523⤵
- Program crash
PID:3380
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 2340 -ip 23401⤵PID:2880
-
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=4080 --field-trial-handle=2252,i,16504368816373493055,9578615028378602855,262144 --variations-seed-version /prefetch:81⤵PID:1836
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe.log
Filesize706B
MD5d95c58e609838928f0f49837cab7dfd2
SHA155e7139a1e3899195b92ed8771d1ca2c7d53c916
SHA2560407c814aef0d62aec7fd39b7c2f614746f0d8ff41f8ef957736f520f14b0339
SHA512405310b29a833604c6627063bfdcf055a197e01f633ef21da238f1a6415a02e21315d689b4a6669db23e82152bed6f3492afb60963e6b2a0e9bb2ac09a480b5d
-
Filesize
1KB
MD5a9b87881a2db6fd1f7aef007668a196c
SHA1be98eeeacf945c0006a3e068f2060b961be64ff2
SHA25674bbfb9905ebb96da29d9235f1bee94964bb921d626b743934953f369eba668a
SHA512f38965ebcb206bbe7d510e7c6defa9cb1b73ef0bbeca4bdff4499c76c845867fc84e82c68ecab5406b2c0b9c194ec1881e6a77c8efe45192020c371c964c43f7
-
C:\Users\Admin\AppData\Roaming\XenoManager\b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46.exe
Filesize243KB
MD5675943378edf65821651532354a211f7
SHA1bb3ad849880cc1ca9f946e7c3d56b605132cab68
SHA256b23e432607f98a398b19419f30eca5bdbca21b662ce18b882830bfef370a9a46
SHA5126d6ea3b7503d4be8b14217cb1f919404eb5cdfd2d546535c14ed75835293bfd9c2a6564b54cb8ea4487b7d49a4db75d1aafc5f022ea01c58c96d60d8b2ee0bc9