Analysis
-
max time kernel
141s -
max time network
150s -
platform
windows10-2004_x64 -
resource
win10v2004-20240508-en -
resource tags
arch:x64arch:x86image:win10v2004-20240508-enlocale:en-usos:windows10-2004-x64system -
submitted
15-05-2024 16:18
Static task
static1
Behavioral task
behavioral1
Sample
3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe
Resource
win7-20240508-en
General
-
Target
3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe
-
Size
242KB
-
MD5
f36fa3a72893c4151b136426119ad589
-
SHA1
2f83d91056d831a40182c743c36fab2622be8906
-
SHA256
3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885
-
SHA512
fa51532d7257fb7e71a2f5f9091350086c1772dc5458b572674071c25288b80b205bf17db271e58e11e45d930f4c1745938e45068125bf92b29fd8ca3e6859ff
-
SSDEEP
6144:hcBzA6kEHVMRfmlOSdqadv5fdvW5S7w1ofkPAyDEqClNdzI:SBTkEHS8dqidvL7/cPAyDEqClN6
Malware Config
Extracted
xenorat
dns.dobiamfollollc.online
Solid_rat_nd8889g
-
delay
61000
-
install_path
appdata
-
port
1283
-
startup_name
bns
Signatures
-
Detects XenoRAT malware 1 IoCs
XenoRAT is an open-source remote access tool (RAT) developed in C#.
Processes:
resource yara_rule behavioral2/memory/820-9-0x0000000000400000-0x0000000000412000-memory.dmp XenoRAT -
Checks computer location settings 2 TTPs 1 IoCs
Looks up country code configured in the registry, likely geofence.
Processes:
3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exedescription ioc process Key value queried \REGISTRY\USER\S-1-5-21-1337824034-2731376981-3755436523-1000\Control Panel\International\Geo\Nation 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe -
Executes dropped EXE 4 IoCs
Processes:
3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exepid process 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 4696 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 1460 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 2020 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe -
Suspicious use of SetThreadContext 6 IoCs
Processes:
3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exedescription pid process target process PID 3636 set thread context of 820 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 set thread context of 4616 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 set thread context of 4104 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 set thread context of 4696 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 set thread context of 1460 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 set thread context of 2020 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s).
-
Program crash 3 IoCs
Processes:
WerFault.exeWerFault.exeWerFault.exepid pid_target process target process 3580 4616 WerFault.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 748 4104 WerFault.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 1820 1460 WerFault.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe -
Creates scheduled task(s) 1 TTPs 1 IoCs
Schtasks is often used by malware for persistence or to perform post-infection execution.
-
Suspicious use of AdjustPrivilegeToken 2 IoCs
Processes:
3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exedescription pid process Token: SeDebugPrivilege 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe Token: SeDebugPrivilege 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe -
Suspicious use of WriteProcessMemory 54 IoCs
Processes:
3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exedescription pid process target process PID 3636 wrote to memory of 820 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 wrote to memory of 820 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 wrote to memory of 820 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 wrote to memory of 820 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 wrote to memory of 820 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 wrote to memory of 820 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 wrote to memory of 820 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 wrote to memory of 820 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 wrote to memory of 4616 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 wrote to memory of 4616 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 wrote to memory of 4616 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 wrote to memory of 4616 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 wrote to memory of 4616 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 wrote to memory of 4616 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 wrote to memory of 4616 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 wrote to memory of 4616 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 wrote to memory of 4104 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 wrote to memory of 4104 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 wrote to memory of 4104 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 wrote to memory of 4104 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 wrote to memory of 4104 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 wrote to memory of 4104 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 wrote to memory of 4104 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 3636 wrote to memory of 4104 3636 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 820 wrote to memory of 2536 820 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 820 wrote to memory of 2536 820 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 820 wrote to memory of 2536 820 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 wrote to memory of 4696 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 wrote to memory of 4696 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 wrote to memory of 4696 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 wrote to memory of 4696 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 wrote to memory of 4696 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 wrote to memory of 4696 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 wrote to memory of 4696 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 wrote to memory of 4696 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 wrote to memory of 1460 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 wrote to memory of 1460 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 wrote to memory of 1460 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 wrote to memory of 1460 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 wrote to memory of 1460 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 wrote to memory of 1460 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 wrote to memory of 1460 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 wrote to memory of 1460 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 wrote to memory of 2020 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 wrote to memory of 2020 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 wrote to memory of 2020 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 wrote to memory of 2020 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 wrote to memory of 2020 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 wrote to memory of 2020 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 wrote to memory of 2020 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 2536 wrote to memory of 2020 2536 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe PID 4696 wrote to memory of 2420 4696 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe schtasks.exe PID 4696 wrote to memory of 2420 4696 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe schtasks.exe PID 4696 wrote to memory of 2420 4696 3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe schtasks.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe"C:\Users\Admin\AppData\Local\Temp\3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:3636 -
C:\Users\Admin\AppData\Local\Temp\3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exeC:\Users\Admin\AppData\Local\Temp\3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe2⤵
- Checks computer location settings
- Suspicious use of WriteProcessMemory
PID:820 -
C:\Users\Admin\AppData\Roaming\XenoManager\3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe"C:\Users\Admin\AppData\Roaming\XenoManager\3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe"3⤵
- Executes dropped EXE
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:2536 -
C:\Users\Admin\AppData\Roaming\XenoManager\3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exeC:\Users\Admin\AppData\Roaming\XenoManager\3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe4⤵
- Executes dropped EXE
- Suspicious use of WriteProcessMemory
PID:4696 -
C:\Windows\SysWOW64\schtasks.exe"schtasks.exe" /Create /TN "bns" /XML "C:\Users\Admin\AppData\Local\Temp\tmp393B.tmp" /F5⤵
- Creates scheduled task(s)
PID:2420 -
C:\Users\Admin\AppData\Roaming\XenoManager\3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exeC:\Users\Admin\AppData\Roaming\XenoManager\3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe4⤵
- Executes dropped EXE
PID:1460 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1460 -s 805⤵
- Program crash
PID:1820 -
C:\Users\Admin\AppData\Roaming\XenoManager\3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exeC:\Users\Admin\AppData\Roaming\XenoManager\3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe4⤵
- Executes dropped EXE
PID:2020 -
C:\Users\Admin\AppData\Local\Temp\3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exeC:\Users\Admin\AppData\Local\Temp\3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe2⤵PID:4616
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4616 -s 803⤵
- Program crash
PID:3580 -
C:\Users\Admin\AppData\Local\Temp\3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exeC:\Users\Admin\AppData\Local\Temp\3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe2⤵PID:4104
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4104 -s 803⤵
- Program crash
PID:748
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 444 -p 4104 -ip 41041⤵PID:4484
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 4616 -ip 46161⤵PID:1464
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 484 -p 1460 -ip 14601⤵PID:1560
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exe.logFilesize
706B
MD5d95c58e609838928f0f49837cab7dfd2
SHA155e7139a1e3899195b92ed8771d1ca2c7d53c916
SHA2560407c814aef0d62aec7fd39b7c2f614746f0d8ff41f8ef957736f520f14b0339
SHA512405310b29a833604c6627063bfdcf055a197e01f633ef21da238f1a6415a02e21315d689b4a6669db23e82152bed6f3492afb60963e6b2a0e9bb2ac09a480b5d
-
C:\Users\Admin\AppData\Local\Temp\tmp393B.tmpFilesize
1KB
MD59b05c5958cee2ceb4bb051937fddcc44
SHA17c0b5da9cff16e740daee26610581c768d49582b
SHA256a03642a9df011d976bb74d8f29908fe6c3245084c37bcc00d42b60139579a818
SHA5127a6a7db0309cd4e5dd835b9bef55cdffd562a6d41d54091c8e0404e47be3e3a924be2bcb83746b18eb344ba5ee2b80c9c7f5657f2fb327320b4fb5021a2c92c7
-
C:\Users\Admin\AppData\Roaming\XenoManager\3f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885.exeFilesize
242KB
MD5f36fa3a72893c4151b136426119ad589
SHA12f83d91056d831a40182c743c36fab2622be8906
SHA2563f2490dd9d05980a4b02f6b5e6e9c18f349cc4192a4733374318c20bc7f0a885
SHA512fa51532d7257fb7e71a2f5f9091350086c1772dc5458b572674071c25288b80b205bf17db271e58e11e45d930f4c1745938e45068125bf92b29fd8ca3e6859ff
-
memory/820-9-0x0000000000400000-0x0000000000412000-memory.dmpFilesize
72KB
-
memory/820-27-0x0000000075240000-0x00000000759F0000-memory.dmpFilesize
7.7MB
-
memory/820-12-0x0000000075240000-0x00000000759F0000-memory.dmpFilesize
7.7MB
-
memory/2536-36-0x0000000075240000-0x00000000759F0000-memory.dmpFilesize
7.7MB
-
memory/2536-29-0x0000000075240000-0x00000000759F0000-memory.dmpFilesize
7.7MB
-
memory/2536-28-0x0000000075240000-0x00000000759F0000-memory.dmpFilesize
7.7MB
-
memory/3636-4-0x00000000050D0000-0x0000000005110000-memory.dmpFilesize
256KB
-
memory/3636-8-0x00000000062F0000-0x00000000062F6000-memory.dmpFilesize
24KB
-
memory/3636-15-0x0000000075240000-0x00000000759F0000-memory.dmpFilesize
7.7MB
-
memory/3636-7-0x00000000063B0000-0x0000000006442000-memory.dmpFilesize
584KB
-
memory/3636-6-0x0000000006960000-0x0000000006F04000-memory.dmpFilesize
5.6MB
-
memory/3636-5-0x0000000006310000-0x00000000063AC000-memory.dmpFilesize
624KB
-
memory/3636-0-0x000000007524E000-0x000000007524F000-memory.dmpFilesize
4KB
-
memory/3636-3-0x0000000075240000-0x00000000759F0000-memory.dmpFilesize
7.7MB
-
memory/3636-2-0x0000000002A90000-0x0000000002A96000-memory.dmpFilesize
24KB
-
memory/3636-1-0x0000000000630000-0x0000000000676000-memory.dmpFilesize
280KB