https://konto.zssk.sk/zk/new#step1

Also, it only seems to show "Strong password" if any of these characters is used: !@#$%^&*, and not other special characters.

you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 2 days ago (3 children)

They could have cracked the password hashes, most likely collected NetNTLMv2 hashes, using a generated list of weak passwords using the company name + a possible ruleset with hashcat.

Some audits still do it against all NTLM hashes stored on the AD DC, but it fell a bit out of fashion because most orgs don't feel comfortable giving out that data for a pentest.

NetNTLMv2 and NTLM hashes are also still notoriously easy to run dictionary and combo bruteforce attacks on with GPUs.

You can see the benchmark for an RTX 5090 here: https://gist.github.com/Chick3nman/09bac0775e6393468c2925c1e1363d5c

It can do a whopping 340.1 GH/s for NTLM and 16017.9 MH/s for NetNTLMv2

Compare that to a Linux's default yescrypt which didn't even have official support in hashcat until this year because the hashrate would be a measly 70-200 H/s.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 2 days ago (2 children)

    How feasible is it to attack argon2id with that method?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 1 day ago* (1 child)

    argon2id is one of those newer algorithms created specifically to make cracking infeasible and protect against certain side channel attacks.

    An example performance from an Nvidia 90HX for LUKS is:

    Hash-Mode 34100 (LUKS v2 argon2 + SHA-256 + AES) [Iterations: 16]

    Speed.#01........: 9 H/s (53.28ms) @ Accel:8 Loops:1 Thr:32 Vec:1

    So correctly implemented, basically impossible lol.

    Hashcat also added recent support for argon2id standalone and keepassxc db, so I'll see if I can run my own benchmark just to see what it shows.

  • source
  • parent
  • hideshow 1 child comment