Piracy Distribution Network & Takedown Response

Distribution Network

Spread rate β 0.35

Code-signing coverage 40%

Takedown response speed Medium

Network density 3 links/node

Live Readouts

Pirated nodes

0 / 0

Detected (signed)

Taken down

Sim time

0.0s

How it works

Each node is a distribution point in a piracy channel graph — a torrent swarm, a warez mirror, a Telegram/Discord drop. The outbreak follows a discrete-time SIR-style contagion on the network graph:

P(clean node i gets infected this step) =
    1 - Π_{j ∈ neighbors(i), infected} (1 - β·dt)

β = spread rate slider (probability weight per infected neighbor per second)
dt = simulation timestep, clamped to avoid instability

Two independent defenses act on infected nodes every step:

Code-signing coverage — the probability an infected node's binary fails signature verification and is flagged as Detected on that step. Higher coverage catches pirated builds faster because more of the ecosystem checks signatures before executing.
Takedown response speed — once a node is Detected, this sets the hazard rate at which a DMCA/host takedown actually removes it from the graph (Taken down), cutting its outgoing edges so it can no longer infect neighbors.

A node's color shows its state: grey = clean, red = actively distributing pirated copies, amber = flagged by signature verification, dim = taken down and inert. "Seed New Release Leak" infects one random clean node, modelling a fresh cracked release entering the network. The system reaches a steady state when new-infection rate from β equals removal rate from detection × takedown speed — exactly the R₀-vs-recovery-rate balance that governs whether a leak dies out or saturates the network.

Clean node Distributing (pirated) Detected (flagged) Taken down

⚠ Couldn't load the 3D engineThree.js failed to load from the CDN. Check your connection and reload.