AccountRecoveryTagger
Flags credential-management and account-recovery endpoints — password reset/change, forgot-password, email change, MFA/2FA enrollment, OTP, and account verification/recovery. These are the classic account- takeover surface: review for reset-token leakage, host-header injection in reset links, account enumeration, missing rate limiting, and weak step-up verification.
Constants
Parameter names that mark a credential change or a recovery/step-up code regardless of the route.
Path segments that on their own mark a credential/recovery action.
password/mfa/otp/forgot are not benign as a standalone path
component. recover/recovery are intentionally not here — they
collide with disaster/backup/data recovery — and are matched in the
weak tier instead (so /account/recovery tags but /disaster-recovery
does not).
Spelled-out multi-factor path words. The generic separator split turns
two-factor into the harmless tokens [two, factor], so the mfa/2fa
forms above never match these. Checked against separator-stripped slash
segments instead, so two-factor, two_factor, and twofactor (and
the second-/multi- spellings) all match.
Weaker, generic action words. Tag only when two distinct weak
tokens co-occur (e.g. /verify-email, /change-email,
/account/recovery), so a bare /reset or /confirm on an
unrelated resource is not flagged. change/update pair with
email/username to catch the email-change ATO vector.