CyberKit

Signed Binary Proxy Execution

Also called LOLBin Proxy Execution.

Hiding code execution behind a trusted, signed system binary.

What it is

Using a legitimate, digitally signed operating-system binary to load, run, or proxy the execution of attacker-supplied code. The trusted binary acts as a launcher so the malicious payload inherits its reputation.

Why it matters

This defeats simple allow-listing and signature checks because the executing image is a sanctioned Microsoft-signed tool, pushing detection toward command-line and parent-child process analysis. Stealthy, malware-light intrusions rely on it heavily.

In practice

An analyst spots a signed scripting host being invoked with an unusual command line that loads a remote payload, despite the binary itself being legitimate.

What to look for

  • Built-in binaries such as rundll32, mshta or regsvr32 loading files from user folders.
  • Those binaries making outbound network connections.
  • Unusual command lines, such as a URL or script passed to a binary that rarely sees one.

Common mistake

Allowlisting by publisher alone. The binary is genuinely Microsoft's; the command line is what gives it away.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Atomic Red Team Open source

    Small, scripted tests mapped to ATT&CK techniques, used to check whether a detection fires.

  • ATT&CK Navigator Open source

    Lays techniques out on the ATT&CK matrix so teams can mark coverage, gaps and threat profiles.

  • Microsoft Defender for Endpoint Commercial

    Tags its alerts with the ATT&CK techniques it observed on the host.

  • Sysmon Free

    Supplies the host telemetry that most technique detections are written against. Our notes.

Read next

Sources