Skip to content

Accounts that returned AADSTS50053 should be tested again #51

@realalexandergeorgiev

Description

@realalexandergeorgiev

Hey,

just a quick one:

  • when MS smart protection kicks in after xxx failed attempts it often returns AADSTS50053 (Account appears to be locked.) even though the account is not locked. It is just the source IP that is blacklisted. I noticed that trevorspray will then still add the account to .trevorspray/tried_logins.txt

While it is true (it was tried), I believe it should not be added, since its return code was likely to due smart protection.

Idea:

  • Adding the return code into tried_logins, so people can chose to grep for specific ones and re-run the tests (?)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions