Website

Created By
FunnyWolfa year ago
Adversary simulation and Red teaming platform with AI
Overview

What is Viper?

Viper is a powerful adversary simulation and red teaming platform that integrates essential tools and functionalities for conducting cybersecurity assessments efficiently.

How to use Viper?

To use Viper, users can access the platform through its website, where they can find documentation and guides to get started with red team operations.

Key features of Viper?

  • User-friendly interface for rapid task initiation
  • Multi-platform support for Windows, Linux, and macOS
  • Comprehensive tools covering all phases of the MITRE ATT&CK framework
  • Integrated Large Language Model (LLM) agent for enhanced automation
  • Automated workflows for continuous monitoring
  • Over 100 built-in post-exploitation modules
  • Custom extensibility with Python-based module development
  • Advanced features including anti-tracing and automated notifications

Use cases of Viper?

  1. Conducting red team assessments across various operating systems
  2. Simulating attacks based on the MITRE ATT&CK framework
  3. Automating security assessments and monitoring target environments

FAQ from Viper?

  • Is Viper free to use?

Yes! Viper offers a community edition that is free to use.

  • What platforms does Viper support?

Viper supports Windows, Linux, and macOS for red team assessments.

  • Can I create custom modules in Viper?

Yes! Viper allows for Python-based custom module development to meet specific needs.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
FunnyWolf
Star
4313
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago