CyberKit

Service Execution

Also called Service Creation.

Creating or hijacking a system service to run attacker code.

What it is

Installing a new system service or modifying an existing one so that attacker-controlled code runs, typically with high privileges and automatic start. Services can be created locally or pushed to remote hosts over management protocols.

Why it matters

Service execution offers both high-privilege code execution and durable persistence, and remote service creation is a classic lateral-movement step. Service installation events and the registry's services hive are core artifacts for spotting it.

In practice

A service with a random name is created on a file server to execute a remote-access tool as SYSTEM during lateral movement.

What to look for

  • Event ID 7045 or 4697 for a new service with a strange name or path.
  • Services whose binary path runs cmd.exe, PowerShell or a file in a temp folder.
  • Short-lived services created and deleted within seconds, a pattern of remote execution tools.

Common mistake

Ignoring services that no longer exist. A service created for one run and removed still leaves its install event behind.

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