Guided lesson · beginner

Enumerate the practice company

Work through each phase on your own first. If you stall, tap Tips / Next steps (bottom-right) for one hint at a time. Spoilers stay hidden until you ask.

Targets :3890 directory · :8080 webTime ~30–60 minutes

Before you begin

Mindset for this lesson

You are practicing enumeration: gathering facts before you change anything. Write down what you learn. After each phase, read the short hardening note — that is the defender's takeaway.

01

Phase 1 — Meet the directory

Learn what “domain” and “trust” mean by asking a mock company directory.

Try this

  • Open http://127.0.0.1:3890/help
  • Ask for /domain and /trusts

Why it matters

Attackers and defenders both need a map. Domain and trust info tells you who owns identity and where trust might be abused.

After you finish — harden it

In a real org, directory data should not be anonymous. Require authentication, log queries, and limit what a low-privilege account can read.

02

Phase 2 — Hunt interesting accounts

Find service accounts that look “special,” and notice dangerous group membership.

Try this

  • List users that have SPNs
  • Inspect the Tier-0-Admins group

Why it matters

SPNs mark accounts that act for services. If those accounts are over-privileged, one stolen secret can become domain-wide impact.

After you finish — harden it

Keep service accounts out of Tier-0 / Domain Admin-like groups. Prefer managed/gMSA accounts, strong unique secrets, and tiered admin models.

03

Phase 3 — Web foothold

Use the Tokyo site the way a curious attacker would: notes, login, odd parameters.

Try this

  • Read /notes?file=todo.txt
  • Try the employee portal
  • Test whether file= can leave its folder

Why it matters

Web apps often hold the first credentials. Path confusion and weak passwords turn “just a portal” into a pivot into identity systems.

After you finish — harden it

Never take raw file paths from users. Allow-list filenames. Ban default passwords. Prefer SSO with MFA for internal portals.

04

Phase 4 — Connect the dots

Use what the web foothold gave you to open a more privileged directory view — then explain the risk.

Try this

  • Authenticate to the directory /secrets endpoint
  • Compare the secret to the SPN account from Phase 2

Why it matters

One weak web bug + one over-privileged service identity is a classic chain. Enumeration is how you notice the chain before an attacker finishes it.

After you finish — harden it

Separate web tier credentials from directory privilege. Rotate secrets after labs (and after real incidents). Review BloodHound-style paths regularly in production forests.

Wrap-up

Can you explain the chain?

In your own words: how could a messy website help someone abuse a powerful service account? If you can answer that, you understood the lesson.