Skip to main content
D0pam1ne Black Hole Beacon The Black Hole Beacon is the internal side of D0pam1ne. Where recon maps a client from the internet, the beacon maps it from the inside: you drop one lightweight agent on a machine in each client site, it discovers every device around it, and the console then reaches deeper through it with internal recon and internal attacks. Nothing is installed on the client’s other machines. Everything it finds lands in the same project as ordinary hosts, services and findings, tagged Internal and filed under the beacon’s site, so a test can cover the external surface, the internal network or both, and a report can carry either side or the two together.
How the Black Hole Beacon feeds D0pam1ne Pro

Where the beacon sits: inside the client network, feeding D0pam1ne Pro outbound only

How it works

1

Deploy

Name the beacon, label its site, pick the platform and run the one-line installer on a machine inside the client network. See Deploy a beacon.
2

Discover Assets

The beacon sweeps its own network without any pivot: every live device with its OS, device type, vendor and MAC, and the Wi-Fi around it. This sweep is the baseline everything else builds on. See Discover Assets.
3

Internal Recon

The console scans hosts, ranges and ports through the beacon’s pivot, then adds service versions, live web, crawling, TLS checks, screenshots and nuclei. See Internal Recon.
4

Internal Attacks

Evidence-driven attacks against what recon proved, through the same pivot, filed as internal findings for review. See Internal Attacks.
5

Review and report

Internal findings land in the same Needs Review inbox as the external ones. Report them in the pentest report, hand over an Asset Mapping Report of the whole internal network, and send them to the client through Synapse.

What makes it safe to run inside a client

Outbound only

The agent only ever connects out to your console on a fixed interval. The console never reaches in, so it works from behind NAT and needs no inbound port or firewall change at the client.

One-time enrolment

The install command carries a one-time token that is traded for a long-lived agent key and then rotated out. Only the key’s hash is stored, and a copied command cannot enrol a second agent.

Kill switch

One click revokes a beacon. On its next check-in it reads the revoke and uninstalls itself from the host. The assets it already found stay in the project.

Nothing to fetch

The agent is a single dependency-free Go binary for macOS, Linux and Windows, served by your own console. Customers never compile anything and nothing is downloaded from outside.

Where to find it

The beacon has its own Internal Pentest section in the sidebar of an open project, in shades of the beacon’s electric indigo, next to External Pentest. It holds three groups: Beacon & Pivoting (the Black Hole Beacon overview and Deploy), Map & Attack (Discover Assets, Internal Recon, Internal Attacks) and Internal Results (Internal Assets, the Wireless Rogue Detector and the Asset Mapping Report). The Command Center has its own Black Hole Beacon band across every client: beacons online, internal assets found and a card per beacon.
The Black Hole Beacon is a paid module, licensed on its own and separately from Synapse. A standard build shows none of it until an admin activates a licence that includes it under System, Licenses.