So you want to hack anonymously eh?
Firstly, I’m certainly not going to be held responsible for anything you do with this article, or indeed on any content you might read on my site. However, I’ve been making a little diagram to help map out how my computers on my local network talk to my gateway, which talks to my ISP provider. What if though, we borrowed next doors Wireless Network completely unsecured? Well, other than having a lot of fun we’d be breaking the computer misuse act. Hacking is a white colar crime but you still do hard time for it. So… anyway, you need some stuff:
Simple things
- Laptop (preferably, because it looks cool) ;<
- Clean HDD, all personal data removed, no personal data stays.
- Putty or other SSH Client that supports Proxy Socks.
- Friend (or not as the case may be) with a proxy.
- Wireless Network Card for laptop (or pc respectively).
Ok, so you have all the parts you need, pretty much. Lets get started and connect to the wireless network next door. You are probably now (if you haven’t already been) considerng your target, this might be on a trusted network, Open Virtual Private Network or even a LAN off one of your SSH terminals. I’ve actually put together a really sweet diagram for you guys to look at.
Why use the proxy? Well, considering we’re using Wireless which is almost and completely untraceable, you might not want to use a proxy. It could just be a fast-track way to someone getting caught… Or you might be like me.. personally I find this interesting, beating a system is interesting. Trashing it…. is not, so I used a proxy (trusted) because it protects me (or my machine(s) ) from being detected immediately.
Its Time to SSH

but first look at this little diagram, infact, its massive, click on it for fullsize !
Right here we go, your all kitted up, you’ve got a working proxy with socks4 or socks5 and your going to use it to initiate your first SSH connection from your (probably) uber windows machine. If you have used the correct IP and port, login and password (+ set right IP authentication on the proxy SERVER side), you will be able to simply enter the first SSH session IP and port details, click Open/Connect, and authorise yourself.
If your using linux you will need to type something like this:
ssh user@somehostname.com port
Once you've logged in we're ready to repeat the same, this time, jumping to another machine 1000's of miles away in the US. Remember, all of this traffic is Encrypted via RSA keys and is more difficult to monitor (or crack if your up to mischief). Lets repeat the same thing to another host.
ssh mybox.azio.org 2209
OK, so now your running accross A wireless Network of your neighbours, which in my diagram would connect to a local exchange (hop 2 for us , and hop 1 for them), the local exchange will most likely route through several booster switches (not shown in diagram), end up at a UKCORE (@ some ISP) route to the relevant datacenter/exchange and then finally meet the proxy server. Note, this hack was destined anonymous from the start, we're using wireless. However, we are paranoid tin hat wearing morons, aren't we? aren't we?! So from the proxy server through 3 Machines, the last machine terminal connecting via https (lynx in my case) and connectng to our "target" over 10,000 miles away. Boy, this lags a bit, but thats the price you will have to pay if you want to be fairly secure. Be sure not to confuse route hop's with SSH hops, not the same thing here, although the port traffic is forwarded from each machine to you, it doesn't actually count as part of your route, each machine has its "own route", that is, a return route and a send route. Your route is only to the proxy, the proxy is doing the rest of the socket connections, thats the idea. SSHD machine 1 will only connecting to the proxy and SSHD machine 2, and SSHD machine 2 will only connection to SSHD Machine 1 and SSHD Machine3.
Finally SSHD Machine 3 Will connect via lynx over https:// into another webserver (possibly rooted) running SSH Java applet (or similar completely and utter lameness), and only the webserver will "attack" the target.
Hacked!
Other possible solutions to hide yourself would obviously be deleting logs (even though this wont always work at the router level, some hardware does log IP’s), but alas, your all nice and squeaky clean anonymously Wirelessly connected in, joy to that, and probably, some free porn (eventually!).. Don’t do this at home kids, because I don’t and the Fed’s still watch the site

Click image for Bumper Size Diagram