Hello, today I want to show you a short guide, how to get rid of leaking-pages. When you create a premium-resource you do not want to get it leaked on such sites. This short tutorial should show how to prevent that behavior and what you can do against it when your resource has already been leaked. What to do before leaking First of all, I want to start to explain, what you could do against it: 1. Save the Username of the Spigot-User into your plugin Spigot offers you to change the value of the following variable in your plugin: Code (Text): public static String USER = "%%__USER__%%"; By adding this code, the value %%__USER__%% will get replaced by the Spigot-UserID of the user. This could be used for a simple antipiracy-system which communicates with your server 2. Take a hash-value of your plugin-jar The hash value of each downloaded file on Spigot is different. By taking the hash-value of a downloaded file you can also create a simple antipiracy-system. This two methods can be extended by tracking the IPs also over a stats-system etc. The crackers are often only removing the antipiracy itself, so by tracking the IPs of the stats-data which is sent to your server and comparing it with the anti-piracy, you can easily get IPs, which are running illegal versions of your plugin. 3. Obfuscate your plugin A good anti-piracy would not work without a good obfuscation. There many obfuscators out there. A common, but not bad one is ProGuard. This makes leakers harder to read your code and take them more time to crack your software. So just give it a try, there many tutorials out there, how you could make your plugin obfuscated very well. What to do after leaking Now we get to the point, where your resource had already been leaked anywhere out in the web. Here you have also some good options to go against leaking-sites. 1. Contact Google to remove links from its web search Google offers to remove links, which are against valid copyright. So just collect the links and send them to Google via this form: https://support.google.com/legal/contact/lr_dmca?product=groups&uraw=&hl=en Google will contact you after one or two days and will remove these links. This is a good step to ban leaking-sites from the web. 2. Contact hosters of IPs If you found an IP which is using your plugin illegal, you can simply contact the hoster by searching them over their IP. The hoster will surely not host illegal content, as he would probably get problems by the police when doing so. Often the hoster will ban the user. Here you could also take a lawyer and get into court against the person, as the hoster needs to give the customer data to the police in such case. I hope this thread had overall helped you with leakers and gave you some good tips on how to get rid of them. I'm using them myself, too and I'm very happy with that Please note: This post should not be a discussion about DRM itself. It should give interested Developers some hints, how they could improve their software. Each person should decide on their own if an anti-piracy is a useful thing for their plugin.