devanshbatham / rayder

A lightweight tool for orchestrating and organizing your bug hunting recon / pentesting command-line workflows

---

Hey, It's Devansh ⚡

Projects 🏗️

• ParamSpider - Mining URLs from dark corners of Web Archives for bug hunting/fuzzing/further probing
• FavFreak - Making Favicon.ico based Recon Great again
• OpenRedireX - A fuzzer for detecting open redirect vulnerabilities
• CertEagle - Weaponizing Live CT logs for automated monitoring of assets
• Quaithe - Quaithe empowers you to execute multiple commands in parallel for blazing-fast performance.
• DNSleuth - DNSleuth allows you to spy on the DNS queries your machine is making.
• Watson - Watson is a utility for note management and search from your terminal.
• ip2cloud - Check IP addresses against known cloud provider IP address ranges
• getresolvers - A simple utility to fetch freshly updated DNS resolvers
• revwhoix - A simple utility to perform reverse WHOIS lookups using whoisxml API
• heaptruffle - Mine URLs from Browser's Heap Snapshot for fun and profit
• ip2asn - A utility to quickly map IP addresses to their respective ASN
• revit - A command-line utility for performing reverse DNS lookups
• getsan - A utility to fetch and display dns names from the SSL/TLS cert data
• headerpwn - A fuzzer for finding anomalies and analyzing how servers respond to different HTTP headers
• dnsaudit - A command-line utility for auditing DNS configuration using Zonemaster API
• rayder - A lightweight tool for orchestrating and organizing your bug hunting recon / pentesting command-line workflows
• realm - A utility for recursively traversing SSL/TLS certificates for collecting DNS names

Knowledge Bases 💡

• Awesome Bugbounty Writeups - A curated list of bugbounty writeups (Bug type wise)
• Vulnerabilities Unmasked - Learn complex security vulnerabilities in simple terms that even a five-year-old can understand!
• Everything About DNS - Explains the basics of DNS at different levels of complexity for readers with various technical backgrounds.
• Solidity Gas Optimization Tips - Solidity Gas Optimization Tips and Tricks

Contact 📞

• Twitter
• LinkedIn

rayder's Issues

Parallel tasks

Hi, what about parallel tasks mode. Now there are 2 ways: all sequentially, all parallel
So, what about combination mode, rewrite few lines in go file and make flag parallel to module, not entire config

task1 => task2 => task3 (seq) => task 5 => task6
--------------------=> task 4 (parallel)

Check tools

Hello,

Firstly thank for this simple and amazing tool. If you would like to use this workflow within the tools, please see: crlfuzz, subfinder, etc. Should be able to control the tools installed in the operating system.

request help

I encounter an error when using the -it flag, but it works fine when I use either the -i or -t flag.
And the same happens when silent=true. Is it possible to support the -it flag ?

If I use the -i flag, I can exit a running Docker container with Ctrl+C. However, an error message is displayed

"If I only use the -t flag, I cannot exit a running container with Ctrl+C.

thank you very much ！

help error

Support to the axiom

Hello,

I use to axiom (https://github.com/pry0cc/axiom), Can we integrate that?

In documentation, example #1 can't be parsed because of ":" in the commands

Description

While reading the straightforward documentation, tried to execute the first example workflow, but got Error unmarshaling YAML: yaml: line 7: did not find expected key

To Reproduce

Create a workflow from the first example

vars:
  ORG: "example.org"
  OUTPUT_DIR: "results"

modules:
  - name: example-task
    cmds:
      - echo "Organization: {{ORG}}"
      - echo "Output directory: {{OUTPUT_DIR}}"

Execute the workflow

user :: Ryder/Testing » rayder -w example1_flow.yaml
                                                                                                                                                                               
                                                                                                                                                                               
                                 __                                                                                                                                            
           _____________  ______/ /__  _____                                                                                                                                   
          / ___/ __  / / / / __  / _ \/ ___/                                                                                                                                   
         / /  / /_/ / /_/ / /_/ /  __/ /                                                                                                                                       
        /_/   \____/\___ /\____/\___/_/                                                                                                                                        
                   /____/                                                                                                                                                      
                                                                                                                                                                               
                                - v0.0.4 ⚡                                                                                                                                    
                                                                                                                                                                               
                                                                                                                                                                               
                                                                                                                                                                               
Error unmarshaling YAML: yaml: line 7: did not find expected key

Solution

I started to figure out "why this happened" (I am not familiar with YAML) and found out that colon ":" is a special "indicator character".

The way to fix this error is as follows:

• remove colon ( : ) after string "Organization" and "Output directory"

  • - echo "Organization {{ORG}}"
  • - echo "Output directory {{OUTPUT_DIR}}"

• escape colon with double quotes

  • - echo Organization":" {{ORG}}
  • - echo Output directory":" {{ORG}}

I think that because of the error in the first example, fewer people will try this great tool

Add feature: About parallelism

Hopefully it's possible to customize any of several of these workflows in parallel, rather than globally