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 ARL? The Asset Reconnaissance Lighthouse Recon Platform

An open-source asset discovery console that maps domains, ports and login pages: who runs it, where Odin Research sees it, and how to see your own surface first.

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

In short

ARL (Asset Reconnaissance Lighthouse) is an open-source asset discovery system. It finds domains, IP ranges, open ports, services and web fingerprints linked to a target, schedules recurring scans and watches GitHub for keywords. Security teams use it to map their attack surface, and attackers use the same map to choose targets.

Key takeaways

What it is
An open-source asset reconnaissance system, documented by the tophant-ai organization, that builds an inventory of a target's internet assets.
How it works
Web, worker, GitHub-worker and scheduler services run discovery, nmap port scans and web fingerprinting, store results in MongoDB and serve a console on HTTPS port 5003.
Why it matters
The map ARL builds is the first step of a targeted attack. Odin saw ARL staged next to a weaponizer project and a callback collector.
What Odin Research saw
Up to 488 ARL endpoints in one study, about 70% on port 5003, mostly in China, the US and Hong Kong. None was blocked as dual-use.
What to do first
Map your own attack surface, close forgotten assets and rate-limit inbound scan bursts. Watch ARL consoles; do not block them all.

What is ARL?

ARL, short for Asset Reconnaissance Lighthouse, is an open-source system that quickly finds internet assets linked to a target and builds a basic asset inventory. Its documentation says it helps enterprise security teams and penetration testers see their attack surface from an attacker's point of view and spot weak points.

ARL's documentation lives in the ARL-doc repository of the tophant-ai organization on GitHub. Most ARL consoles Odin Research sees sit in China and Hong Kong. The documentation asks users to agree to a disclaimer before they install or use it.

ARL is a reconnaissance tool. It does not exploit anything by itself. But the map it builds, of domains, open ports, services and login pages, is exactly what an attacker needs to pick targets. That makes it dual-use, like most external attack surface management tooling.

How ARL works

The ARL documentation lists these feature groups:

  • Asset discovery for domain names, IP addresses and IP ranges.
  • Port scanning and service identification, with nmap doing the port scans.
  • Web fingerprinting of sites, with support for custom fingerprints.
  • Asset management with grouping and search.
  • Task management with strategy settings, scheduled tasks and recurring tasks.
  • Monitoring of GitHub keywords, domain and IP assets, and site changes.
  • Risk checks for file leaks and Host header collision issues, plus calls to nuclei templates and WebInfoHunter.

Under the hood, the installation guide describes four services: arl-web for the console, arl-worker for scanning, arl-worker-github for GitHub monitoring and arl-scheduler for timed jobs. MongoDB stores the results. The web console uses HTTPS on port 5003.

In MITRE ATT&CK terms, an ARL scan against someone else's network is Active Scanning (T1595), which sends traffic straight to the target's infrastructure.

ARL requirements and installation

According to the installation guide, ARL does not support Windows. The guide suggests Docker for first-time use and a source install for long-term use, and the source install is adapted only for CentOS 7. A Podman setup is also documented. It needs the NET_RAW capability so nmap can open raw sockets.

The guide recommends 4 CPU threads, 8 GB of RAM and 10 Mbps of bandwidth, and suggests a cloud server because asset discovery creates a lot of traffic. That advice helps explain why so many ARL consoles sit on cloud hosting.

The documentation also describes a default administrator login. If you run ARL, change it at once and keep the console off the open internet.

How attackers use ARL

Recon comes before almost every targeted attack. An attacker who points ARL at a company gets a list of its subdomains, exposed services and login portals. That list feeds the next step, whether it is phishing, password spraying or an exploit against an exposed appliance.

Odin Research reports show ARL used in that role next to clearly offensive tools.

  • One open directory held ARL-plus-docker, a packaged ARL worker, next to a weaponizer project for the RuoYi framework and 126 screenshots of web login pages.
  • One cloud server ran a DNSLog callback collector on the same IP as an ARL panel on port 5003.

Most ARL consoles still belong to testers and researchers. The tool is a signal of interest, not of intent.

What Odin Research observed

ARL appears in five Odin reports. Each study draws its own set, so totals differ.

  • A large fleet. Monograph 14 counted 425 ARL endpoints on 413 IPs: 96 confirmed, 24 suspected and 305 candidates. Ports 5003 (282), 443 (95) and 3389 (19) led. China (235), the United States (127) and Hong Kong (46) hosted the most.
  • Another large set. Monograph 29 found 488 ARL endpoints on 474 hosts, 69.7% on port 5003. Nineteen suspected hosts also exposed RDP on port 3389 with self-signed certificates named after internal addresses.
  • Paired recon suites. Two Chinese servers in Monograph 29 ran ARL next to ScopeSentry. Six ARL candidate endpoints on five hosts also served an open file index, and three of them exposed configuration or credential files next to the console.
  • A newer fork. Monograph 23 counted 75 ARL-Next endpoints on 67 hosts, 45 of them on port 5173. 63 of the 75 sat in China and Hong Kong.
  • Repeated certificates. Monograph 02 found one ARL certificate name on 90 endpoints on port 443. Monograph 17 found the DNSLog and ARL pairing described above.

No ARL console in these reports went on a block list. They stay on watchlists, because legitimate teams run the same software.

How to detect ARL scanning

  • Inbound scan bursts. ARL sweeps ports, fingerprints sites and requests many paths. Bursts of this kind from one cloud source are the main sign on your own perimeter.
  • ARL markers in headers. Some ARL traffic carries product-specific header markers that a network sensor can match.
  • Exposed consoles. HTTPS on port 5003, or a Vite UI on 5173 for ARL-Next, with an ARL login page identifies a console on the internet.
  • Your own hosts. ARL worker containers or ARL-plus-docker outside approved testing hosts deserve a look.

Odin Research publishes rules for these signs. Monograph 14 has a Suricata signature for ARL header markers. Monograph 23 adds a Suricata audit rule for ARL-Next task calls and a Sigma rule that covers ARL-plus-docker. Monograph 29 adds a Suricata policy rule for ARL task submissions. All are in the Defense Kit. Keep them in alert mode, not drop mode.

How to defend against ARL reconnaissance

  1. Map yourself first. Run your own asset discovery so you see what ARL would see. The EASM 101 guide explains how.
  2. Close what you do not need. Remove forgotten subdomains, test sites and admin panels. See how to handle unknown exposed assets.
  3. Rate-limit at the edge. Slow sources that send bursts of probes, and alert when a scanning source also shares a host with an implant.
  4. Do not block every console. An ARL console on the internet is a lead. Blocking all of them breaks legitimate work and barely slows an attacker, who can move to a new server.

ARL compared with other recon platforms

PlatformTypical console portOdin countNotes
ARL5003 (HTTPS)488 endpoints (Monograph 29)Asset, port, fingerprint and GitHub monitoring
ARL-Next517375 endpoints (Monograph 23)Newer ARL-based suite
reNgine808241 endpoints (Monograph 29)Chains tools such as subfinder, httpx and nuclei in containers
ScopeSentry8082138 endpoints (Monograph 29)Seen side by side with ARL on two servers

Frequently asked questions about ARL

What is ARL?

ARL, or Asset Reconnaissance Lighthouse, is an open-source system that finds a target's internet assets, such as domains, IP ranges, ports, services and web fingerprints, and keeps them in a searchable inventory.

Is ARL malware?

No. ARL is a reconnaissance tool built for security teams and penetration testers. It is dual-use, because attackers can use the same asset map to plan attacks.

Is ARL legal to use?

Scanning your own assets or assets you are authorized to test is legal. Scanning other organizations without permission may break the law in many countries.

What port does ARL use?

The ARL documentation says the web console uses HTTPS on port 5003. Odin Research also saw ARL consoles on port 443, and the ARL-Next suite mostly on port 5173.

Who makes ARL?

ARL's documentation is published in the tophant-ai organization's ARL-doc repository on GitHub.

How do I install ARL?

The documentation recommends Docker for first-time use, or a source install on CentOS 7. It does not support Windows and suggests 4 CPU threads, 8 GB of RAM and a cloud server.

How do I detect ARL scanning?

Look for inbound bursts of port and path probes from one source, ARL header markers and exposed ARL consoles. Odin Research publishes Suricata and Sigma rules for ARL in its Defense Kit.

ARL vs reNgine: what is the difference?

Both automate asset discovery. ARL bundles discovery, fingerprinting and GitHub monitoring in one console on port 5003, while reNgine chains tools such as subfinder, httpx and nuclei in containers.

Sources

  1. tophant-ai, ARL-doc repository, GitHub. github.com/tophant-ai/ARL-doc (checked 21 November 2026)
  2. ARL documentation, overview. github.com/tophant-ai/ARL-doc/blob/master/docs/index.md (checked 21 November 2026)
  3. ARL documentation, system installation guide. github.com/tophant-ai/ARL-doc/blob/master/docs/system_install.md (checked 21 November 2026)
  4. MITRE ATT&CK, T1595 Active Scanning. 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