Thread: My 20 golden rules to succeed at cheating

I hope some of you find this kinda useful. I have successfully cheated on very well-know trackers for 6 months up to now and I would like to share the rules I have strictly followed to achieve it.

inb4walloftext

• 1) Do not start cheating the first day you got into a tracker. Stay legit for some weeks. Instead, go for freeleechs, introduce yourself to the community, post comments, open threads, participate in polls and so on. A member with an insane ratio but 0 posts, 0 comments... is always more suspicious than an integrated an active one.
  
• 2) Never cheat as a 100% seed on a tracker-exclusive torrent impossible/hardly found outside the tracker. If you do, you must be able to legitimate you got that torrent from outside. Stay away from inner realeases unless you really downloaded them beforehand and could provide proof (be careful with showing creation/modification times on screenshots, instead they can be easily edited).
  
• 3) For the trackers that register not only ratio but seed time you may want to cheat (or legit) upload a pack of torrents simultaneously and not cheating always only on one. 1TB uploaded on only 1 or 2 torrents, and a seed time of 1 week will just look odd. Just grab some freeleech/low size torrents and leave them uploading at 1kb/s on your real client for some weeks to build a safe seeding time.
  
• 4) Stay away from "Top10s". You don't want to appear as one of the max uploaders, leechers, highest ratios, with max seeding time... Always try to go with the flow and never stand out.
  
• 5) Avoid abusing the flashing method, as most of trackers run a simple max upload script which will get you banned in a blink.
  
• 6) Don't use incremental uploads as weeks go on, as it would be fishy that first week you were uploading at ~100kb/s, next at ~150kb/s, next ~200kb/s...etc (given you are not getting caught), instead see point 13)
  
• 7) Never use a steady upload/download speed as a whole day uploading at 100.00 kb/s sharp is not a good idea, instead use some loosy ones (with decimals).
  
• 8) Try to cheat on mostly new torrents with a high amount of peers. Be careful with partial seeders as they will been shown as leechers but they won't produce any download traffic. Also try to stay within a logical range of upload given the torrent and actual peers. Make daily a quick sum of all the download speeds from leechers and upload speeds and never produce an upload higher than, say, 110% the download sum. If a torrent is reporting the tracker a 2MB/s download traffic and the summed upload rate is 3MB/s something is failing and this can be easily cross-checked with a simple script.
  
• 9) Never cheat to a torrent with 0 leechers (obviously) or even with a low amount of leechers and a high number of seeders if you are using a high upload speed. Try some client features like stopping the traffic generated when the amount of leechers is less than X (RM). This will prevent you as well from reporting upload traffic to a deleted torrent.
  
• 10) Always use the memory reader option at RM or similar on other clients to fake the most accurately possible the behaviour of a real client. It is always advisable to cheat and leave the torrent client opened in case some staff member wants to connect to you. Never cheat to a tracker while real uploading a torrent to it simultaneously for obvious reasons. You can cross cheat though (cheat at tracker A, legit upload at tracker B).
  
• 11) Each tracker its own method. Use the waffles method in waffles, use the low&steady in What.CD...etc.
  
• 12) Deactivate DHT and never publicize your passkey or a torrent downloaded from you with it in for obvious reasons.
  
• 13) When possible, try to get several accounts -at least two- to experiment methods/new clients emulated/incremental max uploads speeds... with one of them. You must be twice the cautious when browsing the site, and torrenting. It would be advisable to use different networks (wired desktop, and wifi laptop from any neighbour for example) and if possible, different ISPs, browsers and torrent clients.
  
• 14) Avoid well-known proxies/VPNs/bouncers/etc (Tor, anchorfree...). Be careful with trackers that deal with bans to international IP changes (you are torrenting from Canada and you use a proxy from Russia). Never torrent/cheat from your home and brose the site at the same time under other IP.
  
• 15) Always stay in the bandwith range from your ISP. Do not use higher uploads/downloads then the max ones available on your ISP. Several trackers deal with ISP bandwiths and know exactly the max upload/download you can be using. It's always a nice idea to state in a forum post/signature your "real" upload/download speed as an image from a speedtest direct link, never upload it to a image server as it would be suspicious to have been modified. You can always grab a fake one from speedtest, as long as it belongs to your real ISP and it's run from a location close to where you live, just run a test, click on direct link and go backwards some numbers from yours to check previous png tests (it will take >10 mins but it only needs to be done once).
  
• 16) Never use the same string that could get you identified (nick/avatar/password/mail/signature/custom title...etc) on two different trackers. As if you eventually get caught cheating in one, you are very likely to be banned from several as staff share a lot of data (especially cheaters). Obviously, avoid using the same nick on trackers and on trading/cheating forums as staff tend to lurk those type of forums.
  
• 17) Avoid browsing the tracker site/forum/chat with the same pc/browser you use for visiting sites like sb-i, moofdev, trading communities...etc. Or at least make sure you are using a cookie/history/temporaries clean browser at every time. This can be easily achieved with, for example, Firefox and its "Removing personal data on every application exit" option, using the private navigation tabs since 3.9.5, or using some HTTP blocking plugins that monitor every string sent to the site server.
  
• 18) Always use the same emulated client on your cheating application as the one you use for real torrenting. Do not use an emulated client for an OS different from the one you use for site browsing. For example, if you use Windows 7 for browsing it is not a good idea to use rTorrent (you can always say you had VMWare/VirtualPC/etc running but it would be extremely odd).
  
• 19) Always tend to use the latest client emulation version that matches your newest torrent client build. There are some trackers that force you to use the latest build available to date in order to avoid old well-known emulation clients. Never go back from a client/build version to a previous one. Some trackers do register your client history and it would be very fishy that you eventually downgrade from uTorrent 1.8.5 to, say, 1.8.4 just because you found a client that you know for sure it works on that site (always experiment with newer clients with dupe accounts).
  
• 20) COMMON SENSE.

All the above rules could be summed up in the last one. Go with the flow, don't do stupid/weird/improbable things and you will be done. You will be always smarter than a bunch of php scripts.

PD: Mods please feel free to edit my post as it may contain errors (I am an ESL student)

Have fun :)

15) Always stay in the bandwith range from your ISP. Do not use higher uploads/downloads then the max ones available on your ISP

i totally agree with all the rules but
can't resist putting high speeds in the up speed box

Originally Posted by nperversion

1) Do not start cheating the first day you got into a tracker. Stay legit for some weeks. Instead, go for freeleechs, introduce yourself to the community, post comments, open threads, participate in polls and so on. A member with an insane ratio but 0 posts, 0 comments... is always more suspicious than an integrated an active one.

I'm with slikrapid on this - I never post on tracker's forums. Every post is another place where my fake upload can be spotted. As cheaters it's better not to stand out or be community guys.

2) Never cheat as a 100% seed on a tracker-exclusive torrent impossible/hardly found outside the tracker. If you do, you must be able to legitimate you got that torrent from outside. Stay away from inner realeases unless you really downloaded them beforehand and could provide proof (be careful with showing creation/modification times on screenshots, instead they can be easily edited).

Agreed. It's very suspicious to jump as 100% done on a tracker-exclusive torrent you can't find elsewhere. The site's scripts or even staff may not detect this right away, but I prefer to look like a non-cheater.

3) For the trackers that register not only ratio but seed time you may want to cheat (or legit) upload a pack of torrents simultaneously and not cheating always only on one. 1TB uploaded on only 1 or 2 torrents, and a seed time of 1 week will just look odd. Just grab some freeleech/low size torrents and leave them uploading at 1kb/s on your real client for some weeks to build a safe seeding time.

I always aim for ratios between 1 and 3, so I'd never fake 1TB on a single torrent. My style is buffering on torrents that have a lot of leechers to look realistic, then download things that have few or none without cheating, and optionally keep on seeding them for a long time to avoid looking like a hit & runner - although some trackers, or at least SCC, allow you to H&R if your ratio is above a certain value, e.g. 1.5. Anyway, it's a lot better if you don't immediately stop the torrent after snatching it, so that at least you can do some real upload.

4) Stay away from "Top10s". You don't want to appear as one of the max uploaders, leechers, highest ratios, with max seeding time... Always try to go with the flow and never stand out.

Most of the people on Top 10s often have gigantic amounts of traffic and fast speeds, so yes. You may also end up in the Top 10 via flashing, which will show you as having GB/s speeds. Which you don't want. Again, the rule here is "don't stand out".

5) Avoid abusing the flashing method, as most of trackers run a simple max upload script which will get you banned in a blink.

I don't know what you mean with "abusing" here - either flashing TBs of upload, or flashing small amounts repeteadly?

I can agree with the former, at the time of this post no one has dedicated GB/s lines that can be maxed out in a few seconds. Some trackers don't care anyway. The latter shouldn't get you in much trouble (except maybe for the tracker hammering)

6) Don't use incremental uploads as weeks go on, as it would be fishy that first week you were uploading at ~100kb/s, next at ~150kb/s, next ~200kb/s...etc (given you are not getting caught), instead see point 13)

You could have been limiting your upload speed all this time, so this isn't that suspicious, but it's still better not to go above what your ISP can offer, just in case.

7) Never use a steady upload/download speed as a whole day uploading at 100.00 kb/s sharp is not a good idea, instead use some loosy ones (with decimals).

The Extreme Mod will only fake between the two values you set, so speeds always fluctuate. And the RM and mR have mini-randomizers to prevent you from reporting such exact speeds.

8) Try to cheat on mostly new torrents with a high amount of peers. Be careful with partial seeders as they will been shown as leechers but they won't produce any download traffic. Also try to stay within a logical range of upload given the torrent and actual peers. Make daily a quick sum of all the download speeds from leechers and upload speeds and never produce an upload higher than, say, 110% the download sum. If a torrent is reporting the tracker a 2MB/s download traffic and the summed upload rate is 3MB/s something is failing and this can be easily cross-checked with a simple script.

Checking the peerlist (if available) can help with both - just check who's stuck at a certain % with has a download speed of 0.00kB/s, and the speed ranges others are on, respectively.

9) Never cheat to a torrent with 0 leechers (obviously) or even with a low amount of leechers and a high number of seeders if you are using a high upload speed. Try some client features like stopping the traffic generated when the amount of leechers is less than X (RM). This will prevent you as well from reporting upload traffic to a deleted torrent.

If the tracker doesn't return the seeder/leecher counts in announces, you'll have to enable scraping in the RM for that function to work. The mR doesn't have that feature and never will, since The248 doesn't deem it reliable. And the Extreme Mod does have a function to stop faking when there are less than X connected peers or the peer:seed ratio is lower than X%. (Personally, I set both of those values to 0 so that it's always faking, and review whether my speeds are still realistic manually)

10) Always use the memory reader option at RM or similar on other clients to fake the most accurately possible the behaviour of a real client. It is always advisable to cheat and leave the torrent client opened in case some staff member wants to connect to you. Never cheat to a tracker while real uploading a torrent to it simultaneously for obvious reasons. You can cross cheat though (cheat at tracker A, legit upload at tracker B).

What slikrapid said - no ratio tools have peer connection code. If a staff wanted to connect to you, the connection would either time out (RM with TCP listener) or end up in nothing (RM+real client in the same port; unless you run the torrent in both, which you shouldn't).

11) Each tracker its own method. Use the waffles method in waffles, use the low&steady in What.CD...etc.

You should cheat the way you find it the best and working for you. Last year I used the slow and steady method at Waffles, and something similar to the W-M (which didn't exist at the time) on What. This year it's the opposite, since Waffles's scripts were proven not to be that "wow", while What's have advanced light years from when even the PMR worked there.

12) Deactivate DHT and never publicize your passkey or a torrent downloaded from you with it in for obvious reasons.

Not exposing your passkey is 100% correct, but the DHT myth... don't take it personally, but I get pissed off every time I read "disable DHT or else you'll report bad stats, bla bla bla"... let me quote myself:
All trackers say you disable it, and that it doesn't matter if your client respects the private flag, because with DHT/PEX you can "leak" info about torrents, "upload to other people outside of tracker X", etc.

This is FALSE. If a torrent has the private flag set to 1 (as all .torrents from ALTs do), clients won't "leak" anything about it, or upload to other people "outside" of the tracker. I really don't know why they tell you to disable both. (Anyone can of course connect and upload/download from you if they have the correct info_hash/IP/port combo. BitTorrent wasn't meant to be a secure/anonymous protocol.)

The only good reasons to disable DHT are (in my opinion):

• avoiding router/connection crashes created by the extra connections
• saving bandwidth if you're using your client to download from ALTs only

So, in short:
If you're having router crashes when running uT, disable DHT.
If you download from ALTs only, disable DHT.

If you're not having any router issues, and are also using the same uT instance to download from public trackers, keep DHT enabled.

Also, remember that despite the tracker staff being wrong regarding this, it's them that have the ability to disable accounts and not you, so if you ever send an screenshot of your uTorrent to them be it through the tracker's forum/e-mail/etc., right click "DHT: x nodes" in the status bar, and untick "Enable DHT". Re-enable it after you've taken the cap.

13) When possible, try to get several accounts -at least two- to experiment methods/new clients emulated/incremental max uploads speeds... with one of them. You must be twice the cautious when browsing the site, and torrenting. It would be advisable to use different networks (wired desktop, and wifi laptop from any neighbour for example) and if possible, different ISPs, browsers and torrent clients.

In my experiences I didn't have to go as far on trackers that care about multiple accounts (all of them care to some degree, but there's a difference betweem Demonoid and What.cd) - just don't use the same IP for both and optionally, browse them using a different browser.

14) Avoid well-known proxies/VPNs/bouncers/etc (Tor, anchorfree...). Be careful with trackers that deal with bans to international IP changes (you are torrenting from Canada and you use a proxy from Russia). Never torrent/cheat from your home and brose the site at the same time under other IP.

It's a very good idea to avoid using proxies and such in general, unless you really have to. Personally, I'd rather wait a day until my real IP changes, since a lot of trackers will ban you if you're caught using a proxy, public VPN, or any other means of hiding your real address. Most are OK with paid VPN services, but always ask, just in case.

And before someone mentions the rule of "you can use up to 5 different IPs on the same account" a lot of trackers have... you can indeed open the same account from up to five addresses, yes - but they must be from the same country. It's not possible for you, if/as account sharing is not allowed, to travel to other country and visit the tracker in a few minutes. And most of the time, the rule only applies for browsing - announcing must still be done from a single IP only.

15) Always stay in the bandwith range from your ISP. Do not use higher uploads/downloads then the max ones available on your ISP. Several trackers deal with ISP bandwiths and know exactly the max upload/download you can be using. It's always a nice idea to state in a forum post/signature your "real" upload/download speed as an image from a speedtest direct link ...

This is a good tip, although the Waffles method, for example, involves using upload speeds a lot of us don't have (1MB/s).

Also, what if you're asked to make an speedtest right now to prove you really have the speeds you say you do?

16) Never use the same string that could get you identified (nick/avatar/password/mail/signature/custom title...etc) on two different trackers. As if you eventually get caught cheating in one, you are very likely to be banned from several as staff share a lot of data (especially cheaters). Obviously, avoid using the same nick on trackers and on trading/cheating forums as staff tend to lurk those type of forums.

Different values are indeed a must. Use different usernames, password, e-mail addresses and everything else you mentioned for every tracker. Also, don't use the same IP for those that share them (What.cd, x264 and BCG, for example).

17) Avoid browsing the tracker site/forum/chat with the same pc/browser you use for visiting sites like sb-i, moofdev, trading communities...etc. Or at least ...

This shouldn't be a problem if you read the security announcement

18) Always use the same emulated client on your cheating application as the one you use for real torrenting. ...

19) Always tend to use the latest client emulation version that matches your newest torrent client build. There are some trackers that force you to use the latest build available to date in order to avoid old well-known emulation clients. Never go back from a client/build version to a previous one. ...

20) COMMON SENSE.

Agree.

I like the rules.But steady and slow on what.cd....Th ewaffles method works there fine.Or maybe you mean "Steady and slow waffles method"

Originally Posted by Mihai91

I like the rules.But steady and slow on what.cd....Th ewaffles method works there fine.

I fully trust you when you say the Waffles method works at What, but I'm scared of losing my account. I'm paranoid.

Just kiding.Actually i don't really care how you cheat there, just be safe.