Suspicious-File-Creation - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/tags/suspicious-file-creation/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioMon, 08 Jan 2024 12:00:00 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgExecutable or Script Creation in Suspicious Pathshttps://feed.craftedsignal.io/briefs/2024-01-08-suspicious-executable-creation/Mon, 08 Jan 2024 12:00:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-01-08-suspicious-executable-creation/Attackers may create executables or scripts in suspicious directories to establish persistence, execute malicious code, or evade detection by blending in with legitimate system activity.Attackers often create executable files (e.g., .exe, .dll, .ps1, .py) in unusual directories as part of their attack operations. This can be a way to establish persistence by placing a malicious script in a startup folder, or it could be a way to execute code while avoiding detection. Standard user directories like AppData, Temp, or Public are common targets because they often have relaxed security controls and are less scrutinized than system directories. This technique allows malicious actors to blend in with normal user activity. This type of behavior can be seen across various attack campaigns, from commodity malware to advanced persistent threats (APTs). Detecting these file creations is crucial for identifying compromised systems.

Attack Chain

  1. Initial Access: The attacker gains initial access through an exploit or social engineering.
  2. Privilege Escalation: The attacker escalates privileges to gain higher-level access to the system.
  3. Payload Delivery: The attacker downloads a malicious payload, often a script or executable.
  4. Suspicious Directory Creation: The attacker creates a new directory or uses an existing one in a suspicious location like C:\Users\Public\, C:\Windows\Temp\, or %AppData%.
  5. Executable/Script Creation: The attacker writes the malicious payload (e.g., a PowerShell script, batch file, or compiled executable) to the created or existing directory.
  6. Persistence: The attacker creates a scheduled task or modifies a registry key to execute the malicious script or executable automatically on system startup or user login.
  7. Command and Control: The malicious script or executable establishes a connection to a command-and-control server to receive further instructions.
  8. Lateral Movement/Exfiltration: The attacker uses the compromised system as a pivot point to move laterally within the network or exfiltrate sensitive data.

Impact

Successful exploitation leads to arbitrary code execution, potentially giving the attacker control over the compromised system. This can lead to data theft, system compromise, lateral movement within the network, and ultimately, significant business disruption. Depending on the level of access achieved, the attacker may be able to install ransomware, steal sensitive data, or disrupt critical business operations. The number of potential victims is broad, spanning across any organization where users have write access to the aforementioned suspicious directories.

Recommendation

  • Enable file creation monitoring, specifically for the suspicious paths listed in the rules, using tools like Sysmon (logsource category: file_event, product: windows).
  • Deploy the Sigma rules provided to your SIEM to detect the creation of executable files in suspicious directories (rules).
  • Investigate any alerts generated by these rules to determine if the created files are malicious or benign.
  • Implement application control policies to restrict the execution of unauthorized executables in user directories (recommendation).
]]>highadvisorypersistencesuspicious-file-creationendpoint