Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Odin Research / What is / C2 and post-exploitation

What Is the Viper Red Team Platform? How It Works and How to Detect It

A shared web console that puts Metasploit, post-exploitation modules and an LLM agent behind one login: what it is, where it shows up and how to spot it.

By
Odin by Brandefense
Updated
21 Nov 2026
Reading time
7 min read
Type
Offensive framework (red team platform)

In short

The Viper red team platform is an open-source adversary simulation tool from the GitHub author FunnyWolf. It wraps Metasploit in a browser interface for several operators, adds more than 100 post-exploitation modules and an LLM agent, and runs as a Docker container. Red teams use it for authorized tests. Attackers can run the same console.

Key takeaways

What it is
An open-source red team platform, published on GitHub by FunnyWolf, that drives Metasploit through a shared browser console with more than 100 post-exploitation modules.
How it works
A web front end talks to the Metasploit RPC daemon. Operators manage handlers, sessions and modules from the browser instead of msfconsole.
Why it matters
It lowers the skill needed to run Metasploit as a team. The same console can serve an authorized red team or a hostile operator.
What Odin Research saw
Viper had no endpoints of its own in Monograph 22. It sits on top of Metasploit and Meterpreter listeners, 22 of which were confirmed C2.
What to do first
Register every sanctioned Viper and Metasploit host. Put their consoles behind a VPN or mutual TLS, and alert on Viper API traffic from anywhere else.

What is the Viper red team platform?

The Viper red team platform is an open-source adversary simulation tool that wraps the Metasploit Framework in a shared browser console. It adds more than 100 post-exploitation modules, automated workflows and a built-in LLM agent. Red teams use it for authorized assessments, and attackers can run the same software.

The project is published on GitHub by the author FunnyWolf. Its README calls VIPER "a powerful and flexible red team platform" for adversary simulation and red team operations. It lists support for Windows, Linux and macOS targets, and tooling that covers all phases of MITRE ATT&CK.

Viper is not a new implant family. It is a management layer on top of Metasploit. The listeners and payloads it controls are Metasploit handlers and Meterpreter sessions. That matters for detection, because most network signals you will see belong to Metasploit, not to Viper itself.

Like Caldera and Starkiller, Viper is a dual-use tool. It is built for penetration testing, so finding one does not mean an attack is under way.

How the Viper red team platform works

Viper has three layers:

  1. The web console. A browser interface where several operators log in, see sessions, start handlers and launch modules. Odin Research's Monograph 22 describes it as a React and Ant Design multi-operator interface with an ATT&CK module runner.
  2. The platform backend. A Python service that stores state, runs automated workflows and sends notifications. The README says custom modules can be written in Python.
  3. The Metasploit engine. Viper talks to msfrpcd, the Metasploit RPC daemon. The Metasploit documentation describes this RPC as an HTTP and MessagePack interface, with SSL on by default.

An operator starts a handler from the console, a target runs the matching payload, and the session appears for the whole team. From there the operator runs post-exploitation modules, such as credential collection or lateral movement, from the browser.

The README also lists an integrated LLM agent for automation and decision support, a pivot graph, a handler firewall, anti-tracing and automated notifications. These features aim to keep a long engagement running with little manual work. They also make the platform attractive to anyone who wants Metasploit power without command-line skill.

Viper requirements, installation and deployment

According to the project's getting-started guide, Viper needs a Linux host with kernel 5.x or later, about 2 GB of free memory and 5 GB of free disk. The guide names Ubuntu 22.04, Kali Linux and Debian 11 as examples.

The recommended install is a script from the project site. The manual path installs Docker and runs the viperplatform/viper image with Docker Compose in host network mode. The guide says the web console listens on port 60000 over HTTPS, with the user name root and a password the operator sets.

The guide tells VPS users to open port 60000 and their handler ports in the firewall. It also suggests turning on anti-tracing to lower the chance of being flagged by threat intelligence platforms. Defenders should read that as a hint: operators expect to be hunted, and some will change defaults.

Is Viper legal? The software is free to download and use against systems you own or are authorized to test. Using it against anyone else is illegal in most countries.

Why the Viper red team platform matters to defenders

Team consoles change how an intrusion looks. Several operators can share one server, one set of sessions and one task history. Monograph 22 calls these shared team command-and-control consoles, and groups Viper with browser shell consoles such as SuperShell.

Three points matter for defenders:

  • Metasploit underneath. Every Viper session is a Metasploit or Meterpreter session. Existing Metasploit detections still apply, and they are usually the first thing that fires.
  • Post-exploitation at scale. Ready-made modules for credential access, discovery and lateral movement shorten the time between a foothold and a domain-wide problem.
  • Legitimate twins. Purple teams run the same console. Without an inventory of sanctioned hosts, a SOC cannot tell an approved test from a real intrusion.

Public vendor reporting that names Viper in a specific intrusion was not found for this page. Treat Viper as a capability to watch for, not as a signature of any one group.

What Odin Research observed

Viper appears in Monograph 22, which mapped 718 endpoints on 537 hosts running ten team C2 and emulation frameworks in a two-week window ending 18 November 2026.

  • No endpoints of its own. The report counts no Viper endpoints, because Viper drives Metasploit and Meterpreter listeners rather than exposing its own implant protocol.
  • The listeners it drives. Across 75 Metasploit endpoints and 18 Meterpreter endpoints, 22 were confirmed C2. One Meterpreter handler sat on the Remote Desktop port, so its traffic looks like RDP at a glance.
  • An exposed Metasploit tree. One unattributed server exposed a full Metasploit installation directory. The report notes that such a database-backed workspace can hold shared host tables, captured credentials and Viper session state. The owner's authorization is unknown.
  • Dual-use by design. The report lists Viper with Caldera, Starkiller, Empire and Metasploit as tools red and purple teams use legitimately. A listener alone does not show hostile intent.

How to detect the Viper red team platform

  • Viper API paths. Monograph 22 publishes a Suricata signature (SID 9522006) for URIs starting /api/v1/msf/, which catches Viper workbench API use. It needs TLS inspection to see HTTPS traffic.
  • Metasploit RPC logins. A companion signature (SID 9522007) flags auth.login requests to /api/ on ports 55552, 55553, 60000 and 3790. The Metasploit documentation gives 55553 as the RPC default.
  • Meterpreter behavior on endpoints. Memory allocation, remote thread creation and unbacked module loads shortly after outbound traffic to an unknown server are stronger than any port.
  • Odd ports. A browser console on 60000, or Meterpreter on 3389, from a host with no testing role deserves a look.

The Monograph 22 Sentinel query also flags console URIs such as /api/v1/msf/ and joins network hits with in-memory activity within 10 minutes. All rules are on the report page and in the Defense Kit. For rule formats, see YARA and Sigma rules.

How to defend against Viper and Metasploit-based intrusions

  1. Keep a register of sanctioned consoles. List every approved Viper, Caldera, Empire and Metasploit host in your SIEM allowlists. Anything outside the list is a lead.
  2. Lock down your own consoles. Put them behind mutual TLS or a VPN, change default credentials and never expose port 60000 to the internet.
  3. Turn off directory listing on staging and build servers, so a full framework tree is never published by accident.
  4. Watch memory, not just ports. Your EDR should alert on in-memory payload behavior. Join those alerts with egress logs during threat hunting.
  5. Block only confirmed listeners. Keep dual-use consoles on watchlists until a second signal appears.

The Viper red team platform compared with similar tools

ToolWhat it isEngine or agentNotes
ViperMulti-operator web consoleMetasploit via RPCNo own implant; detect the Metasploit layer and the Viper API
MetasploitExploit and C2 frameworkMeterpreter and other payloadsThe engine Viper drives
CalderaAutomated emulation plannerSandcat agentWidely used by purple teams
StarkillerWeb console for EmpireEmpire agentsSimilar shared-console model
Cobalt StrikeCommercial adversary simulationBeaconSee our Knowledge Hub profile

Frequently asked questions about Viper red team platform

What is the Viper red team platform?

Viper is an open-source red team and adversary simulation platform from the GitHub author FunnyWolf. It runs Metasploit behind a shared browser console and adds more than 100 post-exploitation modules and an LLM agent.

Is Viper malware?

No. Viper is a legitimate testing tool. It is dual-use, so attackers can run it too, but the software itself is published openly for red team work.

Is Viper legal to use?

Yes, on systems you own or have written permission to test. Using it against other systems is illegal in most countries.

Who made Viper?

The project is published on GitHub by the author FunnyWolf, with documentation on the project's own website.

What port does Viper use?

The project's getting-started guide says the web console listens on port 60000 over HTTPS. Handlers use whatever ports the operator configures.

Is Viper the same as Metasploit?

No. Viper is a management layer. It talks to the Metasploit RPC daemon, so the sessions and payloads it controls are Metasploit ones.

How do I detect Viper on my network?

Look for requests to /api/v1/msf/ paths, Metasploit RPC auth.login calls and Meterpreter behavior in memory. Odin Research publishes Suricata, Sigma and KQL rules for these in Monograph 22 and its Defense Kit.

Should I block every Viper console I find?

No. Red and purple teams use it. Keep unknown consoles on a watchlist and block only when a second signal, such as a confirmed Meterpreter handler, appears.

Sources

  1. FunnyWolf, Viper repository README, GitHub. raw.githubusercontent.com/FunnyWolf/Viper/master/README.md (checked 21 November 2026)
  2. Viper documentation, Getting started. www.viperrtp.com/guide/getting_start (checked 21 November 2026)
  3. Metasploit documentation, How to use Metasploit MessagePack RPC. docs.metasploit.com/docs/using-metasploit/advanced/RPC/how-to-use-metasploit-messagepack-rpc.html (checked 21 November 2026)

Related tools and terms

All Odin Research explanations · Brandefense glossary

Odin Research

Get the rules, not just the definition

Every Odin Research report ships with verified indicators and detection rules you can load today.

Open the Defense Kit