Tag Archive for 'dead-proxies'

06
Aug

TCP 9415 Proxies

Recently, a sharp-eyed reader noted that proxies on TCP port 9415 suck ass, and suggested they might be Koobface proxies.  So this morning I did a little reality check and found:

  • They do suck ass
  • They share some aspects of last year’s Koobface spread

I did a special resurrection on every dead port 9415 proxy in the Gold Database (proxies verified at one time or another) and did some manual spot-checking.  In all, out of 5766 dead proxies I found fifteen live ones.  Most were located in China, Hong Kong, or Taiwan.  One was in Alberta, Canada.

The first one I found, in China, gave me two pages before it started resetting connections.

The Canadian proxy – apparently a Shaw Cable residential account – was fine.  It was perky and never refused a request.

However, I just now re-checked it and it’s timing out.

Several of the others simply returned the text string “error” to the browser.

Some took forever and never returned anything.

This report from Japan offers some interesting insights:

As for 9415/tcp, access from multiple sources in overseas (mainly China) observed at multiple monitoring points … has been on the rise since March.

When I look at the Big Database (all proxies scraped but not verified) I see approximately the same results just eyeballing the data, but I see the activity starting way back in August 2009.

It really takes off by the middle of May 2010.  A quick query shows that 60% of all 9415 proxies were discovered after May 15th.

In all there are over 170,000 port 9415 proxies in the database, which would make a decent botnet.

Coincidentally, Koobface “bloomed” in May of 2009.

I’ve always said this was a seasonal business.

28
Sep

My Saudi Proxy Finally Goes Dark

This morning my gold old Saudi proxy finally told me to fuck off.  What a shame!  I’ve been using it since at least January of this year.

But that’s the proxy biz for ya.

So I went to my favorite proxy list and pulled a Swedish IP off and put it into my SQUID configuration.

That worked for about 15 minutes.  It wouldn’t surprise me if that wasn’t really a Russian IP, since those proxies all tend to bump you off after a few minutes.

Then, a Polish IP.  Very fast.  Obviously NOT a hacked dsl or cable account, since the IP reverse resolved to a “real” host name.  It turned out to be a “real” Web server, shown below:

f-play

Love their hosting prices!  Everything is FREE!

So what’s up with that?  Clueless admin, playing with a staging or development site?  Or is it something more vile, like a fake hosting site?

Whatever it is, I’ve always been pleased with the performance of Polish proxies.  They’re probably #2 on my personal favorites list, right after Germany.  Still, I don’t expect it to stay up for long.

18
Sep

History Repeats Itself

It looks like last fall’s proxy drought is happening once again.

The list has been running on auto pilot for a few weeks now.  Yesterday the proxy count hit the magic number and triggered a recheck.  After the dust had settled there were only 400 or so total.  Subsequent runs, including a few Google Hack runs, have picked up very few proxies.

I haven’t been in this “business” long enough to judge the seasonal variations on the availability of proxies, and – as I recall – last year’s low point seemed to coincide with the sudden disappearance of a couple of high volume “suppliers”.  But I do remember it didn’t pick up again for several months, well after the new year.

Is this related to the start of a new school year?  Kids are hot for proxies during the school year, although they’ve been mostly using the CGI/PHP type proxies that come and go because they’re so easily banned.  Does that make open proxies (the kind we offer) all the more valuable?  Are they being sold, rather than given away, during the school year?

Whatever the reason, I still have my “stash”, and it’s bigger than last year’s.  So, I’m bumping up the list, re-testing about 30,000 dead proxies.

23
Aug

HTTP_VIA 1.0 cache-mex-popocatepetl-1

Apparently, nearly every open proxy in Mexico goes through this box.  Maybe that’s why they named it after a volcano.

Yes, I admit it.  Since yesterday I’ve been resurrecting dead proxies right and left, entertaining myself by watching the HTTP headers fly by (I am easily amused).  And going through the list I have noticed a few things.

For one, the “Proxies of 2008″ are dying off, which is to be expected.  There are only about 60 or so left.

Second, this month, August 2009, has been a great month for proxies!  Twelve full pages worth.  August has also been a great month for Mexican proxies, with most of them discovered on the 15th.  Most of them are going through the server in the title of this article.  It’s a shame I never bothered to put the VIA header in the database.  There’s a lot of good information there, lost forever.  Oh, well.

August 2008 was also a good month for proxies.  It was when we hit our first 1,000,000 boxes.  And if anyone besides me remembers back then, September 2008 was extremely dry.  Things did not pick up again until February of 2009.

Thirdly, the sites I mentioned yesterday as running “TeamViewer” all turned out to be a single IP address with 200 open ports (and probably more, since I started dropping any port less than 80 over a year ago).  And although they were running TeamViewer yesterday, all of them are open proxies today (so far, 40 out of the 200 open ports are now reporting as Transparent proxies in the list – I just haven’t hit them all yet).  Which means they’ll probably be dead tomorrow.

Here is the whois information on that particular IP:

teamviewer

Note they assigned a netname to a single IP address.  This seems unusual to me, but it could be a common practice (in fact this ISP does it a lot, if you look here and search for “SXTY”).  This probably at least partially explains the “here today, gone tomorrow” nature of Chinese proxies.  But the tie-in with “This site is running TeamViewer” is still a head-scratcher.  WTF is up with that?

I did solve my issue with the proxy judges that don’t return an Http-Referer header.  They still all return the User-Agent header, so I use that as well.  Still, I have a nagging suspicion that some proxy judges are lying to me.  I would use my own (yes, I have one of my very own design), but I have found that a lot of servers in foreign countires have difficulties resolving mrhinkydink.com.  Perhaps it may be useful as a backup of last resort for High Anon proxies (all the judges I use identify Transparent and Anonymous proxies faithfully).

Web site/false proxy detection (“Offline/WEB” in the database) is now rock solid.  I used to depend on the headers returned, but you will often get an “HTTP 200 OK” result for a login page instead of the expected (some RFC dweebs would say “correct”)  ”HTTP 403 Forbidden” result, followed by an “HTTP 302 Object Moved” to the login page.  You can’t expect Web developers to play by the rules, since they’re morons.

Other Tidbits

I keep checking the Israeli obfuscator site manually, although it has been removed from the code.  The name still resolves but the site times out and the nmap still shows port 80 as “filtered”.

I added “Cameroon’s favorite proxy list” under the page title, just for the Hell of it.

We added another 100,000 proxies to the database, hitting the 2.1 million mark this week.  And there’s more than 107,000 proxies in the “gold” table (address/ports that are or were open proxies since March 2008).

Something isn’t right with the code.  Right now there are 1140 proxies, but only 19 pages.  At fifty per page there should be 23 pages.  Come to think of it, this probably explains the missing proxies from 2008.

Unfortunately, I haven’t looked at the forum spammer’s reporting site since I started mirroring it.

Remember the Canadian hospital proxies?  They’re all gone now.  Someone figured it out and fixed it.  Good for them!

05
Aug

Forum SPAMMER Site Mirrored

I used GNU wget to mirror the forum SPAMMER’s site and ended up with about 3G of data. I’m going to mirror it every day to see if anything new pops up. After the first run it gets easier, since wget only downloads new and changed files.

As far as the proxies go, it was just as I suspected. Out of 2879 unique proxies (from 268M of log data), not including SOCKS, there was nothing but TIMEOUT and CLOSED proxies. Not one single live box. Probably 85% were already in the database, but that’s just an eyeball estimate.

There were some hints at the scams this guy is running SEO on, along with some telling graphics. It was a good education on these guys, but I’ve barely scratched the surface. I have a lot going on today and I’m going to be very busy until next week, so I’ll save my findings for later.

04
Aug

Google Hack: Not Dead Yet

No sooner do I declare the Google Hack played out, it turns me into a liar.

Shortly after my last post, I ran the Hack one more time before putting it out to pasture. A few minutes into the run, it came up with one of “those” sites. It seems to have every kind of scam on the Net (lose weight, make money from Google/Craigslist, payday loans, etc.) and some type of blackhat SEO angle. There are dozens of text files listing “users” of various online forums, the accounts they use, URLs for their profiles, and…

… the proxies they use to post.

I ran a few Google searches on some of these names and they are absolutely everywhere. There’s hardly an online forums that hasn’t been hit by these accounts so it’s definitely a forum or comment SPAM operation of some sort.

I’m not sure if this is good news or bad news. I’ve done a few runs against what they’ve got and so far it appears they don’t have anything that isn’t already in my database, although I am getting a few new TIMEOUTs and port CLOSED results. In other words, dead crap.

Anyway, there is so much stuff here that I’m going to mirror the site and bang at it at my leisure. It’s well-indexed by Google, so it’s no Big Secret, but the last time I ran across a site like this it didn’t last more than a couple of months. And the information is so… varied… that an offline study is the best way to mine it.

Check back in to see how it goes!

30
May

Chinese Proxy Purge

It seems my Russian “supplier” is overly fond of Chinese proxies lately.  Since I fixed my code yesterday that seems to be all I get out of him.

Our Russian friend may like them (who knows – he may have grown them), but I’ve never cared for them.  Back when I used to scour the lists by hand, the Chinese proxies never worked (Brazil used to have the same issue, btw).  And with all the recent news about cyberwar and the weaponization of the Internet, you just have to think twice about using anything Chinese (even though your system, a large chunk of the software you run, and your ISP’s network was probably made in China or built with Chinese parts), especially Chinese proxies from a Russin supplier.  The mind boggles.   

However, sometime this year – perhaps it has happened already – China is predicted to have the highest number of users online, so it would seem only natural for them to have the most proxies – or the most hacked systems – on the Net.

But be that as it may, old habits die hard.  I don’t like seeing all those little red flags on Page 1.

So this morning I ran a special recheck on all those allegedly active Chinese proxies.

53% were already dark.

Even with that correction, China still leads the pack in verified, non-CoDeeN proxies.

30
Jun

Check, check, re-check

At this moment, the second run of the Automatic Dead Proxy Eliminator (ADPE) is about half-way done.

ADPE is currently scheduled to run on Mondays, Wednesdays, and Fridays and its purpose is to glean dead proxies out of The List.

There were 13 pages – 630+ proxies – before it started. Now it’s down to 9 pages and 420-odd proxies. Proof positive, if you ever wondered about it in the first place, that they go fast!

Earlier, I speculated that the Bahrainian Proxy Problem might be taken care of on this run, but so far those boxes are still checking out to be up and running. I’m still curious as to what, exactly, they are, since port scans seem to imply they’re devices rather than computers.