Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Odin Research / What is / Offensive and testing tools

What Is reNgine? How the Recon Framework Works

An open-source recon pipeline that maps subdomains, ports and weaknesses: how it works, where Odin found it, and how to read its scans.

By
Odin by Brandefense
Updated
21 Nov 2026
Reading time
7 min read
Type
Reconnaissance platform

In short

reNgine is an open-source automated reconnaissance framework for web applications. It runs tools such as Subfinder, Naabu, amass and Nuclei through configurable YAML scan engines, correlates the results in a database and shows them in a web interface. Security teams use it to map their own attack surface, and attackers use it to choose targets.

Key takeaways

What it is
A GPL v3 recon framework on GitHub, built with Django, Celery, PostgreSQL and Docker.
How it works
YAML scan engines chain discovery and check tools, then store, correlate and alert on the results.
Why it matters
Recon is the first step of most attacks. reNgine turns it into a repeatable, scheduled job.
What Odin Research saw
36 to 41 reNgine endpoints per study, most often on port 8082, all kept on watchlists as dual-use.
What to do first
Run discovery on your own estate, retire forgotten hosts and rate-limit inbound scan bursts.

What is reNgine?

reNgine is an open-source automated reconnaissance framework for web applications, published on GitHub under the GNU GPL v3. It chains tools such as Subfinder, Naabu, Nuclei and amass through configurable scan engines, stores results in a database and shows them in a web interface. Security teams and attackers both use it to map attack surfaces.

The project is maintained on GitHub by its author, the user yogeshojha, as yogeshojha/rengine. The README calls it a passion project developed in the author's free time. It focuses on configurable recon, data correlation, continuous monitoring and a database-backed interface.

Reconnaissance is the first stage of almost every intrusion. reNgine automates it. That makes it valuable for defenders who want to see their own attack surface, and for attackers who want a target list.

How reNgine works

reNgine runs as a set of Docker containers. Per its README, the stack uses Django for the web application, Celery workers for scan tasks and PostgreSQL for storage.

  1. Scan engines. A YAML file defines which tools run and how. The project ships preset engines for a full scan, a passive scan, screenshot gathering and OSINT.
  2. Discovery. Subdomain tools such as Subfinder, amass and Chaos find hosts. Naabu finds open ports.
  3. Checks. Nuclei templates, Dalfox for cross-site scripting, CRLFuzzer and an S3 bucket scanner look for weaknesses. GF patterns sort interesting URLs.
  4. Correlation and alerts. Results land in the database. Scheduled and periodic scans can alert through Slack, Discord or Telegram, and the tool can export PDF reports.

Newer releases added AI features. reNgine 2.0 introduced GPT-powered vulnerability descriptions and an attack surface generator, and version 2.1.0 added support for local language models. Version 2.2.0 added a HackerOne target manager called BountyHub.

reNgine requirements, versions and popularity

The README's main path is an Ubuntu server or VPS, installed with an install script after cloning the repository. It recommends scan concurrency by memory: MAX_CONCURRENCY=10 for 4 GB of RAM, 30 for 8 GB and 50 for 16 GB. Once installed, reNgine is reached over HTTPS on the server's address.

The repository showed version 2.2.0, about 9,000 stars and 1,300 forks on 21 November 2026. Role-based access separates system administrators, penetration testers and auditors.

Is reNgine legal? Yes. It is free, open-source software. Scanning systems you are not authorized to test can break computer misuse laws and many hosting providers' terms.

Why reNgine matters to defenders

reNgine itself does not break into anything. What it produces is a map: subdomains, open ports, login portals and likely weaknesses. Attackers use that map to pick targets for phishing, credential attacks or exploits. MITRE ATT&CK files this activity under Active Scanning (T1595), which includes vulnerability scanning and wordlist scanning.

Two practical points follow. First, inbound reNgine-style scanning is often the earliest visible sign of interest in your organization. Second, the same tool run by your own team shows you what that attacker sees. See EASM 101 for how continuous discovery fits a defense program.

What Odin Research observed

  • A steady presence. Monograph 02 counted 23 reNgine records among 476 scanner and OAST records in a C2 feed. Monograph 14 counted 36 reNgine endpoints on 27 IPs. Monograph 29 counted 41 endpoints on 29 hosts.
  • Port 8082 first. In Monograph 14, 18 of 36 endpoints listened on 8082, then 9 on 443 and 5 on 80. The hosts sat mainly in the United States (9), Germany (8) and France (5). Monograph 29 again found 8082 most often, followed by 443, 80 and 8000.
  • Default certificates. In Monograph 29, 17 reNgine endpoints presented the stock certificate that a default install creates, and 15 of those shared one TLS fingerprint. That makes default installs easy to find.
  • Several ports per host. reNgine had the most ports per host in Monograph 29, at 1.41 endpoints per host. One DigitalOcean stack in Germany ran it on 80, 443 and 8000 together.
  • Next to hostile tooling. In Monograph 14, reNgine and ARL consoles sat alongside VShell staging and attacker workbenches that mapped hospital portals. The consoles automate the same kind of discovery those workbenches did by hand.

None of these consoles was blocked. Monograph 29 kept 23 confirmed and 2 suspected reNgine nodes on time-bound watchlists, because enterprise EASM and penetration testing teams run the same software.

How to detect reNgine scanning

  • Inbound bursts. Many requests in a short time, walking through subdomains, ports and common paths, often come from automated recon suites. Rate-limit such sources at the perimeter.
  • Nuclei-style probes. Template scanners request many known paths and fingerprints in a fixed order. WAF logs show this pattern clearly.
  • Exposed consoles. A reNgine console on 8082 or 443 with the default certificate is a hunting lead, not a verdict.
  • Your own hosts. Unapproved reNgine worker launches on your servers suggest someone is running recon from inside your estate.

Monograph 29 publishes a Suricata signature for reNgine and ScopeSentry scan-creation API calls, a Sigma rule for ARL, ScopeSentry or reNgine worker launches, and a KQL hunt. Monograph 29 advises running these rules in alert mode, never drop mode. Monograph 14 adds a Suricata rule for ARL and reNgine discovery traffic. All are in the Defense Kit.

How to defend against automated reconnaissance

  1. Run it on yourself first. Continuous discovery of your own assets removes the attacker's advantage. See external attack surface management and how to defend unknown exposed assets.
  2. Retire forgotten hosts. Old subdomains and test portals are what recon tools find first.
  3. Allowlist narrowly. Exempt only the egress addresses of your own scanners and contracted testers, and only for scanning traffic.
  4. Watch, do not block, consoles. Put exposed reNgine consoles on a watchlist unless a second hostile signal appears.
  5. Harden what recon reveals. Put admin and VPN portals behind multi-factor authentication and patch exposed services fast.

reNgine compared with other recon suites

SuiteFocusEndpoints in Monograph 29Common console port
reNgineWeb reconnaissance with YAML scan engines418082
ARLAsset discovery platform4885003
ScopeSentryRecon suite138See our ScopeSentry page
NemoRecon suiteCovered in other Odin studiesSee our Nemo page

Frequently asked questions about reNgine

What is reNgine?

reNgine is an open-source automated reconnaissance framework for web applications. It chains tools such as Subfinder, Naabu, amass and Nuclei through YAML scan engines, stores the results and shows them in a web interface.

Is reNgine malware?

No. reNgine is a legitimate, GPL-licensed security tool. It is dual-use: attackers run it to map targets, which is why defenders watch for its scans and exposed consoles.

Is reNgine legal?

Yes, the software is legal. Scanning systems you do not own or are not authorized to test can break computer misuse laws and hosting terms.

Who made reNgine?

reNgine is developed by the GitHub user yogeshojha, who describes it as a passion project, and is published as yogeshojha/rengine.

Is reNgine free?

Yes. reNgine is free and open source under the GNU GPL v3.

What tools does reNgine use?

The README names Subfinder, Naabu, amass, Chaos, Nuclei, Dalfox, CRLFuzzer, a misconfigured S3 scanner, GF patterns, WHOIS lookups and WAF detection, among others.

Does reNgine use AI?

Yes. reNgine 2.0 added GPT-powered vulnerability descriptions and an attack surface generator, and version 2.1.0 added support for local language models.

How do I detect reNgine scans?

Look for inbound bursts that walk subdomains, ports and known paths, Nuclei-style template probes, and exposed consoles with the default certificate. Odin Research publishes Suricata, Sigma and KQL rules in its Defense Kit.

reNgine vs ARL: what is the difference?

Both automate asset discovery. reNgine focuses on web reconnaissance with YAML scan engines. ARL is an open-source asset discovery platform whose console listens on HTTPS port 5003 by default, and it was far more common in Odin's data.

Sources

  1. yogeshojha, reNgine repository and README, GitHub. github.com/yogeshojha/rengine (checked 21 November 2026)
  2. MITRE ATT&CK, Active Scanning (T1595). attack.mitre.org/techniques/T1595/ (checked 21 November 2026)

Related tools and terms

All Odin Research explanations · Brandefense glossary

Odin Research

Get the rules, not just the definition

Every Odin Research report ships with verified indicators and detection rules you can load today.

Open the Defense Kit