Only one way to know.
You need to think bigger, nya. Build a list of IP ranges containing potential seedboxes, based on the prefixes announced by the AS numbers of the most popular hosting providers. Then use Zmap to scan TCP ports above 1024 on all of them. You will end up with thousands of results, which are impossible to add by hand, or even through the Peer Injector plugin; at this point you can write a local HTTP server that reads them from a file and serves them as a regular bencoded tracker response... hint: clients will accept a non-compact peers/peers6 even when they asked otherwise. Repeat the scanning procedure periodically and/or whenever your current list dries up. (There's another argument in favor of IPv6: the vast immensity of its address space makes port scanning effectively infeasible.)I know this is super old but i have like a few ip's on TorrentLeech that i'd like to try it on but my system doesn't work with the latest utorrent app XD.
Note that even if you had the IP and port of every BitTorrent peer in the world, that won't do much for you without the info_hash for the torrent(s) you want to download. Obtaining such information in a way that can't be traced by tracker staff is a complex task, but I can think of at least two workarounds, and one way to abuse server-side logging to frame an innocent account for facilitating ghostleeching, but that's beyond the scope of this discussion.
It's also noteworthy that BiglyBT's Fast Resume feature will cache known peers on a per-torrent basis, up to 512 by default (can be set to unlimited), and with no expiration date. This would allow building peer lists for ghostleeching as part of regular client usage.
After typing all this I almost want to start writing the "local peer injector tracker", but I'm not sure there's a lot of demand for that. I think most people either use the "remove tracker URL" method or manually build customized peer lists for the trackers they belong to.
Bookmarks