CTF-Sandbox-Orchestrator/competition-mailbox-abuse/SKILL.md·查看原始 Markdown·索引

name: competition-mailbox-abuse description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for enterprise mail abuse, OAuth consent, inbox or forwarding rules, transport rules, shared mailbox access, phishing chains, and token-to-mailbox side effects. Use when the user asks to trace mailbox rules, OAuth consent grants, forwarding or delegate abuse, shared mailbox access, message-trace evidence, or explain how mail artifacts turn into persistence, exfiltration, or privilege. Use only after $ctf-sandbox-orchestrator has already established sandbox assumptions and routed here.


Competition Mailbox Abuse

Use this skill only as a downstream specialization after $ctf-sandbox-orchestrator is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to $ctf-sandbox-orchestrator first.

Use this skill when the decisive path runs through mailbox behavior, consent flow, or message-routing effects rather than generic AD evidence alone.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Decide whether the active path is phishing-to-consent, token-to-mailbox, rule-based persistence, or transport-level mail rerouting.
  2. Keep mailbox evidence, identity evidence, and message-trace evidence tied to the same user, mailbox, token, or message ID.
  3. Separate possession of a token or delegate edge from the actual mailbox effect it enables.
  4. Record forwarding targets, rule predicates, consent scopes, shared mailbox edges, and resulting mail flow in compact blocks.
  5. Reproduce the smallest mail effect that proves persistence, exfiltration, or privilege.

Workflow

1. Map The Mail Trust Path

2. Prove The Mailbox Effect

3. Reduce To The Decisive Abuse Chain

Read This Reference

What To Preserve