Viper Red Team Platform
An all-in-one adversary simulation and red teaming platform with a built-in LLM Agent, visual UI, and 100+ post-exploitation modules covering the full MITRE ATT&CK framework.
- Source repo
- FunnyWolf/Viper
- Stars
- ★ 5.4k
- Last updated
- 5mo ago
- FA score
- 23/100 · Major gaps
At a glance
- How it runs
- Works with
- Universal · cross-platform
- Cost
- Free, no paid service needed
- Setup effort
- Medium · a few setup steps
- You'll need
- Typical use
- An authorized red team needing long-running monitoring of a target environment via 24/7 automated workflows and notifications
- Not a fit if
- Teams looking for purely defensive vulnerability scanning
- Organizations without authorization for offensive testing
- Users who need a hosted SaaS and cannot run their own server
- Website
- viperrtp.com ↗ set on GitHub
- Maintenance
- Commits in the last 6 monthslast commit 2026-05-31
- Source review
- 23/100 · Major gaps 6 safety controls not found
What does this agent do, and when should you use it?
VIPER is a self-hosted red team and adversary simulation platform that combines Cobalt Strike-style team operations, Metasploit-ecosystem capability, and a built-in Large Language Model agent. It offers an intuitive web interface for launching assessments, implant management across Windows, Linux and macOS, a visual pivot graph, and automated notifications. The platform ships more than 100 post-exploitation modules spanning all stages of the MITRE ATT&CK framework and supports Python-based custom module development. Repository topics include mcp-server, indicating MCP-based integration capability. Distribution goes through an official Docker Hub image (viperplatform/viper) with documentation and a getting-started guide at viperrtp.com. A product comparison table in the README positions Viper as a free alternative to Cobalt Strike, NightHawk, and BruteRatel.
Once deployed, Viper serves a web UI where red team members launch and manage security assessment tasks: implants are deployed to Windows, Linux, or macOS targets; the visual pivot graph maps compromised network topology; and the 100+ built-in post-exploitation modules execute actions across MITRE ATT&CK stages. A built-in LLM agent adds automated processing and intelligent decision support; automation workflows support 24/7 monitoring of target environments with orchestration and notifications. Anti-tracing, handler firewall, and defense evasion features are built in. Team collaboration allows multiple operators to share sessions. The mcp-server topic further suggests MCP-protocol integration into other tooling.
- An authorized red team needing long-running monitoring of a target environment via 24/7 automated workflows and notifications
- A pentest team replacing per-year licenses costing $12,600 (Cobalt Strike), $10,000 (NightHawk) or $3,000 (BruteRatel) with the free Viper
- Assessment projects that must attack Windows, Linux, and macOS hosts from one platform
- Security teams wanting an LLM agent to assist decisions and automate post-exploitation steps
- Scenarios requiring custom attack modules, written in Python against Viper's module API
- Workflows integrating red team capability into an AI toolchain via the MCP server
Key setup facts
Pulled from the install and usage notes below. The project README has the current values.
- Install / run
docker pull viperplatform/viper
- Install notes cover
- Windows · macOS · Linux · Docker
How do you install or deploy this agent?
The README does not include verbatim install commands, but it points to the official Getting-Started documentation and provides an official Docker Hub repository (viperplatform/viper), indicating Docker is the documented deployment path. Exact steps live in the official docs:
Getting started: https://www.viperrtp.com/guide/getting_start
Documentation: https://www.viperrtp.com/guide/welcome_to_viper
Docker Hub: https://hub.docker.com/u/viperplatform# Deployment is Docker-based per the official docs; the exact compose file
# and environment variables are not listed in this README.
docker pull viperplatform/viperMissing information: the README does not contain the concrete docker run/compose command, required ports, or initial credentials needed for a first run; consult the Getting-Started page for those.
How do you use this agent?
After deployment, open Viper's web UI in a browser, create an assessment task, and generate implants for Windows/Linux/macOS targets. Use the visual pivot graph to track compromised topology, pick from 100+ post-exploitation modules to execute actions, or delegate steps to the built-in LLM agent. Configure automated workflows for round-the-clock monitoring and notifications. To extend the platform, write custom Python modules. Full operational details: https://www.viperrtp.com/guide/welcome_to_viper .
What are this agent's strengths and limitations?
- Free, versus $12,600/user/year for Cobalt Strike, $10,000 for NightHawk, and $3,000 for BruteRatel in the README comparison
- The only platform in the comparison with a built-in LLM Agent for automation and decision support
- Implants cover Windows, Linux, and macOS, while Cobalt Strike, NightHawk, and BruteRatel support Windows only
- Built-in evasion and anti-tracing, with custom plugins written in Python — a lower barrier than Cobalt Strike's CNA scripting
- Includes team collaboration and a visual pivot graph, matching core capabilities of commercial red team platforms
- Requires self-hosting and maintaining a server (Docker-based); no vendor-hosted SaaS mode is offered
- As an offensive tool it must only be used within authorized scopes for red teaming and adversary simulation
- The repository's License field is marked unknown; verify the actual license terms before adopting
- Concrete getting-started commands are not in the README, so first deployment requires reading the external documentation
- Not compatible with the Cobalt Strike CNA plugin ecosystem; migrating existing tooling means rewriting in Python
How does this agent compare with similar options?
The README includes a direct comparison: versus Cobalt Strike ($12,600/user/year), NightHawk ($10,000), and BruteRatel ($3,000), Viper is free, supports implants on all three major operating systems, and is the only one with a built-in LLM Agent, plus Python custom plugins and automation. Cobalt Strike offers team collaboration and pivot graph but lacks automation and an LLM agent; NightHawk and BruteRatel lack team collaboration. Relative to the Metasploit Framework, Viper adds a visual UI, collaboration, and LLM automation (the metasploit-framework topic suggests ecosystem linkage).
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| Viper Red Team Platform This agent | 23 · Major gaps | Self-hosted serviceFree | ★ 5.4k | 5mo ago | — | — |
| LazyOwn RedTeam / APT Framework | 41 · Major gaps | CLIFree + model costs | ★ 302 | 1d ago | Python | Claude Code |
| CyberStrike — Open-Source AI Penetration Testing & Red Team Platform | 39 · Blocked | CLIFree + model costs | ★ 3.7k | 1d ago | TypeScript | — |
| RedAmon: Autonomous AI Red Team Framework | 69 · Some gaps | CLIFree + model costs | ★ 3.5k | 1d ago | Python | OpenAI API · Claude API |
How does FollowAgents rate this agent?
Why each dimension lost points
Almost no evidence for trust criteria. The packet contains only README and a docs-site package.json; no LLM Agent source, SKILL.md, or permission declarations, so least_privilege, user_confirmation, data flow, sensitive data handling, and rollback are scored 0. Dependencies are declared as version ranges without lockfile or audit info, so dependency_security is 1. README shows no authorization gating, target confirmation, or destructive-action safeguards for an offensive-simulation product, so external_effects is 0. Attribution traces to FunnyWolf/Viper and viperrtp.com, but license metadata is unknown, so source_attribution is 1.
No agent code, tests, or error-handling logic in the packet; failure_messages and behavioral consistency cannot be assessed (0). package.json dependencies are complete and match the docs scripts, giving dependency_availability and self_consistency 1 at the declaration level only.
README clearly targets red-team/adversary-simulation users with stated multi-OS support (audience_and_scenarios 2). Environment fit is asserted without configuration detail (1). The LLM Agent's capability boundaries and triggers are not shown at all (capability_boundaries 1, trigger_precision 0).
README is well structured, bilingual, with consistent naming (VIPER/viperrtp) (naming_stability 2); active-commit and community badges support maintenance_responsibility 2. Install instructions are an external link only, no FAQ/example content in the packet, and versioning rests on a badge alone (each 1). License metadata is unknown (0) and known_limitations are entirely absent (0).
The packet does not show the agent's actual output format or workflows, only marketing screenshots and feature lists (output_usability 1). Differentiation claims versus commercial C2 products are tabulated but unverifiable here (marginal_value 1, cost_benefit 1).
Most functional claims (100+ modules, evasion, automation) have no in-packet source corroboration (claim_traceability 0). The bilingual README and comparison table partially corroborate positioning (cross_source_corroboration 1). Marketing adjectives are not separated from factual claims (fact_inference_separation 1).
- Not found in source: least-privilege scopingGrant only what the task needs: a dedicated account or read-only token, scoped to specific directories and repos.
- Not found in source: confirmation before actingTurn on (or add) a confirmation step before it acts, and try it in a sandbox or test environment before real data.
- Not found in source: data-flow disclosureWatch which external services it contacts (proxy or firewall logs) and keep sensitive data out until you know where it goes.
- Not found in source: sensitive-data handlingUse dedicated, low-privilege, revocable API keys — never production credentials — and keep secrets out of logs.
- Not found in source: disclosed external effectsEstablish which external systems it writes to, sends to or changes, and verify with test accounts or repos before production.
- Not found in source: rollback or recovery pathBack up first, or work on a git branch or snapshot, so its changes can be undone.
- Packet evidence covers only README and docs-site configuration; the LLM Agent's own code is entirely absent, so scores reflect only the visible sample at low static-review confidence.
- The product is an adversary-simulation/C2 platform and a strongly dual-use tool: use only within written authorization; deployment grants real offensive capability against target systems.
- License metadata is unknown; confirm licensing terms before commercial or internal adoption.
- README provides no authorization confirmation, operation auditing, or destructive-action safeguards; verify such controls independently before adoption.
- Dependencies are version ranges without a lockfile, and the docs site pulls Vercel/Google analytics packages; watch supply-chain and data-egress risk.
FAQ
Is Viper free?
What runtime does it need?
Which target operating systems are supported?
How does the LLM agent work, and are there extra API costs?
Can it replace Cobalt Strike?
Is Viper Red Team Platform open source?
Is Viper Red Team Platform safe to use?
Is Viper Red Team Platform still maintained?
Who makes Viper Red Team Platform?
What is Viper Red Team Platform's official website?
Thanks — we use this to improve the page.