- a pligg captcha
- gocr
- ImageMagick
- PHP

You’ve probably already heard about pligg, it’s a digg clone which is pretty easy to install. That means a lot of people already have it running on their domain (free backlinks with different IPs and PageRank!).

Pligg demands you enter the right captcha answer at sign up. Once you’re signed up however, you no longer need to enter captcha’s. So if you’re like me, you sign up for the sites, keep the passwords and logins in a nice list, put a small bot together and throw a couple of links to the pligg sites.

If however, you want to sign up for a lot of pligg sites and don’t want to do it manually you’ll have to crack the captcha pligg provides. Lukily the captcha is pretty easy to crack since there is enough space between all the numbers.

So we start by downloading the captcha through PHP with wget, you can fetch the captcha’s URL with fsockopen/curl on the sign-up page:

Okay so we downloaded the captcha and saved it. Now let’s perform some ImageMagick actions to clear the noise in the background. We’ll use a floodfill to find the background color and then remove it from the image.

Now we have a nice image with no background noise:

Ok so that’s looking pretty good. However we need to optimize this image a bit. First of all, for gocr to work properly we’ll need to add more space in between the numbers. We also should make the numbers bolder so gocr will recognize it better/faster.

This code is using php’s GD library to perform some operations. It will scan the image and if it finds a spot with less than 2 black pixels it means there’s a space between the 2 numbers. We put extra space between the numbers and make them bolder.

The final step is to fetch the result from gocr.

Ofcourse you first need to train gocr, you can do this by:

This will train gocr. If you feel gocr has learned enough, you can request the captcha result by doing:

$a will contain the answer, simply post that to the sign up page with fsockopen and you’re in! Massive accounts in no time.

However, if a site has XSS leaks, this does become possible. All you need is a way to inject javascript (clientscript) code onto the page. It does not even have to be saved on the site itself, simply an unfiltered echo $_GET['whatever']; will do.

Once you find this, you can steal the cookie and use it to act like the user. There are 2 options: either you use the cookie with a bot you wrote, or you mimic the user actions with javascript/ajax, since you can access javascript on the other site.

I’ll talk about sending the cookie to your bot, which will for example post a comment on a popular social network.

Let’s say the XSS hole you found is : http://www.othersite.com/input.php?txt=[whatever]
All you do is inject this piece of javascript code to attach the script to the current page:

This will send the cookie to cookiejar.php where we will catch the cookie and feed it to our bot.

Now the bot will send a comment under the user’s name. Ofcourse, this will use the same IP address for all the users you stole their cookie from. If you want to avoid this, mimic the behaviour in ajax.

It will also submit your site and keywords to SQUIRT and SQUIRT2 which is a seo tool to promote your sites. SQUIRT will submit your site to various social bookmarking sites, directories, a dedicated blog network and more… You can read more about SQUIRT here.

This tool will submit your site to (19 bookmarking sites):

• ClipClip
• Furl
• Del.icio.us
• SearchLes
• BlinkList
• Spurl
• Simpy
• ThingsIWant
• SpotBack
• Faves
• BuddyMarks
• Mister-Wong
• FyberSearch
• and some more minor bookmarking sites

It will ping your feed to pingomatic and submit it to rss aggregators.

It will generate a backlink on 55 different popular pligg websites (all different C class IPs), most with pagerank.

So on top of all the advantages that SQUIRT and the new SQUIRT2 gives you, you get additional benefits by all the extra features I added in my script.

You can use this script for $7 / url which is very cheap considering there are tons of services on digitalpoint asking a lot more for less.

Take advantage of this script now:

This will redirect to a page after payment where you can enter your URL and keywords. Enjoy the backlinks!

Multiple domains? Contact me or add a comment for a discount.

Let’s say you buy an online service somewhere through paypal. Like for example a site which will submit your article to hundreds of other websites. But you have to pay each time you submit a new article.

How can you bypass this? Well first, you’ll have to pay for 1 article just to see how the system works and verifies purchases. So what I did was input my article in the form, pay with paypal and see how my article was being published on all the other websites.

In the background I had been logging all headers and responses with Live Http Headers. After I submitted the form, I was being redirected to a file called paypal.php which saves the article and redirects to paypal. In the post redirect to paypal the owner of the site naturally sends along an ID to the saved article so that when I paid it will know what my article is.

So I paid and was redirected to a page confirming my payment (/cgi-bin/paid.pl) with the following post parameters sent from paypal to the confirmation page:

So naturally, I captured this and tried the following:

Which the paid.pl gladly accepted and started with distributing my article.

So after that I tried inputting another article in the form, get redirected to paypal. I did not pay, but instead captured the Invoice ID and changed it in the postdata in the code below.

The mistake that paid.pl made was not using the paypal API to verify if the payment was in fact completed. Instead, it simply looked at one of the parameters, presumable payment_status and just assumed the payment was completed.

So modifying parameters and then sending them to a payment verification system might sometimes work if the programmer was too lazy to use the paypal API.

Ofcourse you could use FireFox’s Tamper data as well to do this kind of stuff.

This one is for all you blackhat seo people out there trying to beat captcha’s with gocr or your own code.

The first thing you have to realise is that beating captcha’s with neaural networks is possible, but it’s very hard.
So if there’s an easier way out, then we’d all be happy to follow that route, right?

Let’s think about how a captcha system works. You create a random string, use GD or ImageMagick to put the string in an image. For the system to know if the entered code corresponds to the right string in the image, it needs to know the answer for every generated captcha.

We can assume that most captcha systems link the filename of the captcha image to the right answer in a database, like so:

Table answers
——————–

Generated image |  Answer
————————-

captcha1.jpg  | DOF93fF

captcha2.jpg  | lf3FM9

Once a person/bot enters the text in the textfield, the system will check if the input corresponds to the right answer. If the input is the same as the answer, you can pass. After that the system SHOULD remove/deactivate the row because the right answer was given to the question.

This is where a lot of systems go wrong. They keep the row in the database, they do not deactivate or remove this row. What are the consequences?

Let’s say I want to post a comment on a blog like this with php:

The headers I got by making a most through firefox and capturing them with Live HTTP Headers.
As you can see, the captcha details are included in the post parameters:

The cid is most likely the number of the row in the database, this way the system keeps track of which captcha is displayed. The capcode is the correct answer I entered, so this comment will succeed.

Since this is an example of a bad captcha system, it will ofcourse not remove/deactivate the row in the database. Which means I can trick the system into thinking I got the same captcha again (while obviously I got another captcha) and use the same answer I provided earlier. I simply change all the other post parameters but keep using the same captcha parameters:

So I changed the comment_post_ID parameter, which means I posted a comment on another page/blog, but I still kept using the same captcha answer. A lot of systems are vulnerable to this technique, I have been using this very same technique on alexa top 50 websites and they still are vulnerable after all these months.

I hope all of this makes sense. If not, please leave a comment and I’ll do my best to explain.