Infdefaultinstall - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/tags/infdefaultinstall/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioThu, 03 Sep 2026 13:45:50 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgAbuse of InfDefaultInstall.exe for SCT Script Executionhttps://feed.craftedsignal.io/briefs/2026-09-infdefaultinstall-sct-execution/Thu, 03 Sep 2026 13:45:50 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-09-infdefaultinstall-sct-execution/Adversaries leverage the native Windows utility InfDefaultInstall.exe to execute malicious script content embedded within specially crafted INF files.InfDefaultInstall.exe is a legitimate Microsoft-signed Windows binary designed for the installation of INF (Information) files. Threat actors can abuse this utility as a Living-off-the-Land (LotL) technique to bypass security controls. By creating a malformed or specially prepared INF file containing references to script components (SCT) via scrobj.dll, an attacker can force the system to execute arbitrary code. Because the process is signed by Microsoft, this technique is frequently utilized to evade signature-based detection mechanisms that rely on process reputation. This behavior is documented in the LOLBAS (Living Off the Land Binaries and Scripts) project and has been validated by Atomic Red Team exercises. Defenders should monitor for the execution of InfDefaultInstall.exe with arguments pointing to suspicious or user-writable INF files, as this is a known vector for initial access or persistence.

Attack Chain

  1. Attacker prepares a malicious INF file containing an InstallSection that references a remote or local SCT file.
  2. Attacker crafts the INF file to utilize the RegisterOCX directive or similar hooks to load scrobj.dll.
  3. Attacker delivers the malicious INF file to the victim endpoint through phishing or shared drive access.
  4. Attacker executes InfDefaultInstall.exe from the command line, passing the path to the malicious INF file as an argument.
  5. The Windows utility parses the INF, triggers the registration of the specified SCT script, and executes the payload.
  6. The malicious payload runs within the context of the InfDefaultInstall.exe process, potentially leading to further compromise.

Impact

Successful exploitation allows for arbitrary code execution, which can be leveraged for lateral movement, credential theft, or the deployment of secondary malware. While InfDefaultInstall.exe is a built-in utility, its misuse allows an attacker to hide malicious activity under a trusted process identity, complicating incident response and forensic analysis.

Recommendation

  • Deploy the provided Sigma rule to monitor for suspicious command-line invocations of InfDefaultInstall.exe.
  • Establish a baseline of legitimate use of InfDefaultInstall.exe within the organization; alert on any unexpected paths or execution from user-writable directories (e.g., C:\Users\Public).
  • Enable Sysmon process-creation logging (Event ID 1) and command-line auditing to capture the arguments passed to InfDefaultInstall.exe.
]]>mediumadvisoryliving-off-the-landexecutionwindowsinfdefaultinstall