Skip to content

Add new hashcat rules: r3naissance, incredibleindishell, nyxgeek, evilmog, efensive#12

Open
ibnaleem wants to merge 5 commits into
mainfrom
scrape/new-rules-2026-06-16
Open

Add new hashcat rules: r3naissance, incredibleindishell, nyxgeek, evilmog, efensive#12
ibnaleem wants to merge 5 commits into
mainfrom
scrape/new-rules-2026-06-16

Conversation

@ibnaleem

@ibnaleem ibnaleem commented Jun 16, 2026

Copy link
Copy Markdown
Owner

New sources added

Checked, nothing new

Hob0Rules, Hashcracky-Hashcat-Rules, pantagrule, L33tSwap, hashcat-rules-generator, Hashcat-Stuffs, TheZakManRules, NotSoSecure/password_cracking_rules (near-duplicate of existing OneRuleToRuleThemAll), stealthsploit/OneRuleToRuleThemAll (renamed to OneRuleToRuleThemStill, already present), BRDumps/hashcat-rules (README/LICENSE only).

Summary by CodeRabbit

  • Documentation

    • Expanded repository documentation with archive notes and rule descriptions.
  • New Features

    • Added three new rule files containing 2,200+ rule entries.

@coderabbitai

coderabbitai Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

Two README files are populated with rule set documentation (efensive and evilmog). Three new hashcat rule files are added under the nyxgeek directory: a short chopper-mini rule list, a 1380-line insert-from-end rule set covering i1iF token variants, and an 828-line overwrite-from-end rule set covering o1o9 token variants.

Changes

Rule Files and Documentation

Layer / File(s) Summary
README documentation
efensive/README.md, evilmog/README.md
efensive/README.md gains a hashcatrules header noting 250k+ rules. evilmog/README.md is populated with an archive section describing five named rule files (evil.rule, auto.rule, generated2-full.rule, generated3.rule, new-auto.rule).
New nyxgeek rule files
nyxgeek/nyxgeek-chopper-mini.rule, nyxgeek/nyxgeek-i1-fromend.rule, nyxgeek/nyxgeek-o1-fromend.rule
Adds three rule files: 22 quoted-symbol entries in chopper-mini, 1380 r i<token> r lines spanning i1iF variants in nyxgeek-i1-fromend, and 828 r o<token> r lines spanning o1o9 variants in nyxgeek-o1-fromend.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

new rules

Poem

🐇 Hopping through the rule lines, one by one,
From i1 to iF, oh what fun!
The chopper-mini snips, the overwrite roams,
250k rules — the rabbit calls it home.
🌟 New entries land, the archive grows bright!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main change: adding five new hashcat rule sources to the repository, matching the PR objectives which document the addition of rules from r3naissance, incredibleindishell, nyxgeek, evilmog, and efensive.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch scrape/new-rules-2026-06-16

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@evilmog/README.md`:
- Around line 17-20: In the README.md file, correct two text issues: first, on
the line describing a successor to generated2.rule, fix the spelling of
"succesor" to "successor". Second, on the line about the new-auto.rule file,
change "auto generated" to "auto-generated" to properly hyphenate the compound
adjective modifying "rule file".
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 62b0cecd-d18f-4f27-8371-45eb8ecdf102

📥 Commits

Reviewing files that changed from the base of the PR and between cd6955b and 1a79e12.

📒 Files selected for processing (19)
  • efensive/README.md
  • efensive/efensive.rule
  • evilmog/README.md
  • evilmog/auto.rule
  • evilmog/evil.rule
  • evilmog/generated2-full.rule
  • evilmog/generated3.rule
  • evilmog/new-auto.rule
  • evilmog/omgwtfbbq.optimized.rule
  • incredibleindishell/rockyou-30000.rule
  • nyxgeek/T0XlC-insert_00-99_1950-2050_toprules_0_F.as_advertised.rule
  • nyxgeek/T0XlC-insert_00-99_1950-2050_toprules_0_F.fixed.rule
  • nyxgeek/nyxgeek-chopper-mini.rule
  • nyxgeek/nyxgeek-i1-fromend.rule
  • nyxgeek/nyxgeek-i2-fromend.rule
  • nyxgeek/nyxgeek-o1-fromend.rule
  • nyxgeek/nyxgeek-o2-fromend.rule
  • r3naissance/all_the.rulez
  • r3naissance/balanced.rulez

Comment thread evilmog/README.md
Comment on lines +17 to +20
an attempt at a succesor to generated2.rule

new-auto.rule:
another attempt at making an auto generated rule file, releasing now

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Fix spelling and hyphenation in rule descriptions.

Line 17 has a typo (succesorsuccessor), and Line 20 should use auto-generated for correct compound adjective usage.

Suggested patch
-an attempt at a succesor to generated2.rule
+an attempt at a successor to generated2.rule
@@
-another attempt at making an auto generated rule file, releasing now
+another attempt at making an auto-generated rule file, releasing now
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
an attempt at a succesor to generated2.rule
new-auto.rule:
another attempt at making an auto generated rule file, releasing now
an attempt at a successor to generated2.rule
new-auto.rule:
another attempt at making an auto-generated rule file, releasing now
🧰 Tools
🪛 LanguageTool

[grammar] ~17-~17: Ensure spelling is correct
Context: ...d out generated3.rule: an attempt at a succesor to generated2.rule new-auto.rule: anot...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~20-~20: Use a hyphen to join words.
Context: ....rule: another attempt at making an auto generated rule file, releasing now for p...

(QB_NEW_EN_HYPHEN)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@evilmog/README.md` around lines 17 - 20, In the README.md file, correct two
text issues: first, on the line describing a successor to generated2.rule, fix
the spelling of "succesor" to "successor". Second, on the line about the
new-auto.rule file, change "auto generated" to "auto-generated" to properly
hyphenate the compound adjective modifying "rule file".

Source: Linters/SAST tools

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant