Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
sliver-gui — Cross-platform Electron GUI for the Sliver C2 framework, providing session and beacon dashboards, payload generation, listeners, loot, and cloud deployment management. | Kitploit
Tools/GitHubGitHub/sliverarmory/sliver-gui
Penetration Testing FrameworksPayload GenerationLateral MovementPost-ExploitationPenetration TestingCloud SecurityCommand and ControlUtilities & FrameworksRed TeamingRemote Access Tool
GitHub
176121992 days agoReviewed by Kitploit
sliverarmory/sliver-gui

sliver-gui

Cross-platform Electron GUI for the Sliver C2 framework, providing session and beacon dashboards, payload generation, listeners, loot, and cloud deployment management.

View Repository

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

Sliver GUI icon

Sliver GUI

Download the latest release

Sliver GUI is a cross-platform Electron desktop application for Sliver. It combines backend connections, live status views, dedicated workspaces, and a native Sliver console in a React interface built with HeroUI, HeroUI Pro, and Font Awesome.

Features

  • Multiple application windows with saved operator configurations, shared connections for matching configurations, and independent workspace state.
  • An Overview topology view, Sessions and Beacons dashboards, and dedicated interaction workspaces with Files, Processes, Environment, Registry, and Activity panels.
  • Generation, builds and profiles, jobs and listeners, Loot, and Credentials views.
  • Hosted Websites with site creation/deletion, standalone Monaco text editing, file and recursive directory imports, content replacement/deletion, MIME updates, and save-copy actions directly from content rows or source previews. Browser previews serve current content and website resources from a temporary loopback HTTP server. Read-only Monaco source and binary hex views remain available. See website limits and preview security.
  • Dedicated Sliver console and managed SSH windows with tabbed Ghostty terminals.
  • A standalone File → Remote Desktop client powered by IronRDP, with direct TLS connections with default NLA or remote-screen sign-in, saved profiles, certificate review, tabbed desktops, explicit text clipboard, and a sandboxed canvas viewer. It works without an operator configuration or a Sliver server connection. See RDP usage and architecture and verification.
  • Separate Armory, Network, and Cloud Deployment windows, including AWS and Azure account integration.
  • A Cloud Deployment DNS manager for Route 53 and Azure DNS, with zone and all-zones record views and record editing.
  • Configurable keyboard shortcuts, application appearance, and update controls.
  • Command palette navigation to live sessions and beacons by name, with host, user, and ID details to distinguish matching names.

The GUI does not implement every upstream command or option. Operator connections use mTLS; WireGuard operator configurations are recognized but cannot connect. See the operator parity report for tracked coverage and the feature documents below for specific boundaries.

Development

Requirements

  • Node.js 24.15 or newer on the 24.x line, or Node.js 26 or newer.
  • npm 11.19 or newer.
  • rustup for the bundled RDP helper; npm run setup:rdp installs the pinned Rust 1.94.1 toolchain and platform targets.
  • A HeroUI Pro license and authentication for its package artifact, you only need this license if you want to build the code from scratch. You can download prebuilt binaries from the Github releases.

The supported versions and locked dependencies are recorded in package.json and package-lock.json. Application code uses strict TypeScript; build helpers use Node.js ES modules.

Run locally

npm ci --strict-allow-scripts
npx heroui-pro login
npx heroui-pro install --yes
npm run setup:rdp
npm run dev

The HeroUI login/install steps are needed for initial workstation setup; they can be skipped when HEROUI_AUTH_TOKEN is already configured for installation. Keep credentials out of tracked files.

npm run dev builds and launches the static application at sliver://app/index.html, using the production content security policy. It also builds the host RDP helper from the pinned IronRDP fork. Ordinary TypeScript builds and unit tests do not require compiling Rust. Restart the command after source changes; this workflow does not use HMR.

The TypeScript client is installed from the pinned sliver-script npm package. An adjacent client checkout is not needed. Ordinary application development does not require a Sliver source checkout; building the native console does.

Local settings and configurations

The default Sliver client root is ~/.sliver-client; SLIVER_CLIENT_ROOT_DIR can select another root. Application preferences, including Overview graph options, are saved in gui/application-settings.json; workspace zoom is saved in gui/workspace-zoom.json, and text editor preferences in gui/text-editor-settings.json beneath that root. The GUI discovers existing operator configs in configs/ and updates the open selector when a valid config is saved there. It saves configs selected through Import as private file references in gui/operator-configs.json. Import and Forget do not copy or delete the source configs.

Remote Desktop profiles and endpoint certificate pins live in gui/rdp.json. Passwords are omitted by default, can be retained until app exit, or can be encrypted with the operating system's secure storage. Persistent passwords are unavailable when Linux selects an unencrypted key store. Clipboard transfer is explicit and limited to text; closing an RDP tab disconnects without logging off the remote Windows account.

Settings → General → Appearance → Disable window transparency turns off native window glass immediately across the app. The switch is off by default, so transparency remains enabled where supported. It is saved with the other application preferences and takes precedence over terminal transparency.

Ghostty-compatible terminal colors are configured in Settings → Terminal and saved to gui/ghostty/config. Custom themes belong in gui/ghostty/themes/; installed native Ghostty themes are discovered automatically. See terminal appearance and Ghostty themes for config sharing, the Monaco editor, platform transparency support, and runtime limits.

Commands

CommandPurpose
npm run typecheckCheck the main/preload and renderer TypeScript projects.
npm testRun Vitest unit and component tests.
npm run test:watchRun Vitest interactively.
npm run test:e2e:electronBuild and exercise Electron through its renderer, preload, and IPC.
npm run protocol:checkVerify the pinned client, upstream baseline, and parity artifacts.
npm run buildTypecheck and build application output in dist/.
npm run build:consoleBuild the pinned native Sliver console.
npm run build:rdp:hostBuild and verify the RDP helper for this machine.
npm run build:rdpBuild the RDP packaging target, including both macOS slices.
npm run test:rdp:nativeRun the Rust runtime tests.
npm run packageCreate an unpacked application under release/.
npm run distCreate platform installers under release/.
npm run test:e2e:packagedVerify and test an existing unpacked application against a local fixture.

Unit and component tests live beside source files; Electron scenarios live in src/e2e/. Actual-server tests are separate, opt-in checks requiring configured disposable infrastructure. A fixture test does not establish live-server or installed-package compatibility.

Download Tool