In short
ScopeSentry is an open-source asset discovery and scanning platform. It maps subdomains, open ports, web pages and leaked information, then runs directory and vulnerability scans, spread across scan nodes the user deploys. Security teams use it for attack surface management. Attackers can use the same map to choose targets, so it is a dual-use tool.
Key takeaways
- What it is
- A self-hosted reconnaissance platform on GitHub, with a Python FastAPI server, a Go scanner and a Vue web console, licensed AGPL-3.0 with commercial terms.
- How it works
- A central server stores assets in MongoDB and queues tasks in Redis. Scan nodes do the work: subdomains, ports, crawling, directory and vulnerability checks.
- Why it matters
- Reconnaissance is the first step of most intrusions. A tool that maps a company's whole external footprint shortens the attacker's planning.
- What Odin Research saw
- 120 ScopeSentry consoles in Monograph 18 and 138 in Monograph 29, mostly on port 8082 in China, Hong Kong and the United States. All stay on watchlists.
- What to do first
- Map your own external assets first. Rate-limit scanning bursts, and keep ScopeSentry rules in alert mode rather than blocking.
What is ScopeSentry?
ScopeSentry is an open-source platform for asset mapping and scanning. It enumerates subdomains, scans ports, crawls websites, looks for leaked sensitive information and runs directory and vulnerability scans, with the work spread across scan nodes the user deploys. It serves defenders and attackers alike.
The project is published on GitHub under the account Autumn-27, with an English README and a Chinese version. It had about 2,600 stars and 669 forks on 21 November 2026. Related repositories hold the scanner, the web interface and a plugin template.
ScopeSentry belongs to the family of self-hosted attack surface management tools. A security team points it at its own domains to find forgotten hosts. An attacker points it at someone else's domains to find a way in. The software cannot tell the two apart.
How ScopeSentry works
According to its README, a ScopeSentry deployment has four parts, started together with Docker Compose:
- MongoDB, which stores assets and results.
- Redis, which holds task queues.
- The ScopeSentry server, written in Python with FastAPI, which serves the web console and API. The console is built with Vue.
- The scan service, written in Go, which runs the actual probing.
Users can add more scan nodes to spread work across several machines. The README lists the main features:
- subdomain enumeration, plus checks for subdomains left pointing at unclaimed services;
- port scanning and asset identification;
- crawling, URL extraction and page change monitoring;
- sensitive information leakage detection;
- directory and vulnerability scanning, with POC import;
- a plugin system for adding tools, and webhooks for alerts.
The result is a live inventory of a target's internet-facing footprint. That is exactly the reconnaissance stage of an attack, done automatically and kept up to date.
Is ScopeSentry legal to use?
ScopeSentry is licensed under AGPL-3.0, with extra terms. The project says companies and for-profit entities must obtain a commercial license before using, distributing or modifying it.
Scanning your own assets, or assets you have written permission to test, is legal in most places. Scanning someone else's infrastructure without permission can break computer misuse laws and the target's terms of service. Many organizations also block or report aggressive scanners.
How attackers use ScopeSentry
Attackers need a target list before they need an exploit. A platform like ScopeSentry builds one: every subdomain, open port, login page and leaked file it can find for a target organization.
Monograph 29 explains the risk plainly. ARL, ScopeSentry and reNgine map subdomains, ports and login portals, and attackers can use that map to choose phishing targets. Monograph 18 places ScopeSentry in a surface-discovery step ahead of lure delivery and TLS interception. Both reports present that chain as an analytical model, not one observed operation.
Leaked files and forgotten subdomains are the most valuable output. See our guidance on unknown exposed assets for how to find them first.
What Odin Research observed
- 120 consoles in Monograph 18. Monograph 18 counted 120 ScopeSentry endpoints on 118 addresses. Of these, 101 (84.2%) sat on port 8082, with a few on 18082 and 8443. Most were in China (37), Hong Kong (22) and the United States (17), on Tencent and Alibaba.
- Mostly candidates. In that study, 109 of the 120 were uncorroborated candidates. One candidate on Hetzner in Germany was seen on 18 November 2026.
- 138 consoles in Monograph 29. Monograph 29 counted 138 ScopeSentry endpoints on 136 hosts. Port 8082 held 119 (86.2%). The spread was China 43, Hong Kong 28, the United States 20 and Japan 11.
- Paired with ARL. Two Chinese servers ran ARL and ScopeSentry side by side.
- Watch, never block automatically. Monograph 29 kept 10 confirmed ScopeSentry consoles on a seven-day watch. Enterprise attack surface and penetration-testing teams run these suites too.
The lesson: a ScopeSentry console tells you someone is mapping the internet. It does not tell you who, or whether they are mapping you.
How to detect ScopeSentry scanning
- Console traffic. Monograph 18 documents
/api/requests carrying a ScopeSentry header to ports 8082 or 18082. Monograph 29 addsPOST /api/scan/createrequests with a"scan_engine"field. - Worker processes. On your own hosts, alert on ScopeSentry, ARL or reNgine worker launches outside approved security servers.
- Scan bursts at your edge. Distributed scan nodes show up as many sources sweeping subdomains, ports and common directories in a short window.
- Do not block on the port. Port 8082 hosts many unrelated web apps.
Monograph 18 includes a Suricata signature for ScopeSentry console API use. Monograph 29 adds a Suricata policy signature for scan creation and a Sigma rule for recon worker launches. Monograph 29 advises keeping these rules in alert mode, never drop mode. All are in the Defense Kit.
How to defend against automated reconnaissance
- Map yourself first. Run your own external attack surface discovery and retire forgotten hosts before a scanner finds them.
- Remove leaks. Delete exposed backups, source maps and
.gitfolders, and check that subdomains do not point at unclaimed cloud resources. - Rate-limit bursts. Throttle sources that sweep many paths or ports, rather than trying to block every scanner.
- Register approved scanners. Keep your own ScopeSentry or vendor scanner addresses on an allowlist so real alerts stand out.
ScopeSentry compared with other recon platforms
| Platform | Main ports Odin saw | Endpoints (Monograph 29) | Notes |
|---|---|---|---|
| ScopeSentry | 8082, 18082, 8443 | 138 | Multi-node scanning with plugins |
| ARL | 5003, 443 | 488 | 123 nodes share one TLS fingerprint |
| reNgine | 8082, 443 | 41 | Many keep a default example certificate |
| Nemo | 5000 | Not counted | 6 servers in Monograph 18 |
Frequently asked questions about ScopeSentry
What is ScopeSentry?
ScopeSentry is an open-source platform that maps subdomains, ports and web assets and runs directory and vulnerability scans across distributed scan nodes.
Is ScopeSentry malware?
No. It is a dual-use security tool used for attack surface management and penetration testing. Attackers can use it for reconnaissance, which is why defenders track exposed consoles.
Is ScopeSentry free?
It is open source under AGPL-3.0, but the project says companies and for-profit entities need a commercial license before using, distributing or modifying it.
Who made ScopeSentry?
The project is published on GitHub under the account Autumn-27. The README does not name an individual author beyond that account.
Which port does ScopeSentry use?
In Odin Research data, most ScopeSentry consoles listen on port 8082, with a few on 18082 and 8443. The port can be changed.
How do I detect ScopeSentry?
Look for ScopeSentry API requests and scan-creation calls in your traffic, unapproved recon worker processes on your hosts, and distributed scan bursts at your edge. Odin Research publishes Suricata and Sigma rules for these signals.
ScopeSentry vs ARL: what is the difference?
Both are self-hosted recon platforms. In Monograph 29, ARL was more common (488 endpoints, mostly on port 5003) than ScopeSentry (138, mostly on 8082). Two servers ran both side by side.
Should I block ScopeSentry servers?
Not automatically. Security teams use ScopeSentry legitimately. Rate-limit scanning that hits you and keep consoles on a watchlist unless you have other evidence.
Sources
- Autumn-27, ScopeSentry repository and README, GitHub. github.com/Autumn-27/ScopeSentry (checked 21 November 2026)
Related tools and terms
What is Interactsh?
Interactsh is ProjectDiscovery's open-source OAST server and client for catching DNS, HTTP and other callbacks.
OAST serviceWhat is Burp Collaborator?
Burp Collaborator is PortSwigger's callback service for Burp Suite, used to detect out-of-band vulnerabilities.
OAST serviceWhat is DNSLog?
DNSLog is a family of open-source DNS callback collectors used to confirm blind injection and SSRF flaws.
Offensive toolWhat is ezXSS?
ezXSS is an open-source collector for blind cross-site scripting (XSS) payloads. It records pages where a payload fires.
Interception proxyWhat is mitmproxy?
mitmproxy is an open-source interactive HTTPS proxy. It installs its own root certificate to read encrypted traffic.
Security testing suiteWhat is Yakit?
Yakit is a security testing suite with a desktop interface and a remote engine that can intercept traffic, fuzz web parameters and run exploit checks.
Odin Research
Get the rules, not just the definition
Every Odin Research report ships with verified indicators and detection rules you can load today.