explaingit

schich/lucky-arc

Analysis updated 2026-05-18

6CAudience · developerComplexity · 4/5Setup · hard

TLDR

A reverse shell and command and control tool that uses a pseudoconsole and encrypted websockets to evade detection.

Mindmap

mindmap
  root((Lucky-Arc))
    What it does
      Reverse shell client
      C2 server
      Pseudoconsole terminal
      Encrypted websocket traffic
    Tech stack
      C
      Pseudoconsole API
      Websockets
    Use cases
      Red team engagements
      Penetration testing exercises
      Security tool research
    Audience
      Security researchers
      Red teamers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Study how a pseudoconsole based reverse shell avoids common detection signatures.

USE CASE 2

Use as a research reference for encrypted websocket based C2 communication.

USE CASE 3

Test detection tooling against a realistic reverse shell in an authorized lab environment.

USE CASE 4

Contribute to finishing the still-in-development C2 server component.

What is it built with?

CWebsocketsPseudoconsole

How does it compare?

schich/lucky-arcffmpegkit-maintained/ffmpeglibretro/race
Stars666
LanguageCCC
Last pushed2026-06-29
MaintenanceActive
Setup difficultyhardeasymoderate
Complexity4/52/53/5
Audiencedeveloperdevelopergeneral

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1h+

No build or usage documentation is provided yet, the server component is explicitly unfinished.

In plain English

Lucky-Arc is a security research project made up of two parts: a reverse shell client and a matching command and control, or C2, server. A reverse shell is a technique where a remote machine connects back out to an operator's machine and gives them a command line on the target, and a C2 server is the operator side tool that manages these connections. What sets this project apart from a basic reverse shell, according to the README, is how the client presents its terminal. Instead of launching PowerShell with options that tend to look suspicious to security monitoring tools, it uses something called a pseudoconsole. This has a practical side effect for whoever is using it: normal terminal features like tab autocomplete, ctrl-c, and the arrow keys work the way they would in an ordinary terminal session, rather than behaving oddly the way many simple reverse shells do. Communication between the client and the C2 server happens over encrypted websockets, which is meant to make the network traffic harder to distinguish from ordinary encrypted web traffic and harder to flag through detection tools. The README is short and states plainly that the project is still under active development, with the server side in particular noted as unfinished. There is no build documentation, usage instructions, or license information included at this time. This kind of tool is typically associated with red team and penetration testing exercises, where security professionals simulate attacks against systems they have explicit permission to test.

Copy-paste prompts

Prompt 1
Explain how using a pseudoconsole instead of a hidden PowerShell window helps this reverse shell avoid detection.
Prompt 2
Walk me through how encrypted websocket communication works between this client and its C2 server.
Prompt 3
Help me understand what a pseudoconsole is and how it differs from a regular terminal spawn.
Prompt 4
Show me what parts of the C2 server are still marked as unfinished in this project.

Frequently asked questions

What is lucky-arc?

A reverse shell and command and control tool that uses a pseudoconsole and encrypted websockets to evade detection.

What language is lucky-arc written in?

Mainly C. The stack also includes C, Websockets, Pseudoconsole.

How hard is lucky-arc to set up?

Setup difficulty is rated hard, with roughly 1h+ to a first successful run.

Who is lucky-arc for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.