ops-proxyns

Route all TCP, UDP, DNS, and ICMP traffic through Tor via Linux network namespaces.

1.1k|191|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/uphiago/recon-skills --skill ops-proxyns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ops-proxyns
Source: https://github.com/uphiago/recon-skills/tree/main/redteam/ops-proxyns
Command: npx skills add https://github.com/uphiago/recon-skills --skill ops-proxyns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standard proxy tools like proxychains fail to anonymize traffic for statically compiled binaries, leak DNS queries, and can be bypassed by applications, leading to source IP exposure during penetration tests that can result in blocked access, tracking, or legal consequences for unauthenticated testing.

Core Features & Use Cases

  • Kernel-level traffic routing: Uses Linux network namespaces to force all TCP, UDP, DNS, and ICMP traffic through Tor, working with Go, Rust, and static binaries that fail with LD_PRELOAD-based tools.
  • Complete leak prevention: Blocks IPv6 leaks, eliminates DNS leaks, and prevents applications from bypassing the proxy to expose your real IP.
  • OPSEC automation: Includes built-in Tor circuit rotation, configurable stealth headers, request jitter, and a pre-test checklist to avoid detection, rate limiting, and honeypot triggering during reconnaissance and exploitation.

Quick Start

Use the ops-proxyns skill to set up a kernel-level Tor-routed shell at the start of your authorized penetration test engagement to ensure all subsequent scanning, enumeration, and testing traffic is fully anonymized with no IP or DNS leaks.

Frequently Asked Questions about ops-proxyns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route all traffic through Tor without DNS or IP leaks during a pentest?

Tor traffic routing via kernel-level network namespaces forces all TCP, UDP, DNS, and ICMP traffic through Tor, preventing applications from bypassing the proxy and exposing your real IP during penetration tests.

Why does proxychains fail to anonymize traffic for Go and Rust binaries?

Proxychains fails for Go and Rust binaries because LD_PRELOAD-based proxy solutions do not work with statically compiled tools, whereas kernel-level network namespace routing handles all binary types seamlessly without relying on library preloading.

Can I prevent IPv6 leaks when using Tor for offensive security engagements?

Yes, you can prevent IPv6 leaks during offensive security engagements by using network namespace routing that explicitly blocks IPv6 traffic, ensuring no packets bypass the Tor tunnel and expose your source IP.

Does network namespace Tor routing work with subdomain enumeration and vulnerability scanning?

Network namespace Tor routing fully supports subdomain enumeration and vulnerability scanning workflows by transparently anonymizing all reconnaissance traffic, complete with configurable stealth headers and request jitter to avoid rate limiting and detection.

How do I avoid triggering honeypots and rate limits during reconnaissance over Tor?

Avoid triggering honeypots and rate limits during Tor reconnaissance by using built-in Tor circuit rotation, configurable stealth headers, and request jitter, which randomize traffic patterns to prevent detection and blocking.

What are the limitations of using LD_PRELOAD-based proxy tools for traffic anonymization?

LD_PRELOAD-based proxy tools are limited because they fail with statically compiled binaries, leak DNS queries, and can be bypassed by applications, leading to source IP exposure that kernel-level network namespace routing eliminates.