← ClaudeAtlas

detect-ncentral-post-exploitationlisted

Endpoint detection and hunting for post-exploitation of the August 2026 N-able N-central authentication bypasses (CVE-2026-18556, CVE-2026-18577, both in CISA KEV), for SMBs whose MSP runs the vulnerable RMM server, so operator artifacts land on your Windows endpoints. Covers masquerading svchost.exe outside System32 (MITRE ATT&CK T1036.005), a persistent Cloudflare Tunnel service that survives RMM revocation (T1543.003, T1572), and a Take Control session-log hunt. Ships two Sigma rules (Sysmon Event ID 1 or Security 4688, and System Event ID 7045), a log-review hunt, tuning and false-positive notes, and supplier-assurance questions for your MSP. Use when triaging an MSP or RMM compromise notice, hunting N-central or Take Control post-exploitation, investigating an unexpected svchost.exe or Cloudflared service, writing detections for masquerading binaries or tunnel persistence, or deciding what to ask your MSP after an RMM compromise.
umbrasec-labs/umbra-blue · ★ 0 · AI & Automation · score 62
Install: claude install-skill umbrasec-labs/umbra-blue
# N-able N-central Post-Exploitation - Endpoint Detection and Response N-central is an RMM platform: the console a managed service provider uses to patch, script and remotely control every endpoint it manages. In early August 2026 two authentication bypasses in it, CVE-2026-18556 and CVE-2026-18577, were exploited in the wild as zero-days and both landed in CISA KEV. The vulnerable server sits in your provider's rack, so there is no patch for you to apply - but every artifact the operators left landed on client endpoints, and you are best placed to detect it. This skill is defensive: it works from the published weakness class, vectors and confirmed outcome, reconstructs no exploit, and ships no offensive tooling. It explains the technique only as far as endpoint detection and mitigation require. ## TL;DR for defenders Nothing on your side is patchable, so hunt the operator's hands on your own endpoints instead. Three things give the post-exploitation away: a process named `svchost.exe` running from outside `System32`, a Windows service named `Cloudflared` that nobody asked for, and Take Control remote-session logs under `C:\ProgramData\GetSupportService_N-Central\Logs\`. The two Sigma rules below are high-value; the Cloudflared service is what makes this your incident, because it was built to hold access after the MSP's N-central credentials were revoked - containment upstream does not clear persistence downstream. Then put the supplier-assurance questions in the Mitigatio