I am not responsible for misuse of this information.
This article describes how computer networks can be hacked remotely using telnet. This article is part 1 of 2 on telnet hacking. It will give you the basic idea behind how this is done. If you want a more detailed description see Telnet Hacking Part 2.
Hackers always do things remotely. One of the oldest and most effecient ways is telnet If you don't know what telnet is go here.
For the purpose of making this easy to understand, lets assume the following. A hacker located at point
1 in Georgia wants to hack a computer system located in Canada (point
5). In order to reduce his/her chances of getting caught, the hacker would pick a public place in georgia to start from.
This place would be somewhere that is accessible to everyone such as a library. The hacker would then open telnet and remotely login to
a computer system (point 2) in Oregon. Next he/she will spawn a connection to another machine or network (point
3) located in Nebraska. Next, the hacker will make a huge jump and make another connection overseas to network in Poland (point
4). Finally, the hacker goes in for the kill and Connects to their target network located in Canada (point
5), and does some damage.
What Happens Next?
The SA's (systems administrators) for the network in Canada realizes the system was hacked. They trace the connection to Poland. After talking to the SA there, they realized the hacker was not even located in Poland. This is a process known as "backtracking." A good hacker will choose his/her connection points carefully to make backtracking complicated or most of the time impossible. The best connection points are often normal machines owned by home users. This is because the average home user does not keep logs of connections to their machine. If a hacker hops through several machines that have no logging system at all, the backtracking quickly comes up empty.