In short
XingRin (星环) is an open-source attack surface management platform published on GitHub by the author yyhuni under the MIT license. A master server sends subdomain, port, web and vulnerability scans to distributed worker nodes. Security teams use it to map their own assets. The same automation can map someone else's.
Key takeaways
- What it is
- An MIT-licensed attack surface management (ASM) platform that chains tools such as Subfinder, Naabu, HTTPX, Katana, FFUF and Nuclei behind one web console.
- How it works
- A master server schedules scan tasks across Docker worker nodes, local or on remote VPS hosts, based on their reported load.
- Why it matters
- Distributed workers spread scanning across many addresses. An MCP bridge also lets AI agents start XingRin scans directly.
- What Odin Research saw
- 11 XingRin endpoints on 10 hosts in China and Hong Kong, seven on port 8083. One was confirmed, on a dynamic telecom line, so it went to a 24-hour watchlist.
- What to do first
- Find out what scans you from the outside. Rate-limit noisy probing, and hunt XingRin worker processes on servers that have no scanning role.
What is XingRin?
XingRin (星环) is an open-source attack surface management platform that discovers assets, probes services, runs vulnerability scans and stores the results in one web console. It is published on GitHub by the author yyhuni under the MIT license. Defenders use it to map what they own, and attackers can point it at targets.
The README says the platform is meant for owned assets, authorized security testing and defensive research. It covers subdomain enumeration, port scanning, site discovery, fingerprinting, URL collection, directory scanning, screenshots and vulnerability detection.
Around those scans it adds platform features: target management, asset snapshots, blacklist filtering, scheduled scans, global search, CSV export, API keys and notifications to WeCom, Telegram and Discord.
XingRin sits in the same category as recon suites such as ARL and ScopeSentry. For the defender's view of this category, see Attack Surface Management (ASM and EASM).
How XingRin works
XingRin splits work between one master and many workers:
- The master server. It hosts the web console, stores targets and results, and schedules tasks. The README says it assigns tasks to workers based on load data cached in Redis.
- Worker nodes. Each worker runs the scanning tools in Docker. A local worker registers on its own, and remote VPS workers can be deployed over SSH. Workers send heartbeats with CPU, memory and disk status, and reconnect after an outage.
- The tool chain. The README lists Subfinder, Amass and PureDNS for subdomains, Naabu for ports, HTTPX and XingFinger for web fingerprints, Waymore and Katana for URLs, FFUF for directories, Nuclei and Dalfox for vulnerabilities, and Playwright for screenshots.
A typical job starts with a domain, expands it into subdomains, finds open ports and live web services, then runs template scans against them. Because many workers share the load, scans can come from many addresses at once.
XingRin also connects to AI agents. A separate open-source project, SurfaceMCP, offers a stdio MCP server that lets an AI client query, create and stop XingRin tasks, alongside ARL and ScopeSentry. Its NOTICE file says its adapter logic was adapted from CyberStrikeAI.
XingRin requirements, installation and popularity
According to the README, XingRin runs on Ubuntu 20.04 or later, or Debian 11 or later, on AMD64 or ARM64. It asks for 2 CPU cores, 4 GB of memory and at least 20 GB of disk. It is installed by cloning the repository and running an install script, with a mirror option for users in mainland China.
The web console listens on HTTPS port 8083. The install ships with a default administrator login, and the README tells users to change the password after the first login. Unchanged defaults on an internet-facing console are a common exposure.
The repository had 675 stars and 95 forks on 21 November 2026. The README says a new architecture with a Go backend is being built in a separate project, so the current code base may change.
Why XingRin matters to defenders
XingRin is not malware. It is a reconnaissance platform, and recon is the first step of most intrusions. Three features matter for defenders:
- Distributed scanning. Workers on several VPS hosts spread probes across many addresses, which weakens simple per-IP rate limits.
- Exploit-ready output. Nuclei and Dalfox results point straight at weak services, which shortens the path to Exploit Public-Facing Application (T1190).
- Agent control. With an MCP bridge, an AI agent can launch and read scans without a human at the console.
No public vendor report tying XingRin to a named intrusion was found for this page. Treat it as dual-use infrastructure.
What Odin Research observed
Monograph 20 studied seven specialized vulnerability agents across 285 endpoints. It grouped XingRin with Strix and RedAmon as tools that run web and API checks from containers.
- Small footprint. XingRin had 11 endpoints on 10 hosts, all in China and Hong Kong. Seven sat on port 8083, the README's console port.
- A shared default certificate. Five of the port 8083 endpoints presented a self-signed
CN=localhostcertificate with the same TLS fingerprint. One DeepAudit listener shared that fingerprint, so the report marks it hunt-only. - One confirmed, on a moving address. The single confirmed instance sat on a dynamic China Telecom line. Addresses there rotate between customers, so it went to a 24-hour watchlist, not a block list.
- Co-hosting. One Hong Kong host ran XingRin next to the AutoHunter route-discovery tool. Three more XingRin endpoints were suspected and seven were candidates. All XingRin addresses are withheld.
How to detect XingRin
- Worker heartbeats. Monograph 20 publishes Suricata SID 9520008, which matches an outbound
POST /api/xingrin/nodewith anX-XingRin-Token:header. A hit from inside your network means a worker is running there. - Worker processes. A Sigma rule in the same report flags container worker names such as
xingrintogether with port 8083. Each rule excludes only named, approved hosts. - Staged files. The YARA rule
ODIN_Strix_RedAmon_XingRin_Swarm_Composelooks for the XingRin route and token header in deployment files. - Inbound scan patterns. Waves of subdomain lookups, then port probes, then template scans from several cloud addresses fit a distributed recon run.
The rules are on the report page and in the Defense Kit. Pair the TLS fingerprint with an API route before acting. Fingerprint background is on our JARM page.
How to defend against XingRin-style scanning
- Scan yourself first. Run your own external attack surface inventory so you see what a XingRin worker would see.
- Patch what template scanners find. Nuclei templates track public flaws quickly. Prioritize internet-facing services in the KEV catalog.
- Rate-limit by behavior, not by single IP. Distributed workers defeat per-address thresholds.
- Govern your own tools. If your team runs XingRin, keep the console off the internet, change the default login and register every worker host.
XingRin compared with similar recon platforms
| Platform | Focus | Odin sightings | Notes |
|---|---|---|---|
| XingRin | ASM, fingerprinting, Nuclei and Dalfox scans | 11 endpoints (Monograph 20) | Master plus Docker workers; console on 8083 |
| ARL | Asset reconnaissance | 488 endpoints (Monograph 29) | Mostly on hosts in China, the US and Hong Kong |
| ScopeSentry | Asset discovery and scanning | 138 endpoints (Monograph 29) | Two servers ran it next to ARL; also reachable through SurfaceMCP |
| reNgine | Web reconnaissance | 41 endpoints (Monograph 29) | Dual-use; kept on watchlists |
Frequently asked questions about XingRin
What is XingRin?
XingRin (星环) is an open-source attack surface management platform on GitHub. It discovers subdomains, ports and web services, runs vulnerability scans and stores the results in one web console.
Is XingRin malware?
No. It is an MIT-licensed security tool built for owned assets and authorized testing. It is dual-use, because the same scans can map systems the operator has no right to test.
Is XingRin legal to use?
Yes, against assets you own or are authorized to test. Scanning other organizations without permission is illegal in many countries.
Who made XingRin?
The project is published on GitHub by the author yyhuni.
What port does XingRin use?
The README says the web console runs on HTTPS port 8083. Odin Research found seven of eleven XingRin endpoints on that port.
Does XingRin use AI?
XingRin itself is a scan platform. A separate open-source project, SurfaceMCP, exposes XingRin, ARL and ScopeSentry to AI agents over the Model Context Protocol.
How do I detect XingRin?
Look for worker heartbeats to /api/xingrin/node with an X-XingRin-Token header, and for xingrin worker processes on port 8083. Odin Research publishes Suricata, Sigma and YARA rules for these in Monograph 20.
XingRin vs ARL: what is the difference?
Both are Chinese open-source recon platforms. XingRin stresses distributed Docker workers and a Nuclei and Dalfox scan chain. ARL is a separate asset reconnaissance suite, which Odin Research found on 488 endpoints in Monograph 29.
Sources
- yyhuni, XingRin (星环) repository, GitHub. github.com/yyhuni/xingrin (checked 21 November 2026)
- RuoJi6, SurfaceMCP repository, GitHub. github.com/RuoJi6/surface-mcp (checked 21 November 2026)
Related tools and terms
What is CyberStrikeAI?
CyberStrikeAI is a public AI-driven offensive security platform. It spreads its operator interface, API and agent listener across several ports on one host and exposes tools through MCP.
AI offensive toolWhat is PentAGI?
PentAGI is an open-source autonomous penetration testing system that coordinates AI agents and security tools in containers.
AI offensive toolWhat is HexStrike AI?
HexStrikeAI is a public project that exposes many security tools to AI agents through the Model Context Protocol (MCP).
AI security toolWhat is DeepAudit?
DeepAudit is an open-source AI code auditing tool. Application security teams use it to find flaws in source code.
AI security toolWhat is AutoCVE?
AutoCVE is an AI-assisted tool that turns new vulnerability advisories into HTTP checks.
AI security toolWhat is Cairn?
Cairn is a reconnaissance tool that keeps an asset graph built from DNS zones, TLS certificates and HTTP banners.
Odin Research
Get the rules, not just the definition
Every Odin Research report ships with verified indicators and detection rules you can load today.