Executive Overview — What We’re Dealing With

This specimen has persisted long enough to matter. Human experts classified it as Malware, and the telemetry confirms a capable, evasive Trojan with real impact potential.

Extended Dwell Time Impact

For 17+ hours, this malware remained undetected — a half-day window that permitted the adversary to complete initial execution, establish basic persistence, and perform initial system enumeration.

Global Detection Posture — Who Caught It, Who Missed It

VirusTotal engines: 73. Detected as malicious: 58. Missed: 15. Coverage: 79.5%.

Why it matters: if any endpoint relies solely on a missed engine, this malware can operate with zero alerts. Prevention‑first controls close that gap regardless of signature lag.

Behavioral Storyline — How the Malware Operates

This threat shows heavy registry manipulation (34.30% of total behavior), indicating persistent backdoor installation, configuration tampering, or system policy modification attempts. The malware likely establishes persistence mechanisms and modifies security settings to maintain long-term access.

MITRE ATT&CK Mapping

• T1027 – encode data using Base64
• T1620 – invoke .NET assembly method
• T1620 – load .NET assembly
• T1003 – Accessed credential storage registry keys
• T1564 – A process created a hidden window
• T1202 – Uses suspicious command line tools or Windows utilities
• T1202 – Uses Windows utilities for basic functionality
• T1112 – Stores JavaScript or a script command in the registry, likely for fileless persistence
• T1070 – Deletes executed files from disk
• T1064 – A powershell command using multiple variables was executed possibly indicative of obfuscation
• T1064 – Attempts to execute suspicious powershell command arguments
• T1064 – A scripting utility was executed
• T1497 – Checks the version of Bios, possibly for anti-virtualization
• T1497 – Detects VirtualBox through the presence of a registry key
• T1497 – Detects the presence of Windows Defender AV emulator via files
• T1027 – A powershell command using multiple variables was executed possibly indicative of obfuscation
• T1027 – The binary likely contains encrypted or compressed data
• T1564.003 – A process created a hidden window
• T1027.002 – The binary likely contains encrypted or compressed data
• T1082 – Checks the version of Bios, possibly for anti-virtualization
• T1082 – Checks available memory
• T1082 – Access the NetLogon registry key, potentially used for discovery or tampering
• T1010 – Checks for the presence of known windows from debuggers and forensic tools
• T1083 – Detects the presence of Windows Defender AV emulator via files
• T1083 – Attempts to identify installed AV products by installation directory
• T1083 – Checks for the presence of known devices from debuggers and forensic tools
• T1057 – Checks the version of Bios, possibly for anti-virtualization
• T1057 – Detects the presence of Windows Defender AV emulator via files
• T1057 – Checks for the presence of known windows from debuggers and forensic tools
• T1057 – Detects VirtualBox through the presence of a registry key
• T1057 – Enumerates the modules from a process (may be used to locate base addresses in process injection)
• T1057 – Expresses interest in specific running processes
• T1057 – Checks for the presence of known devices from debuggers and forensic tools
• T1057 – Detects the presence of Wine emulator via registry key
• T1012 – Checks the version of Bios, possibly for anti-virtualization
• T1012 – Detects VirtualBox through the presence of a registry key
• T1012 – Access the NetLogon registry key, potentially used for discovery or tampering
• T1012 – Detects the presence of Wine emulator via registry key
• T1518.001 – Attempts to identify installed AV products by installation directory
• T1518 – Attempts to identify installed AV products by installation directory
• T1518 – Detects the presence of Windows Defender AV emulator via files
• T1518 – Detects the presence of Wine emulator via registry key
• T1071 – HTTP traffic contains suspicious features which may be indicative of malware related traffic
• T1071 – Makes a suspicious HTTP request to a commonly exploitable directory with questionable file ext
• T1071 – At least one IP Address, Domain, or File Name was found in a crypto call
• T1071 – Performs HTTP requests potentially not found in PCAP.
• T1071 – Executable is attempted to be downloaded from an IP
• T1071 – Resolves a suspicious Top Level Domain (TLD)
• T1071 – Attempts to connect to a dead IP:Port
• T1071 – A process attempted to delay the analysis task.
• T1071 – Reads data out of its own binary image
• T1071 – Reads from the memory of another process
• T1071 – Yara detections observed in process dumps, payloads or dropped files
• T1573 – Establishes an encrypted HTTPS connection
• T1106 – Guard pages use detected – possible anti-debugging.
• T1059 – Stores JavaScript or a script command in the registry, likely for fileless persistence
• T1059 – A script or command line contains a long continuous string indicative of obfuscation
• T1059 – A scripting utility was executed
• T1059 – Executed a very long command line or script command which may be indicative of chained commands or obfuscation
• T1059 – A powershell command using multiple variables was executed possibly indicative of obfuscation
• T1059 – Attempts to execute suspicious powershell command arguments
• T1059 – Executed a command line with /C or /R argument to terminate command shell on completion which can be used to hide execution
• T1059.001 – A powershell command using multiple variables was executed possibly indicative of obfuscation
• T1059.001 – Attempts to execute suspicious powershell command arguments
• T1007 – Collects information about services
• T1027.002 – Resolves API functions dynamically
• T1059.001 – Bypasses PowerShell execution policy
• T1112 – Installs system service
• T1480 – Known malicious mutex name is created
• T1543.003 – Installs system service
• T1564.003 – Creates process with hidden window
• T1574.011 – Hijack installed services
• T1574.011 – Installs system service
• T1082 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1033 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1087 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1620 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1083 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1560.002 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1056.001 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1213 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1027 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1113 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1057 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1105 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1614.001 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1047 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1140 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1012 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1112 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1518 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1129 – The process attempted to dynamically load a malicious function
• T1059 – Detected command line output monitoring
• T1082 – Detected an attempt to hide a thread from the debugger using the NtSetInformationThread function
• T1033 – Detected an attempt to hide a thread from the debugger using the NtSetInformationThread function
• T1087 – Detected an attempt to hide a thread from the debugger using the NtSetInformationThread function
• T1620 – Detected an attempt to hide a thread from the debugger using the NtSetInformationThread function
• T1083 – Detected an attempt to hide a thread from the debugger using the NtSetInformationThread function
• T1560.002 – Detected an attempt to hide a thread from the debugger using the NtSetInformationThread function
• T1056.001 – Detected an attempt to hide a thread from the debugger using the NtSetInformationThread function
• T1213 – Detected an attempt to hide a thread from the debugger using the NtSetInformationThread function
• T1027 – Detected an attempt to hide a thread from the debugger using the NtSetInformationThread function
• T1113 – Detected an attempt to hide a thread from the debugger using the NtSetInformationThread function
• T1057 – Detected an attempt to hide a thread from the debugger using the NtSetInformationThread function
• T1105 – Detected an attempt to hide a thread from the debugger using the NtSetInformationThread function
• T1614.001 – Detected an attempt to hide a thread from the debugger using the NtSetInformationThread function
• T1047 – Detected an attempt to hide a thread from the debugger using the NtSetInformationThread function
• T1140 – Detected an attempt to hide a thread from the debugger using the NtSetInformationThread function
• T1012 – Detected an attempt to hide a thread from the debugger using the NtSetInformationThread function
• T1112 – Detected an attempt to hide a thread from the debugger using the NtSetInformationThread function
• T1518 – Detected an attempt to hide a thread from the debugger using the NtSetInformationThread function
• T1057 – The process may have looked for a particular process running on the system
• T1129 – The process tried to load dynamically one or more functions.
• T1564.003 – Detected the creation of a hidden window (common execution hiding technique)
• T1057 – The process has tried to detect the debugger probing the use of page guards.
• T1027.009 – The process has executed a dropped binary
• T1071 – Detected one or more anomalous HTTP requests
• T1071 – Detected HTTP requests to some non white-listed domains
• T1057 – The process attempted to detect a running debugger using common APIs
• T1082 – Queries for the computername
• T1082 – A process attempted to delay the analysis task by a long amount of time.
• T1033 – A process attempted to delay the analysis task by a long amount of time.
• T1087 – A process attempted to delay the analysis task by a long amount of time.
• T1620 – A process attempted to delay the analysis task by a long amount of time.
• T1083 – A process attempted to delay the analysis task by a long amount of time.
• T1560.002 – A process attempted to delay the analysis task by a long amount of time.
• T1056.001 – A process attempted to delay the analysis task by a long amount of time.
• T1213 – A process attempted to delay the analysis task by a long amount of time.
• T1027 – A process attempted to delay the analysis task by a long amount of time.
• T1113 – A process attempted to delay the analysis task by a long amount of time.
• T1057 – A process attempted to delay the analysis task by a long amount of time.
• T1105 – A process attempted to delay the analysis task by a long amount of time.
• T1614.001 – A process attempted to delay the analysis task by a long amount of time.
• T1047 – A process attempted to delay the analysis task by a long amount of time.
• T1140 – A process attempted to delay the analysis task by a long amount of time.
• T1012 – A process attempted to delay the analysis task by a long amount of time.
• T1112 – A process attempted to delay the analysis task by a long amount of time.
• T1518 – A process attempted to delay the analysis task by a long amount of time.
• T1119 – The process tried to detect the presence of common debug and forensic utilities
• T1063 – The process tried to detect the presence of common debug and forensic utilities
• T1063 – The process attempted to detect some widespread AVs presence looking at their installation directories
• T1119 – The process attempted to detect debuggers and common forensic/analysis tools looking for known devices
• T1063 – The process attempted to detect debuggers and common forensic/analysis tools looking for known devices
• T1082 – The process has tried to retrieve the BIOS version (maybe for checking the virtualization presence)
• T1012 – The process has tried to retrieve the BIOS version (maybe for checking the virtualization presence)
• T1086 – Detected some PowerShell commands executions
• T1060 – The process has tried to set its autorun on the system startup
• T1112 – The process has tried to set its autorun on the system startup
• T1050 – The process has tried to set its autorun on the system startup
• T1027.009 – Drops interesting files and uses them
• T1053 – Uses schtasks.exe or at.exe to add and modify task schedules
• T1059.001 – Bypasses PowerShell execution policy
• T1543.003 – Creates or modifies windows services
• T1542.003 – May use bcdedit to modify the Windows boot settings
• T1574.010 – Uses cacls to modify the permissions of files
• T1055 – May try to detect the Windows Explorer process (often used for injection)
• T1036 – Drops a PE files to the windows directory (C:\\Windows) and starts it
• T1036 – Drops PE files to the windows directory (C:\\Windows)
• T1036 – Drops files with a non matching file extension (content does not match to file extension)
• T1036 – Creates files inside the user directory
• T1036 – Creates files inside the system directory
• T1562.001 – Creates guard pages, often used to prevent reverse engineering and debugging
• T1497 – May sleep (evasive loops) to hinder dynamic analysis
• T1497 – Hides threads from debuggers
• T1497 – Allocates memory with a write watch (potentially for evading sandboxes)
• T1497 – Checks for debuggers (window names)
• T1497 – Checks if the current process is being debugged
• T1497 – Contains capabilities to detect virtual machines
• T1497 – Checks for debuggers (devices)
• T1027 – PE file has a high occurrence of arithmetic instructions at the PE entrypoint (possbibily packed)
• T1027 – Binary may include packed or crypted data
• T1027.002 – PE file has section (not .text) which is very likely to contain packed code (zlib compression ratio < 0.011)
• T1027.002 – Binary may include packed or crypted data
• T1518.001 – Tries to detect virtualization through RDTSC time measurements
• T1518.001 – Hides threads from debuggers
• T1518.001 – Checks for debuggers (window names)
• T1518.001 – Tries to detect sandboxes / dynamic malware analysis system (registry check)
• T1518.001 – Checks if the current process is being debugged
• T1518.001 – Tries to evade debugger and weak emulator (self modifying code)
• T1518.001 – Contains capabilities to detect virtual machines
• T1518.001 – Checks for debuggers (devices)
• T1057 – Queries a list of all running processes
• T1057 – May try to detect the Windows Explorer process (often used for injection)
• T1082 – Tries to detect virtualization through RDTSC time measurements
• T1082 – Queries the volume information (name, serial number etc) of a device
• T1082 – Tries to evade debugger and weak emulator (self modifying code)
• T1021.001 – Contains functionality to start a terminal service
• T1105 – Downloads files from webservers via HTTP
• T1105 – Downloads executable code via HTTP
• T1095 – Downloads files from webservers via HTTP
• T1095 – Posts data to webserver
• T1071 – Downloads files from webservers via HTTP
• T1071 – Posts data to webserver
• T1071 – Downloads executable code via HTTP
• T1071 – C2 URLs / IPs found in malware configuration

Following the Trail — Network & DNS Activity

Outbound activity leans on reputable infrastructure (e.g., CDNs, cloud endpoints) to blend in. TLS sessions and
HTTP calls show routine beaconing and IP‑lookup behavior that can masquerade as normal browsing.

Hunting tip: alert on unknown binaries initiating TLS to IP‑lookup services or unusual CDN endpoints — especially early in execution.