wikiZ/RedGuard

Health v2 · maintenance only

Adoption not part of the score

1567 stars · 209 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

RedGuard is a C2 front flow control tool written in Go that acts as a filtering reverse proxy in front of command-and-control servers. It hides C2 infrastructure from blue teams, AVs, EDRs, and cyberspace search engines by intercepting, validating, and redirecting suspicious traffic.

Use cases

• hide c2 server traffic from blue team detection
• filter sandbox and analyst requests to my c2 infrastructure
• prevent c2 server discovery by cyberspace mapping engines
• set up domain fronting and load balancing for c2 channels
• restrict c2 callbacks to specific ip whitelists and time windows
• validate inbound requests against a malleable c2 profile
• log and trace blue team attribution attempts against my c2

When to choose

• you run C2 infrastructure during authorized red team exercises and need traffic filtering
• you want to block sandbox, EDR, and scanner probes from reaching your C2 server
• you need malleable profile validation or domain fronting without modifying the C2 source

When to avoid

• you need a general-purpose reverse proxy or WAF for legitimate production traffic
• your use case is defensive blue-team monitoring rather than offensive operations
• unauthorized use - it is designed for offensive security testing

Facets

cli-tool · maturity active

proxy security networking middleware security penetration-testing networking censorship-circumvention windows cross-platform cli c2 red-team traffic-filtering cobalt-strike malleable-c2 ja3 domain-fronting reverse-proxy linux macos

Member repositories

For agents

markdown · JSON · MCP: product_card(name="wikiZ/RedGuard")