Individual skill
detecting-service-account-abuse
Detect abuse of service accounts through anomalous interactive logons, privilege escalation, lateral movement, and unauthorized access patterns.
internal/tools/skills/data/threat-hunting/detecting-service-account-abuse/SKILL.md
Source commit d42f381ad34843e71a42658e5c57290c713e85af
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,313
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- cybersecurity Repository topic
- security Repository topic
- bug-bounty Repository topic
- automation Repository topic
- autonomous-pentesting Repository topic
- ai-agent Repository topic
- ai-security Repository topic
- ethical-hacking Repository topic
- golang Repository topic
- penetration-testing Repository topic
- threat-hunting Declared skill tag
- mitre-attack Declared skill tag
- service-accounts Declared skill tag
- privilege-escalation Declared skill tag
- t1078 Declared skill tag
- proactive-detection Declared skill tag
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,635 bytes
Read excerpt
# Detecting Service Account Abuse
## When to Use
- When proactively hunting for indicators of detecting service account abuse in the environment
- After threat intelligence indicates active campaigns using these techniques
- During incident response to scope compromise related to these techniques
- When EDR or SIEM alerts trigger on related indicators
- During periodic security assessments and purple team exercises
## Detection Gaps & Validation
- **Interactive logon is the signal:** service accounts should only show 4624 Type 5 (service) or Type 3 (network). Hunt 4624 **Type 2 (interactive)** and **Type 10 (RemoteInteractive/RDP)** for any `svc_*` account — but only if those logon types are collected (Type 10 needs RDP/TS auditing on the destination).
- **Kerberoasting precursor:** T1558.003 shows as 4769 TGS requests with `Ticket Encryption Type 0x17 (RC4)` for the service account's SPN — if 4769 auditing is disabled on DCs, the roasting is invisible.