Analysis
-
max time kernel
162s -
max time network
177s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
26-11-2022 21:55
Static task
static1
Behavioral task
behavioral1
Sample
27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe
Resource
win10v2004-20221111-en
General
-
Target
27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe
-
Size
1.2MB
-
MD5
fa6f8b21924d0288cc91e20e710608e0
-
SHA1
9cfc9f4e732aa278bb880cb1facb58849eb55a3e
-
SHA256
27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b
-
SHA512
aaef1619c519f6d570184ce936aeb0b3f5a8f4333e29259619eb7976e67351bc4fd8acac2c21b2075dd27ed57bbce8ba8fe72d8e04126006d2cfe5655223f839
-
SSDEEP
12288:ZF8e6ej5cQObE7oyWjEZsIWO1F5s8paXERJJKCQ:oen5Omp4EZsIWO1F5s8pa0RJJKC
Malware Config
Signatures
-
Luminosity
Luminosity is a RAT family that was on sale, while claiming to be a system administration utility.
-
Modifies WinLogon for persistence 2 TTPs 2 IoCs
Processes:
sysmon.exedescription ioc process Set value (str) \REGISTRY\MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Winlogon\Userinit = "userinit.exe,\"C:\\Windows\\system32\\clientsvr.exe\"" sysmon.exe Set value (str) \REGISTRY\USER\S-1-5-21-2386679933-1492765628-3466841596-1000\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\shell = "explorer.exe,\"C:\\ProgramData\\970790\\sysmon.exe\"" sysmon.exe -
Executes dropped EXE 3 IoCs
Processes:
sysmon.exesysmon.exesysmon.exepid process 3136 sysmon.exe 3928 sysmon.exe 3964 sysmon.exe -
Checks computer location settings 2 TTPs 1 IoCs
Looks up country code configured in the registry, likely geofence.
Processes:
27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exedescription ioc process Key value queried \REGISTRY\USER\S-1-5-21-2386679933-1492765628-3466841596-1000\Control Panel\International\Geo\Nation 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe -
Adds Run key to start application 2 TTPs 1 IoCs
Processes:
sysmon.exedescription ioc process Set value (str) \REGISTRY\USER\S-1-5-21-2386679933-1492765628-3466841596-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce\System Monitor = "\"C:\\ProgramData\\970790\\sysmon.exe\"" sysmon.exe -
Drops file in System32 directory 2 IoCs
Processes:
sysmon.exedescription ioc process File created C:\Windows\SysWOW64\clientsvr.exe sysmon.exe File opened for modification C:\Windows\SysWOW64\clientsvr.exe sysmon.exe -
Suspicious use of SetThreadContext 3 IoCs
Processes:
27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exesysmon.exedescription pid process target process PID 4000 set thread context of 3972 4000 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe PID 3136 set thread context of 3964 3136 sysmon.exe sysmon.exe PID 3136 set thread context of 3928 3136 sysmon.exe sysmon.exe -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Suspicious behavior: EnumeratesProcesses 64 IoCs
Processes:
sysmon.exe27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exepid process 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3972 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe 3972 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe 3964 sysmon.exe -
Suspicious behavior: RenamesItself 1 IoCs
Processes:
27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exepid process 3972 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
Processes:
sysmon.exedescription pid process Token: SeDebugPrivilege 3964 sysmon.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
Processes:
sysmon.exepid process 3964 sysmon.exe -
Suspicious use of WriteProcessMemory 27 IoCs
Processes:
27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exesysmon.exesysmon.exedescription pid process target process PID 4000 wrote to memory of 3972 4000 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe PID 4000 wrote to memory of 3972 4000 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe PID 4000 wrote to memory of 3972 4000 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe PID 4000 wrote to memory of 3972 4000 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe PID 4000 wrote to memory of 3972 4000 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe PID 4000 wrote to memory of 3972 4000 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe PID 4000 wrote to memory of 3972 4000 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe PID 4000 wrote to memory of 3972 4000 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe PID 3972 wrote to memory of 3136 3972 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe sysmon.exe PID 3972 wrote to memory of 3136 3972 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe sysmon.exe PID 3972 wrote to memory of 3136 3972 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe sysmon.exe PID 3136 wrote to memory of 3928 3136 sysmon.exe sysmon.exe PID 3136 wrote to memory of 3928 3136 sysmon.exe sysmon.exe PID 3136 wrote to memory of 3928 3136 sysmon.exe sysmon.exe PID 3136 wrote to memory of 3964 3136 sysmon.exe sysmon.exe PID 3136 wrote to memory of 3964 3136 sysmon.exe sysmon.exe PID 3136 wrote to memory of 3964 3136 sysmon.exe sysmon.exe PID 3136 wrote to memory of 3964 3136 sysmon.exe sysmon.exe PID 3136 wrote to memory of 3964 3136 sysmon.exe sysmon.exe PID 3136 wrote to memory of 3964 3136 sysmon.exe sysmon.exe PID 3136 wrote to memory of 3964 3136 sysmon.exe sysmon.exe PID 3136 wrote to memory of 3964 3136 sysmon.exe sysmon.exe PID 3964 wrote to memory of 3972 3964 sysmon.exe 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe PID 3964 wrote to memory of 3972 3964 sysmon.exe 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe PID 3964 wrote to memory of 3972 3964 sysmon.exe 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe PID 3964 wrote to memory of 3972 3964 sysmon.exe 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe PID 3964 wrote to memory of 3972 3964 sysmon.exe 27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe"C:\Users\Admin\AppData\Local\Temp\27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4000 -
C:\Users\Admin\AppData\Local\Temp\27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe"C:\Users\Admin\AppData\Local\Temp\27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe"2⤵
- Checks computer location settings
- Suspicious behavior: EnumeratesProcesses
- Suspicious behavior: RenamesItself
- Suspicious use of WriteProcessMemory
PID:3972 -
C:\ProgramData\970790\sysmon.exe"C:\ProgramData\970790\sysmon.exe"3⤵
- Executes dropped EXE
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3136 -
C:\ProgramData\970790\sysmon.exe"C:\ProgramData\970790\sysmon.exe"4⤵
- Executes dropped EXE
PID:3928
-
-
C:\ProgramData\970790\sysmon.exe"C:\ProgramData\970790\sysmon.exe"4⤵
- Modifies WinLogon for persistence
- Executes dropped EXE
- Adds Run key to start application
- Drops file in System32 directory
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3964
-
-
-
Network
MITRE ATT&CK Enterprise v6
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
1.2MB
MD5fa6f8b21924d0288cc91e20e710608e0
SHA19cfc9f4e732aa278bb880cb1facb58849eb55a3e
SHA25627fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b
SHA512aaef1619c519f6d570184ce936aeb0b3f5a8f4333e29259619eb7976e67351bc4fd8acac2c21b2075dd27ed57bbce8ba8fe72d8e04126006d2cfe5655223f839
-
Filesize
1.2MB
MD5fa6f8b21924d0288cc91e20e710608e0
SHA19cfc9f4e732aa278bb880cb1facb58849eb55a3e
SHA25627fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b
SHA512aaef1619c519f6d570184ce936aeb0b3f5a8f4333e29259619eb7976e67351bc4fd8acac2c21b2075dd27ed57bbce8ba8fe72d8e04126006d2cfe5655223f839
-
Filesize
1.2MB
MD5fa6f8b21924d0288cc91e20e710608e0
SHA19cfc9f4e732aa278bb880cb1facb58849eb55a3e
SHA25627fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b
SHA512aaef1619c519f6d570184ce936aeb0b3f5a8f4333e29259619eb7976e67351bc4fd8acac2c21b2075dd27ed57bbce8ba8fe72d8e04126006d2cfe5655223f839
-
Filesize
1.2MB
MD5fa6f8b21924d0288cc91e20e710608e0
SHA19cfc9f4e732aa278bb880cb1facb58849eb55a3e
SHA25627fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b
SHA512aaef1619c519f6d570184ce936aeb0b3f5a8f4333e29259619eb7976e67351bc4fd8acac2c21b2075dd27ed57bbce8ba8fe72d8e04126006d2cfe5655223f839
-
C:\Users\Admin\AppData\Local\Microsoft\CLR_v2.0_32\UsageLogs\27fada8a5998904fcbd5104d080b8295846ba0f1cb4c551d7b8179d30edc6b4b.exe.log
Filesize594B
MD5fdb26b3b547022b45cfaeee57eafd566
SHA111c6798b8a59233f404014c5e79b3363cd564b37
SHA2562707fc7f074413881b7bafca05079327b188db6005709951e7f69d39a2af97c0
SHA51244d9bb8c0f0b341690d00eda86e15a50f7f29ce9595925c1a2a7e19ad26202d10049a7a97bea278ecb7d429ad555de8edceeffff664d4b06309a9410a09bb700