Minutes 1–3: find the routes

Search your password manager and inbox for the accounts connected to this area. Note which ones use a universal identifier, which have a per-service alias, and which no longer have a clear owner or purpose.

Minutes 4–6: find the weak link

One incident creates a target list for credential stuffing and tailored scams. Look first for public addresses used for recovery, temporary routes attached to durable accounts, reused passwords and aliases that receive unrelated mail.

Minutes 7–9: make one repair

  • Save evidence
  • Change exposed credentials
  • Update the genuine account
  • Watch for tailored phishing

Choose the highest-consequence problem, not the longest list. Confirm the replacement before disabling anything.

Minute 10: leave a note

Contain the exposed relationship and replace its route without moving every account. Record what changed and set the next review for a natural event. The alias identifies where the trail began, not necessarily who deliberately shared it.

A ten-minute audit is successful when tomorrow is simpler.

Give the next relationship its own route.

Create an MXDuck alias