Analysis
-
max time kernel
127s -
max time network
137s -
platform
windows7_x64 -
resource
win7-20240220-en -
resource tags
arch:x64arch:x86image:win7-20240220-enlocale:en-usos:windows7-x64system -
submitted
15-05-2024 02:04
Static task
static1
Behavioral task
behavioral1
Sample
fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe
Resource
win7-20240220-en
General
-
Target
fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe
-
Size
242KB
-
MD5
33f2e874128d3a24588e1c89927042bd
-
SHA1
e206af96ff648951608eaf599627635ddff7ecd8
-
SHA256
fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7
-
SHA512
559dc3f6a0f9a6e762545b9683e265e4459b8623786c979c959d5d78dff7f4455fed72135fcccc966c10ba3d3588fcbf077a44091e3012743245dc41bfd1b3c5
-
SSDEEP
6144:gRRan2neJf5QvtapiSgICS86G3vsMP1i8FvEOPDv5bq1RFI:gRTeJf5mappgICS+3xPFvrPDv5bq1I
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 4 IoCs
resource yara_rule behavioral1/memory/1640-1-0x0000000000A00000-0x0000000000A46000-memory.dmp INDICATOR_EXE_Packed_ConfuserEx behavioral1/memory/1640-3-0x0000000000400000-0x0000000000440000-memory.dmp INDICATOR_EXE_Packed_ConfuserEx behavioral1/memory/2644-33-0x0000000001030000-0x0000000001076000-memory.dmp INDICATOR_EXE_Packed_ConfuserEx behavioral1/files/0x0031000000015d0a-31.dat INDICATOR_EXE_Packed_ConfuserEx -
Executes dropped EXE 4 IoCs
pid Process 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 2472 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 2792 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 3016 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe -
Loads dropped DLL 4 IoCs
pid Process 2544 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe -
Suspicious use of SetThreadContext 6 IoCs
description pid Process procid_target PID 1640 set thread context of 2544 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 28 PID 1640 set thread context of 2612 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 29 PID 1640 set thread context of 2404 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 30 PID 2644 set thread context of 2472 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 32 PID 2644 set thread context of 2792 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 33 PID 2644 set thread context of 3016 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 34 -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s).
-
Creates scheduled task(s) 1 TTPs 1 IoCs
Schtasks is often used by malware for persistence or to perform post-infection execution.
pid Process 1672 schtasks.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeDebugPrivilege 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe Token: SeDebugPrivilege 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe -
Suspicious use of WriteProcessMemory 62 IoCs
description pid Process procid_target PID 1640 wrote to memory of 2544 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 28 PID 1640 wrote to memory of 2544 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 28 PID 1640 wrote to memory of 2544 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 28 PID 1640 wrote to memory of 2544 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 28 PID 1640 wrote to memory of 2544 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 28 PID 1640 wrote to memory of 2544 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 28 PID 1640 wrote to memory of 2544 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 28 PID 1640 wrote to memory of 2544 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 28 PID 1640 wrote to memory of 2544 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 28 PID 1640 wrote to memory of 2612 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 29 PID 1640 wrote to memory of 2612 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 29 PID 1640 wrote to memory of 2612 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 29 PID 1640 wrote to memory of 2612 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 29 PID 1640 wrote to memory of 2612 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 29 PID 1640 wrote to memory of 2612 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 29 PID 1640 wrote to memory of 2612 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 29 PID 1640 wrote to memory of 2612 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 29 PID 1640 wrote to memory of 2612 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 29 PID 1640 wrote to memory of 2404 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 30 PID 1640 wrote to memory of 2404 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 30 PID 1640 wrote to memory of 2404 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 30 PID 1640 wrote to memory of 2404 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 30 PID 1640 wrote to memory of 2404 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 30 PID 1640 wrote to memory of 2404 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 30 PID 1640 wrote to memory of 2404 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 30 PID 1640 wrote to memory of 2404 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 30 PID 1640 wrote to memory of 2404 1640 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 30 PID 2544 wrote to memory of 2644 2544 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 31 PID 2544 wrote to memory of 2644 2544 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 31 PID 2544 wrote to memory of 2644 2544 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 31 PID 2544 wrote to memory of 2644 2544 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 31 PID 2644 wrote to memory of 2472 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 32 PID 2644 wrote to memory of 2472 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 32 PID 2644 wrote to memory of 2472 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 32 PID 2644 wrote to memory of 2472 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 32 PID 2644 wrote to memory of 2472 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 32 PID 2644 wrote to memory of 2472 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 32 PID 2644 wrote to memory of 2472 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 32 PID 2644 wrote to memory of 2472 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 32 PID 2644 wrote to memory of 2472 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 32 PID 2644 wrote to memory of 2792 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 33 PID 2644 wrote to memory of 2792 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 33 PID 2644 wrote to memory of 2792 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 33 PID 2644 wrote to memory of 2792 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 33 PID 2644 wrote to memory of 2792 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 33 PID 2644 wrote to memory of 2792 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 33 PID 2644 wrote to memory of 2792 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 33 PID 2644 wrote to memory of 2792 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 33 PID 2644 wrote to memory of 2792 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 33 PID 2644 wrote to memory of 3016 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 34 PID 2644 wrote to memory of 3016 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 34 PID 2644 wrote to memory of 3016 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 34 PID 2644 wrote to memory of 3016 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 34 PID 2644 wrote to memory of 3016 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 34 PID 2644 wrote to memory of 3016 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 34 PID 2644 wrote to memory of 3016 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 34 PID 2644 wrote to memory of 3016 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 34 PID 2644 wrote to memory of 3016 2644 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 34 PID 2612 wrote to memory of 1672 2612 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 37 PID 2612 wrote to memory of 1672 2612 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 37 PID 2612 wrote to memory of 1672 2612 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 37 PID 2612 wrote to memory of 1672 2612 fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe 37
Processes
-
C:\Users\Admin\AppData\Local\Temp\fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe"C:\Users\Admin\AppData\Local\Temp\fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:1640 -
C:\Users\Admin\AppData\Local\Temp\fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exeC:\Users\Admin\AppData\Local\Temp\fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe2⤵
- Loads dropped DLL
- Suspicious use of WriteProcessMemory
PID:2544 -
C:\Users\Admin\AppData\Roaming\XenoManager\fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe"C:\Users\Admin\AppData\Roaming\XenoManager\fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe"3⤵
- Executes dropped EXE
- Loads dropped DLL
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:2644 -
C:\Users\Admin\AppData\Roaming\XenoManager\fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exeC:\Users\Admin\AppData\Roaming\XenoManager\fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe4⤵
- Executes dropped EXE
PID:2472
-
-
C:\Users\Admin\AppData\Roaming\XenoManager\fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exeC:\Users\Admin\AppData\Roaming\XenoManager\fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe4⤵
- Executes dropped EXE
PID:2792
-
-
C:\Users\Admin\AppData\Roaming\XenoManager\fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exeC:\Users\Admin\AppData\Roaming\XenoManager\fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe4⤵
- Executes dropped EXE
PID:3016
-
-
-
-
C:\Users\Admin\AppData\Local\Temp\fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exeC:\Users\Admin\AppData\Local\Temp\fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe2⤵
- Suspicious use of WriteProcessMemory
PID:2612 -
C:\Windows\SysWOW64\schtasks.exe"schtasks.exe" /Create /TN "bns" /XML "C:\Users\Admin\AppData\Local\Temp\tmp963.tmp" /F3⤵
- Creates scheduled task(s)
PID:1672
-
-
-
C:\Users\Admin\AppData\Local\Temp\fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exeC:\Users\Admin\AppData\Local\Temp\fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe2⤵PID:2404
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
1KB
MD5cef9bd9ff86b1e2446b1cebe03185a75
SHA1adf01337b2168caa29c4c950501827ba8a78d6c8
SHA25692535d26ae4597d9a1ef1cc3b98344582e7f939a65f63accbeec32f534e91792
SHA512547e4c841eeb7051ef6974a859df85354fc39c12466d753af59a9cdbd34c2773f0949bc8a6088ea749d54dab4c5e7976b97b811d071288ecf6e5210cbb73ca3d
-
C:\Users\Admin\AppData\Roaming\XenoManager\fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7.exe
Filesize242KB
MD533f2e874128d3a24588e1c89927042bd
SHA1e206af96ff648951608eaf599627635ddff7ecd8
SHA256fbb251f9916a362e527e962c4e2b0950f75de2226f3e3092813fa35eb6392bb7
SHA512559dc3f6a0f9a6e762545b9683e265e4459b8623786c979c959d5d78dff7f4455fed72135fcccc966c10ba3d3588fcbf077a44091e3012743245dc41bfd1b3c5