ArachneC2 - Decentralized C2 framework built on libp2p

项目说明

Arachne C2

<img width="1920" height="1080" alt="image" src=" />

A decentralized Command & Control framework built on libp2p (the peer-to-peer networking
stack behind IPFS). No servers, no domains, no IPs to block — just cryptographic identities
communicating over the global p2p network.

Inspired by Sliver, but redesigned for decentralized
infrastructure.

Key Idea

Instead of running a C2 server on a VPS that can be taken down, Arachne uses **GossipSub
(PubSub) and DHT peer discovery** over the IPFS peer-to-peer network. Your implant
fleet and operator are all equal peers in the network — no central point of failure.

Features

Project Structure

Build

The operator binary is self-contained — embed the implant source at build time, then it builds implants anywhere:

Binaries are written to bin/ as arachne-{os}-{arch} (or *.exe for Windows). The built binary can be copied to any machine with Go installed (or no Go — it auto-installs). No source tree needed.

Quick Start

1. Run the operator

On first run, generates a keypair at ~/.arachne/operator.key and exports the public
key to ~/.arachne/operator.pub.

2. Build an implant

From the operator console (generate) or standalone:

Flags: --os (linux, darwin, windows), --arch (amd64, arm64), --output, --pubkey, --upx (default true), --obfuscate, --quiet, --antivm.

Use --obfuscate to strip function names, package paths, and literal strings via garble (auto-installed if missing). Combine with --upx for maximum hardening.

Use --antivm to compile in . The implant runs 65+ detection techniques (CPUID signatures, MAC prefixes, DMI/SMBIOS, PCI IDs, process enumeration, registry keys, container detection) with a -compatible accumulated scoring system. Exits cleanly if the score exceeds 50%. Pure Go — no CGO, no cross-compilers needed.

Each build generates a unique embedded keypair — the implant keeps the same PeerID across restarts.

3. Deploy and run the implant

Copy ./myimplant to the target machine and run:

The implant will discover the operator via DHT, register itself, and begin beaconing
over a persistent relay stream with automatic keepalive.

4. Use the operator console

From the operator prompt:

A commands: list, select <n>, exec <cmd>, ls <path>, cd <path>,
pwd, ps, shell, portfwd <port> <host:p>, download <path>, upload <path>,
generate [flags], regenerate, help [command], exit.

In the interacti, type exit or press Ctrl+] to return to the arachne prompt.

Use help <command> or <command> --help for per-command details.

A Commands

| Command | Description |
|---|---|
| list | Show registered implants |
| select <idx> | Select implant by index |
| ps | List processes on selected implant |
| ls <path> | List directory |
| cd <path> | Change directory |
| pwd | Print working directory |
| shell | Interacti (direct libp2p stream, Ctrl+] to exit) |
| portfwd <port> <host:p> | Forward local port through implant |
| exec <cmd> [args] | Execute command (with output) |
| download <path> | Download file from implant |
| upload <src> <dst> | Upload file to implant |
| generate [flags] | Build an implant for any OS/arch (auto-installs Go, garble). Flags: --os, --arch, --output, --pubkey, --upx, --obfuscate, --quiet, --antivm |
| regenerate | Regenerate operator keypair (old implants orphaned) |
| help [command] | This help, or details for a specific command |
| exit | Quit |

Security

Disclaimer

This software is provided for educational and authorized security testing purposes only.
You must only use Arachne C2 on systems you own or ha written permission to test.
Unauthorized access to computer systems is illegal. The authors assume no liability and are
not responsible for any misuse or damage caused by this program.

License

GPLv3

项目信息

开发语言：Go

Star 数：470

技术要点

该项目属于红蓝攻防方向的开源资源，代码结构清晰，适合安全研究人员学习参考。项目围绕Decentralized C2 framework built on libp2p展开，提供了可运行的实现，对理解相关安全机制、工具原理与攻防技术具有较高的研究价值。

从技术实现角度看，此类项目的核心在于对底层原理的深入理解与工程化落地。开发者在研究过程中可以结合官方文档与社区讨论，梳理项目的初始化流程、核心模块职责与数据流转，逐步掌握其中的技术细节与设计思路。

使用与学习建议

1. 下载源码压缩包，解压到本地环境。

2. 根据项目类型准备对应的运行环境与依赖。

3. 按照 README 中的步骤完成配置与部署。

4. 在隔离的测试环境中运行验证，避免影响生产系统。

免责声明

本资源来源于开源社区，仅供安全研究、技术学习与合法授权范围内的攻防演练使用，请勿用于任何非法或侵害他人权益的用途。使用本项目产生的一切后果由使用者自行承担。