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 Nemo? The Distributed Recon Platform Explained

An open-source asset discovery platform that chains scanners across distributed workers. Small fleet, clear fingerprints, real reconnaissance value.

By
Odin by Brandefense
Updated
21 Nov 2026
Reading time
6 min read
Type
Reconnaissance platform (dual-use)

In short

Nemo, published as nemo_go on GitHub, is an open-source platform for automated information gathering. It combines common tools such as Nmap, Masscan, Subfinder and Nuclei to map internal and internet-facing assets, running tasks on distributed workers from a web console. Penetration testers use it, and so do operators preparing intrusions.

Key takeaways

What it is
An open-source Go platform, nemo_go, that automates asset discovery for penetration testing by chaining port, subdomain, fingerprint and vulnerability tools.
How it works
A server with a web console sends tasks through RPC and a message queue to distributed workers, which scan and store results in MongoDB.
Why it matters
Recon platforms build the target list for later attacks. A Nemo console aimed at your ranges means someone is mapping you.
What Odin Research saw
Six Nemo controllers, all confirmed and all on port 5000, on Tencent, Alibaba and HostPapa hosting. Monograph 25 published all six for blocking.
What to do first
Know your own exposed assets before scanners do, and watch for task-dispatch traffic to port 5000 from inside your network.

What is Nemo?

Nemo is an open-source platform for automated information gathering, published on GitHub as nemo_go. Its README says it combines common reconnaissance tools to collect data on internal and internet-facing assets. The stated aim is to support hazard investigation and penetration testing from one web console.

In practice, Nemo is an asset discovery console. An operator enters targets once. The platform then runs port scans, subdomain searches, fingerprinting and proof-of-concept checks across many workers, and stores the results in one place.

That is useful for defenders and testers. It is also the first stage of many intrusions. MITRE ATT&CK calls this Active Scanning (T1595), part of the reconnaissance tactic. Nemo is therefore dual-use: the console alone does not tell you who runs it or why.

The name is common. This page covers the nemo_go recon platform that Odin Research observed, not other software named Nemo.

How Nemo works

The README describes a distributed design:

  1. Web console. A login page and dashboard where the operator creates tasks and reviews results.
  2. Server. It receives tasks and hands them out through RPC and a message queue.
  3. Workers. Distributed nodes that run the actual scans. Spreading work across workers speeds up large jobs and spreads scan traffic over many addresses.
  4. Storage. Results go into MongoDB.

The project credits Go libraries such as Beego and rpcx. The README also lists an MCP server for integration with AI models, which lets an AI assistant drive the platform. See Securing MCP Servers and Tool Access for why that matters.

The README lists these collection features:

  • IP and port scanning with Masscan, Nmap and gogo.
  • Subdomain collection and brute-forcing with Subfinder and Massdns.
  • WHOIS lookups, IP geolocation and CDN detection.
  • HTTP and non-HTTP service fingerprinting, similar to banner grabbing.
  • Proof-of-concept validation with Nuclei.

The output is a map of what a target exposes, which services run there and which look vulnerable.

How attackers use Nemo

Reconnaissance platforms do the slow, boring work before an attack. Nemo builds and refreshes a list of live hosts, open ports and fingerprinted services. An operator can then pick the weakest targets for exploitation.

Odin Research places Nemo in the surface-discovery stage. In Monograph 18, Nemo sits beside ScopeSentry as a tool that enumerates subdomains, ports and admin paths. Both platforms automate subdomain enumeration, port scanning, web spidering and vulnerability correlation across distributed workers.

In Monograph 25, the same Nemo servers appear as recon and task controllers in a report on FortiGate edge kits and staging servers. Odin Research found nothing that links those controllers to the report's staging workbenches. Treat Nemo as a sign of mapping activity, not of a specific campaign.

What Odin Research observed

  • Six controllers, all confirmed. Monograph 18 counted six Nemo endpoints on six IPs. All six are confirmed Nemo instances, and all listen on port 5000.
  • Hosting. Five sit in China and one in the United States. Monograph 25 gives the split: three on Shenzhen Tencent, two on Hangzhou Alibaba and one on HostPapa.
  • Shared fingerprints. Five of the six share one JARM TLS fingerprint. The sixth presents the same kind of self-signed certificate, with an IP address as its common name.
  • From watchlist to block list. Monograph 18 placed the fleet on a watchlist as recon consoles. Monograph 25 published all six as confirmed controllers for blocking, with a reminder to re-check them because cloud addresses get reassigned.
  • A fingerprint look-alike. One candidate in a different family, on Contabo, shared the Nemo JARM on port 8443. A shared fingerprint groups similar server builds; it is not proof of the same software.

Six servers is a small fleet. Unlike many tool families, though, every one of them was confirmed, which makes Nemo a clean hunting target.

How to detect Nemo

  • Task dispatch. An outbound JSON POST to /v1/task/ on port 5000 matches Nemo task traffic. Inside your network, that means a host is feeding or running a Nemo console.
  • Self-signed IP certificates on 5000. Pair the certificate pattern with the JARM value from Monograph 25. Do not act on port 5000 alone, since many web applications use it.
  • Distributed scanning. In your perimeter logs, watch for the same scan pattern arriving from several cloud addresses at once. Nemo spreads work across workers.
  • Worker processes. On your own servers, scanners such as Masscan or Nmap running outside approved testing hosts deserve a look.

Monograph 25 publishes a Suricata signature (SID 9525007) for Nemo task dispatch, along with KQL, Sigma and YARA rules for the wider staging set. The rules and the published controller list are on the report page and in the Defense Kit.

How to defend against Nemo-style reconnaissance

You cannot stop someone from scanning the internet. MITRE notes that active scanning is hard to prevent, and suggests reducing the amount and sensitivity of exposed data. In practice:

  1. Map yourself first. External attack surface management shows you the same picture a recon platform builds.
  2. Remove what you do not need. Close stray ports, retire old subdomains and take admin panels off the internet. See our guide on unknown exposed assets.
  3. Patch what scanners will find. Fingerprinting plus Nuclei checks means known flaws on exposed services get found fast.
  4. Block confirmed controllers. Use the published Nemo addresses, and re-check them regularly.

Nemo compared with other recon platforms

PlatformWhat it doesWhat Odin Research saw
NemoDistributed asset discovery with port, subdomain, fingerprint and Nuclei checks6 controllers, all confirmed, all on port 5000 (Monographs 18 and 25)
ScopeSentryDistributed subdomain, port and web discovery120 consoles, 101 on default port 8082 (Monograph 18)
ARLAsset reconnaissance panel99 records in a scanner group (Monograph 02)
reNgineReconnaissance suite23 records in a scanner group (Monograph 02)

Monograph 02 is available here.

Frequently asked questions about Nemo

What is Nemo?

Nemo, published as nemo_go on GitHub, is an open-source platform for automated information gathering. It chains tools such as Nmap, Masscan, Subfinder and Nuclei to map internal and internet-facing assets.

Is Nemo malware?

No. It is a dual-use reconnaissance tool built for penetration testing and asset investigation. It becomes part of an attack when someone uses it to map systems they have no permission to test.

Is Nemo legal to use?

Scanning your own assets, or assets you are authorized to test, is legal. Scanning other organizations without permission may break computer misuse laws.

Who made Nemo?

The nemo_go project is published on GitHub by the account hanc00l. Its README credits several Go projects it builds on, such as Beego and rpcx.

What port does Nemo use?

All six Nemo controllers Odin Research observed listened on port 5000. The project README we checked does not state a default port.

How do I detect Nemo?

Look for outbound JSON POST requests to /v1/task/ on port 5000, self-signed IP-named certificates on that port, and distributed scanning from several cloud addresses. Odin Research publishes a Suricata signature for Nemo task dispatch in its Defense Kit.

Nemo vs ScopeSentry: what is the difference?

Both automate subdomain, port and web discovery across distributed workers. In Odin Research's data, ScopeSentry was far more common, with 120 consoles mostly on port 8082, while Nemo had six controllers, all confirmed, on port 5000.

Sources

  1. hanc00l, nemo_go README, GitHub. raw.githubusercontent.com/hanc00l/nemo_go/main/README.md (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