CYBEREXPERTEXP
HOME / WRITEUPS / DARK-ECLIPSE — AD ATTACK PATH
ACTIVE DIRECTORY LAB

Dark-Eclipse — AD Attack Path

A self-built, hard-rated Windows Server 2022 Active Directory machine with an eight-stage chained path, submitted to Hack Smarter and awaiting QA review.

ACTIVE DIRECTORYWINDOWS SERVERLAB

Lab overview

Dark-Eclipse is a self-built, single-host Windows Server 2022 Active Directory machine designed around an eight-stage chained attack path ending in Domain Admin. The full chain was validated end to end, documented in a technical writeup and handover notes, then revised after platform reviewer feedback. It is scheduled for QA review ahead of release.

Scope: Controlled, self-owned lab environment only. Do not apply these techniques to systems without explicit authorization.

Documented attack-path topics

  1. Credential reuse: use validated credential relationships as an early foothold in the controlled lab.
  2. Nested-group ACL abuse: uncover hidden effective permissions through group nesting.
  3. Shadow credentials: demonstrate abuse of key credential attributes under the lab's configured permissions.
  4. GPP cpassword: identify and validate the legacy credential exposure in SYSVOL.
  5. WriteOwner: chain object ownership control into directory permission changes.
  6. Resource-Based Constrained Delegation: use the configured RBCD path as a later-stage escalation technique.
  7. Decoys: include a fake ADCS misconfiguration and a Kerberoastable dead end to require validation beyond simply following BloodHound edges.

What each future walkthrough will include

  • Lab topology and domain configuration
  • Exact enumeration commands and observed output
  • Prerequisites and permission checks
  • Reproduction steps with sanitized evidence
  • Impact, detection opportunities and remediation

Publication status

The full technical walkthrough and handover notes were created during development. This public page intentionally remains a high-level overview; the detailed chain, commands and evidence can be published as a separate article when the final release and disclosure constraints are clear.

No credentials, private keys, real target addresses or production data should be published in this writeup.