Mvent2's Cheating Iframe detector

Home  Features  FAQ  Download  Comments
 

Welcome to the official horribly-designed homepage of mvent2's famous Cheating Iframe detector!

This project was started in the final few days of 2005. It had one aim and one aim only, to simplify the job of locating cheaters. To this day the detector still follows this goal, however many may consider this goal as already accomplished due to this program's enormous success. Here is a brief history lesson:

The paid-to industry was suffering somewhat of a depression during this period. Advertising revenue was scarce and many programs were desperate to try and make the money to remain honest to their members. Many programs did the right thing and used corporate tactics to try and increase business, however some were so desperate for cash that they turned to other methods, even if it meant biting the hand that feeds them. This was the start of a new era of cheating, the 0-Iframe.

Iframes are useful for embedding one webpage within another. Here I have embedded Google in an Iframe.  An Iframe is used by webmasters to embed a webpage into another webpage. In the example on the left, I have embedded Google into a webpage using an Iframe. Can you see why this is used for cheating now? Webmasters of many casual sites, not just program owners, are using Iframes to send illegal hits to their PTP page or search portal, all without you knowing. For you see, these tricky webmasters have made these Iframes so small you cannot possibly see them. So while your browser is busy rendering all these sites, you remain none the wiser. The only hint was an unusual amount of activity in the status bar. The most unfortunate thing was these cheaters seemed to be getting away with it because few people knew these symptoms. While there were some hard-working good samaritans who would report these cheaters, many simply were not aware of this problem. It seems as though if this were to continue, the PTR industry would kill itself.

Then, as if from nowhere, a program was made which was able to detect and manipulate 0-Iframes to the user's advantage. The creator figured how to link recently-aquired knowledge of webpage manipulation with the 0-Iframe problem. The detector was brought into the world on December 18, 2005. At that time, the 0-Iframe problem had become such a menacing epidemic that this small, young and untested program was welcomed with open arms. Improvement upon improvement, cheat report upon cheat report, the program evolved and gained universal acceptance. Not only did the cheat hunters gain the tool they've always needed, but the tool has allowed program owners and even casual members to locate cheaters, with technical knowledge no longer needed. Even thought the trend of 0-Iframe use has shown no recent signs of slowing, the cheaters are being caught within days, sometimes hours, of putting the 0-Iframe on their site. The thread where the detector was announced.

Cheaters are attempting to cover up their Iframes by encrypting the source code.  Even though the tides have turned in our favour, the anti-cheat war is far from over. Cheaters are using dirty tactics to try and escape, such as putting 0-Iframes within other 0-Iframes, encrypting the 0-Iframe code so that it becomes unreadable to a human (see left), even rigging the status bar so there appears to be no abnormal amount of activity. However, due to the special detection method, no amount of encryption no matter how advanced has stopped the detector from locating any 0-Iframes. Because of the cheaters' new sly methods, a tool like this is no longer a convenience but a necessity to locate cheaters.

We need all the help we can get. The more people we have looking for cheaters, the higher the chance that these cheaters will be caught. What can you do? Its really simple. Install the tool, then browse around like you normally do. When you come across a site which may be cheating using 0-Iframes, report them. Not only to the sites they are cheating, but also to name and shame them on GetPaidForum. Installing the tool is the hardest bit. Once that is out of the way, the rest is up to your browser, the detector, and you.

mvent2,
Cheating Iframe detector creator