stealthy-beacon
02.1 — Stealthy Beacon
Authorized use only: Use these notes only in owned, explicitly authorized, or isolated lab environments.
Detection awareness: Assume commands, binaries, network calls, identity changes, and cloud or directory actions may be logged by endpoint tooling, audit frameworks, SIEM pipelines, proxy logs, DNS logs, auth logs, and platform telemetry.
Blue-team view: Treat every technique as a defender validation exercise too: note what artifacts it creates, what alerts or hunts could surface it, and what monitoring or hardening would prevent or contain it.
CTF/lab boundary: If a sandbox or CTF includes bypass-oriented exercises, keep them confined to that environment and translate the lesson into detection, prevention, and cleanup notes rather than real-world evasion guidance.
This file has been superseded. All stealthy beacon content has been consolidated and expanded in the full module.
Full coverage is in: 7.7 Advanced C2 Techniques — includes working implementations for:
- OneDrive / SharePoint C2 (Graph API)
- GitHub Gist C2
- Slack Bot C2
- Google Calendar C2
- DNS tunneling (advanced OPSEC)
- Domain fronting
- Email draft C2
- Steganography channels
- Tool references: DLL sideloading, threadless injection
Tools referenced in prior version:
- Shhhloader — shellcode loader with evasion
- nimpacker — Nim-based packer
- NimGetSyscallStub — Nim syscall resolution
- Loki — BPAC + sleep obfuscation
For syscall evasion (DLL sideloading, threadless injection): 6.2 Syscall Evasion Deep Dive
For sleep obfuscation and stack spoofing: 6.3 Sleep Stack Evasion