Service Creation
Also called Malicious Service.
Installing or hijacking a Windows service so attacker code runs at every boot.
What it is
Creating a new Windows service, or modifying an existing one, so the service control manager launches an attacker's binary automatically: typically with SYSTEM privileges and across reboots.
Why it matters
Services are a durable persistence and privilege mechanism that survive logoff and restart, so a single missed malicious service can re-establish an intrusion after remediation. Service installs are logged (e.g., Windows event ID 7045), which makes them a reliable hunting signal.
In practice
An attacker registering a service that points to a dropped binary so it relaunches with SYSTEM rights at the next boot.
What to look for
- Event ID 7045 or 4697 with a new service name.
- Service binary paths in temp, ProgramData or user folders.
- New services set to auto start right after an intrusion.
Common mistake
Only reviewing service names. Read the binary path and the account it runs as.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Event Log Reader
Read a binary .evtx file or pasted event XML, with logon types, NTSTATUS codes and the Keywords mask decoded.
- Windows Host Case
An alert on a live Windows workstation: read the event logs and the Registry, rebuild the timeline, then decide what to collect.
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.
ATT&CK techniques
- T1543.003: Windows Service
Read next
- Persistence: Mechanisms that keep attacker access across reboots.
- Windows Event Log: Windows' record of logons, process starts, and system activity.
- Living off the Land: Attackers abuse built-in, trusted tools instead of dropping malware.