By default, the script generates a report that lists the files that were identified as possibly problematic, lists the markers that identified them as problematic (a.k.a. tags), and then shows the specific line of code where the detection occurred.
SteveD3.io provides comprehensive installation and usage instructions.
Python3 kit hunter 2.py -h python3 kit hunter 2.py -h python3 kit hunter 2.py -h
Scanning by default
To run a thorough scan with the default parameters, follow these steps: kit hunter 2.py (python3)
To do a rapid scan using the bare minimum of detection rules: kit hunter 2.py -q python3
Scan made to order
python3 kit hunter 2.py -c python3 kit hunter 2.py -c python3 kit hunter 2.py -c python
When using the -c flag, a tag file must be placed in the same directory as Kit Hunter. This file can have whatever name you desire, but the extension must be.tag. Please keep in mind that formatting is crucial. There should be no whitespaces and only one item per line. If you need more examples, check through the other tag files.
Scanning based on the directory
Kit hunter 2.py may be run from anywhere and uses the -d switch to pick a directory to scan:
kit hunter 2.py -d /path/to/directory python3
It is, however, easier if kit hunter 2.py is placed first.
Disclaimer: The intended use for the tool is strictly educational and should not be used for any other purpose.
Download : https://github.com/cribdragg3r/Alaris