http://ciisqbg45nggykdl6rjdrq3wc64csga4vkphu66qsi65mypeitqedoad.onion/blog/wireguard-privacy-concerns
The page sends a request to a back-end API server, which adds that IP/PSK/key to all of the VPN servers and also stores the IP/PSK/key in a database (explained below). If a user suspects that their internal 10.10.x.x IP is compromised (via WebRTC/STUN or whatever), they can go to http://ciisqbg45nggykdl6rjdrq3wc64csga4vkphu66qsi65mypeitqedoad.onion/wireguard_man and remove that IP/PSK/key from the auth database (and all of our VPN servers), then replace them with new ones....