Yara rules for Threat Hunting sessions

All the detection patterns from the threathunting-keywords project are automatically organized in yara rules for each tool and keyword type. These YARA rules are designed for simple keyword detection, focusing on threat hunting sessions and large-scale triage, rather than performance optimization.

2 ruleset folders available:

• Folder yara_rules: threat hunting YARA rules. These are slower but provide broader detection coverage, requiring more triage.
• Folder yara_rules_binaries_strict: Optimized threat hunting YARA rules. These are focused on relevant file types and sizes, with additional conditions for large pattern rules, offering higher fidelity but fewer detections.

• 🛠️ offensive tool keyword: These keywords relate to offensive tools or exhibit high confidence of malicious intent. It's important that these keywords remaons relevant and reliable in detecting potential threats (low false positive rate).

• 🛠️ greyware tool keyword: Keywords in this category correspond to 'legitimate' tools that are abused by malicious actors. As these tools also have legitimate uses, the potential for false positives is inherently higher. It's important to interpret these results with the understanding that not all detections may signify malicious activity

• 🛠️ signature keyword: These keywords may not directly associate with tools but may include security product signature names, specific strings, or words significant in threat detection.

• all.yara: Contains all the rules

• offensive_tools.yara: all the offensive tools rules

• greyware_tools.yara: all the greyware tools (more false positives expected - triage necessary)

a sperated rule file exist for each tool, organized in alphabetical order to bypass the GitHub limitation of 1000 files per directory.

The python script scan.py enables cross-platform scanning of files and directories using the extracted YARA rules

• -y or --yara: Path to the YARA rule file(s) or directory containing them
• -t or --target:Path to the target file or directory to scan
• -o or --output: Path to the output file to save scan results in json format

Example of the json output file using -o or --output:

Enumerates program capabilities and malicious behaviors with bincapz and this project rules: bincapz -third-party -all -stats myfolder