Skip to content
Brand Logo

hashpwn
  1. Home
  2. Tools

Tools

57 Topics 250 Posts

Discuss useful tools related to hash cracking. Do not upload binaries or post links to malicious files.
Follow Posting Template:
https://forum.hashpwn.net/post/68

Subcategories

  • Matrix - Encrypted Chat

    1 2
    1 Topics
    2 Posts
    No new posts.

  • Encrypted pastebin hosted by hashpwn, powered by PrivateBin.

  • Hash cracking tools.
    Follow Posting Template:
    https://forum.hashpwn.net/post/68

    32 160
    32 Topics
    160 Posts
    cycloneC
    @partly9642 This is a GPU sanity-check failure. When this happens, yescrypt_crack falls back to CPU mode. The error may indicate an issue with the AMD OpenCL implementation or local OpenCL environment, but further testing is needed to confirm what's actually going on. Please verify that: You are running yescrypt_crack on native Linux or Windows, not WSL or another emulated environment Your AMD GPU and OpenCL drivers are up to date and working correctly The GPU has sufficient VRAM, since yescrypt is memory intensive If everything checks out and the error persists, please open a GitHub issue: https://github.com/cyclone-github/yescrypt_crack/issues Please include: GPU model and VRAM AMD driver/OpenCL/ROCm version Host OS/version Full yescrypt_crack error/output

  • Network related tools for web scraping, IP / domain lookups , etc.
    Follow Posting Template:
    https://forum.hashpwn.net/post/68

    4 12
    4 Topics
    12 Posts
    cycloneC
    Spider v1.0.0 released. https://github.com/cyclone-github/spider/releases/tag/v1.0.0 v1.0.0 by @cyclone-github in https://github.com/cyclone-github/spider/pull/15 chore(deps): bump github.com/PuerkitoBio/goquery from 1.11.0 to 1.12.0 in the minor-and-patch group by @dependabot[bot] in https://github.com/cyclone-github/spider/pull/14 added flag "-text-match" to filter page text matches memory and performance optimizations for -file and -url modes -file mode streams wordlists from disk instead of loading entire files into RAM reduced RAM usage for large -sort wordlists default -timeout increased from 1 to 10 seconds progress bars, stats, and errors now write to stderr sanitize url fragments for dedup and extension checks updated default User-Agent Full Changelog: https://github.com/cyclone-github/spider/compare/v0.9.1...v1.0.0

  • Share and discuss scripts that help automate hash cracking and related tasks. Zero tolerance for malicious content.
    Follow Posting Template:
    https://forum.hashpwn.net/post/68

    9 42
    9 Topics
    42 Posts
    A1131A
    On the results of ranker x1.greedy vs a1131.greedy rulesets # head x1.greedy_top50000.rule : T0 T2 T4 T6 T8 TA TC $1 $2 l x12 c'1$s18 “A$p t T0 T6 TA $3 T0 T5 TA 1 $2 $3 R2 -9x35 ^f # head a1131.greedy.25000.rule : l T0 $1 K ] $1 $2 $3 $4 $2 +2 # head a1131.greedy_top50000.r1.rule : ] $a [$1 [$9 [$8 [$7 [$4 [$3 [ [ $6 [ [ $5 As can be seen above, the rules obtained using the ranker (with CELF) are not only diverse, but also deliver very similar results at the identical cut-offs of 10k / 25k / 50k. Rule Hit rate Size AVG Time Eff. a1131.greedy.10000.rule 22.75% 10 000 25 352 2.275 x1.greedy_top10000.rule 22.56% 10 001 501.44 2.2558 a1131.greedy.25000.rule 28.60% 25 000 31 879 1.144 x1.greedy_top25000.rule 28.46% 25 001 25 832.06 1.1384 a1131.greedy_top50000.r1.rule 33.60% 50 001 16 987.14 0.672 x1.greedy_top50000.rule 33.05% 50 001 21 051.92 0.661 Ranker + CELF generates rulesets with very similar effectiveness (differences of only 0.14–0.55 pp), while being more diverse and less redundant. At the 10k/25k/50k cut-offs the results are practically equivalent. Full Benchmark

  • Tools for text, wordlist, hashcat rules, etc.
    Follow Posting Template:
    https://forum.hashpwn.net/post/68

    10 33
    10 Topics
    33 Posts
    cycloneC
    pcfg-go v0.6.0-dev (upcoming release) https://github.com/cyclone-github/pcfg-go/commit/8fb59c2 While I was testing hashcat's new -a 4 PCFG mode with different hash lists and Rules trained with pcfg-go, @atom mentioned something to me that I couldn't shake: "that needs a fast trainer". But, pcfg-go was already fast, right? How much faster did it need to be? I was determined to find the answer to this question and pored over possible optimizations in pcfg-go, optimizing keyboard walks, buffers, worker scheduling, profiling hot paths and reducing GC pressure, testing / benchmarking / and comparing Rule outputs to make sure the optimized trainer still produced 1:1 byte-level-identical Rules to v0.5.3. The result? Let's first back up a minute to run a few comparisons. The original python3 pcfg_cracker trainer.py by @lakiw took 13m21s to train rockyou on my Debian 13 benchmarks pcfg-go v0.5.3 brought rockyou training down to 2m38s And finally, pcfg-go v0.6.0-dev brings rockyou training down to 14.8s Yes, from 13m21s to 14.8s. Now, that's a fast trainer. [image: 1787772381003-9dc5d6d5-4ed8-4d6b-826f-b095be9997b0-image.jpeg] A big thanks to @atom for his support, suggestions, and kindness, and @lakiw for giving the world pcfg_cracker in the first place.