Files
reverse-skill/CTF-Sandbox-Orchestrator/competition-mailbox-abuse/references/mailbox-abuse.md
T
2026-08-08 18:32:33 +08:00

1.1 KiB

Mailbox Abuse Checklist

Core Surfaces

  • Consent grants, app registrations, delegated or application scopes, sign-in events
  • Inbox rules, forwarding settings, delegate access, shared mailbox permissions, transport rules
  • Message traces, mailbox audit events, sender or recipient pairs, message IDs, folder actions

Abuse Chain To Reconstruct

  1. Lure, consent, or credential acquisition
  2. Token or delegate edge obtained
  3. Mailbox or transport mutation applied
  4. Message flow altered, hidden, or exfiltrated

Evidence To Keep Together

  • Identity side: user, app, scope, token claim, delegate edge
  • Mail side: rule predicate, forward target, folder action, message ID, transport action
  • Result side: delivered, forwarded, deleted, rerouted, or silently hidden effect

Common Pitfalls

  • Reporting a token without showing the mailbox effect it actually enables
  • Mixing inbox rules and transport rules without proving which one caused the observed message flow
  • Ignoring shared mailbox or delegate permissions when the mailbox owner itself never logged in