I'm asking this because the last 6 months at least has been a whack-a-mole game. Hashes are different each time, and so are IPs. You can ban them all you want, but they appear to start anew in the very next search. You've seen them already: 657 kb ZIPs, 4.13 Mb MP3s, 5.15 MB MOVs and the like.
Also, there are usually batches of search hits with the same indicated speed, despite completely disparate IPs, which would normally be highly unlikely.
Before this, there were fake files, but the search results were real. That's why filtering was generally effective. This time, my guess is that these search results are faked. Consequently, filtering is useless: one is banning fake IPs and fake hashes, instead of banning the ones who are sending these results. However - and this is my understanding of the protocol - you can't really do that either, because search hits are cached across the network, so one doesn't know whether these hits originated with the one who is sending them, or are merely being passed along.
Is this an accurate description of the situation? While this is probably not a major annoyance at the moment, is there a way to combat the problem?