portbuster1337/ArachneC2
Test summary sentence one. Test summary sentence two.
What it is
ArachneC2 is a public GitHub project (GPLv3) implementing a fully decentralized C2 framework over libp2p. Beyond the summary's capability list, the page exposes the concrete detection surface a defender would hunt on โ transport choices, on-disk artifacts, and the specific evasion behavior โ because there is no server or domain to block.
How it works
Operator and implants are equal peers. On first run the operator generates ~/.arachne/operator.key and ~/.arachne/operator.pub. Implants embed the operator's public key and a unique persistent keypair, so each implant keeps the same libp2p PeerID across restarts. Discovery is via DHT; commands ride per-implant PubSub topics; shell and port-forward use direct libp2p streams (PTY on Linux/macOS, hidden ConPTY on Windows). Messages are Protocol Buffers with deliberately opaque identifiers โ package apb with Z-series message types, RPC service S, methods M0โM13.
Preconditions / Affected
Cross-platform (Linux, macOS, Windows), amd64/arm64. Notably, transport is WebSocket + TCP only โ UDP/multicast-free, explicitly for sandbox compatibility, so purely UDP-focused network detection will miss it. Relay nodes see only encrypted bytes.
What to do
This is offensive tooling with no patch. Defensive/hunting angles the page hands you:
- Host artifacts: the operator directory
~/.arachne/containingoperator.key/operator.pub. - Persistent PeerID per implant survives restarts โ a stable pivot for tracking a known sample.
- Sandbox/VM evasion: the
--antivmbuild runs 65+ checks (CPUID signatures, MAC prefixes, DMI/SMBIOS, PCI vendor IDs, registry keys, container detection) with VMAware-compatible scoring and exits cleanly when the score exceeds 50% โ detonation environments must score below that threshold to observe behavior. - Default hardening: implants ship UPX-packed (
--upxdefault true), optionally garble-obfuscated.
Caveats
"No IPs to block" is real for takedown but not for endpoint detection โ implants still run local processes, spawn shells, and touch ~/.arachne. Cover traffic masks beacon timing, not the existence of libp2p/WebSocket connectivity.
Technologies named here
Techniques named here
- Decentralized C2 infrastructure via p2p network
- Beacon-mode implant communication
- Cover traffic
- Binary obfuscation
- VM/sandbox detection
- Quiet/stealth execution mode
- Hidden interactive shell
- NAT traversal / hole punching
- Port forwarding through implant
- Opaque protocol identifiers
- Per-implant command topics
- Persistent implant identity
- Relay stream keepalive
Related in Offensive Security