Origasus

A Go program compiled with origasus.go, written for examining endpoints that can be associated with ASUS AiCloud / AsusWRT within the scope of authorized security testing or defense analysis (e.g., your own device, a pentest lab environment).

Important: The use of such software against unauthorized systems is illegal in most countries. Only run it with explicit permission and within a legal framework. Do not perform unauthorized scanning / exploitation in production or third-party networks.

Context

The relevant references mentioned in the source file's header comments (e.g., CVE-2025-2492, CVE-2024-12912, CVE-2025-59366 and vendor advisories) can be used for security patches and risk assessment. The program's purpose is to enable security researchers and defense teams to recognize and mitigate this class of attacks; misuse is not supported.

Requirements

• Go (can be compiled as a single file if no module file exists)

Compilation

In the project root:

go build -o origasus origasus.go

General behavior (high level)

• Reads target lines from standard input or a file specified with -f.
• Attempts to verify the target against ASUS AiCloud / AsusWRT indicators (to reduce false positives).
• Then tries chained steps via HTTP requests and variants defined in the file; successful attempts can be logged into exploited.txt (or the file specified with -exploited) and skipped on subsequent runs.

Detailed request bodies, payload variants, and usage in production environments are outside the scope of this README; details are left only for source code review and authorized response processes.

Command line flags

Positional arguments: manual, no-skip, multiport, tls, debug (processed in main in the source).

Co-running with Zmap: zmap -p 443 | ./origasus

Environment variables

Signal behavior

When SIGINT / SIGTERM is received, the process exits with code 124 (for external observers in long-running operations).

Disclaimer

This software is provided "as is". The authors and contributors cannot be held liable for damages arising from unauthorized or illegal use. For defense-side use, rely on logs, network traces, and vendor security bulletins.