git404hub

what is cyber-decoy fr?

secdev02/cyber-decoy — explained in plain English

Analysis updated 2026-05-18

3GoAudience · ops devopsComplexity · 4/5Setup · hard

tl;dr

Cyber-decoy is a containerized honeypot that observes network scans with eBPF and proxies attacker connections into fake SSH, RDP, and SMB decoys.

vibe map

mindmap
  root((cyber-decoy))
    What it does
      Network honeypot
      eBPF observation
      Reverse proxy to decoys
    Tech stack
      Go
      eBPF
      Docker
    Decoys
      SSH via OpenCanary
      RDP via OpenCanary
      SMB via Impacket
    Audience
      Network defenders
    Requirements
      Linux kernel 6.6+
      Docker Compose
    Isolation
      Internal decoy network
      No route to host

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 make with this?

VIBE 1

Deploy a honeypot on your own network to detect and log unauthorized scanning.

VIBE 2

Capture credentials attackers try against fake SSH, RDP, or SMB services.

VIBE 3

Observe port scans with eBPF even against ports the decoy does not serve.

what's the stack?

GoeBPFDockerOpenCanaryImpacket

how it stacks up fr

secdev02/cyber-decoy12vault/ravelalexremn/finalizer-doctor
Stars333
LanguageGoGoGo
Setup difficultyhardeasyeasy
Complexity4/52/53/5
Audienceops devopsdeveloperops devops

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

how do i run it?

Difficulty · hard time til it works · 1h+

Requires a Linux host with kernel 6.6+ for full eBPF observation and Docker Compose v2.24+.

The README does not describe the license terms in the excerpt shown.

in plain english

Cyber-decoy is a containerized network honeypot, meaning it is a defensive tool that pretends to be real services so it can watch and record who tries to break in. It advertises SSH, RDP, and SMB, the kinds of services attackers commonly probe on a network, and it is meant to be run only on networks the operator owns or is authorized to monitor. The project splits its work into two parts. A broker container watches every incoming connection using eBPF, a Linux kernel technology that lets it observe network traffic efficiently, including scans against ports it does not even serve. The same broker then acts as a reverse proxy, forwarding real connections into isolated decoy containers for the matching service, so attackers interact with something that behaves like a genuine SSH, RDP, or SMB server while every byte is logged. Four containers make up the system: the broker itself, and three separate decoys built on tools called OpenCanary and Impacket that simulate SSH, RDP, and SMB well enough to capture credentials attackers type in. The decoys sit on an internal Docker network with no route to the host or the wider internet, so nothing an attacker does inside a decoy can reach anything real. Running it requires a Linux host with a fairly recent kernel, version 6.6 or newer, for the deepest eBPF observation, along with Docker and its Compose plugin. On older kernels or on macOS, where Docker runs inside a virtual machine, the eBPF observation layer simply turns itself off while the proxy and decoys keep working normally, which the project treats as an acceptable fallback rather than a failure. Everything can be started with a small set of make commands, and the broker and each decoy emit structured JSON logs that make it possible to watch scanning and login attempts as they happen. The full README is longer than what was shown.

prompts (copy fr)

prompt 1
Explain how the broker container separates observation from proxying.
prompt 2
Walk me through deploying cyber-decoy on a Linux host with Docker.
prompt 3
Help me understand why eBPF is disabled when developing on macOS.
prompt 4
Summarize how the decoy containers stay isolated from my real network.

Frequently asked questions

what is cyber-decoy fr?

Cyber-decoy is a containerized honeypot that observes network scans with eBPF and proxies attacker connections into fake SSH, RDP, and SMB decoys.

What language is cyber-decoy written in?

Mainly Go. The stack also includes Go, eBPF, Docker.

What license does cyber-decoy use?

The README does not describe the license terms in the excerpt shown.

How hard is cyber-decoy to set up?

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

Who is cyber-decoy for?

Mainly ops devops.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.