Hacker Hacks Own Computer? > General Discussion

Posted: 4/28/2005 11:49:30 AM EDT

Hacker deletes own hard drive

You're going down, man

By Paul Hales: Wednesday 27 April 2005, 09:31

A CHAT CHANNEL spat ended when a wannabe hacker was duped into deleting his own hard drive.
The 26 year-old German claimed he was the baddest hacker in town and threatened to attack a moderator on HipHop's stophiphop.de/modules/news/article.php?storyid=184RC Channel because he thought he'd been thrown out.

He demanded the moderator cough up his IP address and prepare to be hacked.

The moderator sent back a bunch of numbers and there then followed a period in which the moderator assumes all manner of hack tools were unleashed at the IP address.

Finally the hacker declared success."I can see your E: drive disappearing, he gloated, "D: is down 45 percent!" he cried, before disappearing into the ether.

It seems he'd been hot enough to hack his own address. µ

Posted: 4/28/2005 12:01:54 PM EDT

[#1]

Now that is funny... if true.

Posted: 4/28/2005 12:02:38 PM EDT

[#2]

Sounds like one of my employees. I bet it was 192.168.0.1

Posted: 4/28/2005 12:03:35 PM EDT

[#3]

"Faygot."

Posted: 4/28/2005 12:06:31 PM EDT

[#4]

[>(]

Posted: 4/28/2005 12:10:22 PM EDT

[#5]

127.0.0.1

Posted: 4/28/2005 12:11:45 PM EDT

[#6]

I'm interested in how exactly he did that. Usually Windows would prevent one from deleting critical system files.
You could bork it up enough you next restart wouldnt be pretty though.

I'm a bit skeptical about that article.

Posted: 4/28/2005 12:16:53 PM EDT

[#7]

Then he wasn't any kind of a decent hacker. Probably just a poser.

Posted: 4/28/2005 12:20:51 PM EDT

[#8]

It was linked on slahsdot yesterday. It's an old, old chestnut.

The IP 127.0.0.1 is a universal alias for "This machine." So the wise
guy says "oh yeah? If you're so l33t, try to crack my machine.
It's at IP 127.0.0.1." The idiot pings the machine and finds that
it's up! Time to go to work. He fires up a script and runs an attack,
thus wiping out his own computer.

Posted: 4/28/2005 12:22:42 PM EDT

[#9]

Quoted:
Sounds like one of my employees. I bet it was 192.168.0.1

127.0.0.1?

Posted: 4/28/2005 2:00:51 PM EDT

[#10]

Quoted:
Quoted:
Sounds like one of my employees. I bet it was 192.168.0.1

127.0.0.1?

That is known as a Loopback address.
Every network interface using TCP/IP has it.
Kind of like a reference point for all computers to connect to
a network, or teh intarwebz.
Without it, it can't connect.

Posted: 4/28/2005 2:17:21 PM EDT

[#11]

Quoted:
Sounds like one of my employees. I bet it was 192.168.0.1

No, more likely he told the wannabe 127.0.0.01

edit: oops this window has been open for awhile and I see that many many ppl have posted since then.

Posted: 4/28/2005 2:28:03 PM EDT

[#12]

Quoted:
It was linked on slahsdot yesterday. It's an old, old chestnut.

The IP 127.0.0.1 is a universal alias for "This machine." So the wise
guy says "oh yeah? If you're so l33t, try to crack my machine.
It's at IP 127.0.0.1." The idiot pings the machine and finds that
it's up! Time to go to work. He fires up a script and runs an attack,
thus wiping out his own computer.

Yep, script kiddie

Posted: 4/28/2005 2:31:46 PM EDT

[#13]

Quoted:
Quoted:
Quoted:
Sounds like one of my employees. I bet it was 192.168.0.1

127.0.0.1?

That is known as a Loopback address.
Every network interface using TCP/IP has it.
Kind of like a reference point for all computers to connect to
a network, or teh intarwebz.
Without it, it can't connect.

Well...almost. Linux allows you to kill the loopback interface and keep the others. I don't know why you would, but you can. I just did it. I'm posting without it right now, as a matter of fact.

Note that the loopback interface is present:

[root@sleepy /]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:25:42:FD:A5
inet addr:192.168.0.102 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::211:25ff:fe42:fda5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:131788 errors:0 dropped:0 overruns:0 frame:0
TX packets:109565 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:67808234 (64.6 MiB) TX bytes:14866747 (14.1 MiB)
Base address:0x8000 Memory:c0220000-c0240000

eth1 Link encap:Ethernet HWaddr 00:0E:35:9C:A4:DE
inet addr:192.168.0.101 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::20e:35ff:fe9c:a4de/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:362551 errors:0 dropped:30 overruns:0 frame:0
TX packets:143712 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:179068470 (170.7 MiB) TX bytes:20115467 (19.1 MiB)
Interrupt:11 Base address:0x6000 Memory:c0214000-c0214fff

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2095 errors:0 dropped:0 overruns:0 frame:0
TX packets:2095 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2101102 (2.0 MiB) TX bytes:2101102 (2.0 MiB)

Now I'll shut down the interface...

[root@sleepy /]# ifdown lo
[root@sleepy /]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:25:42:FD:A5
inet addr:192.168.0.102 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::211:25ff:fe42:fda5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:131974 errors:0 dropped:0 overruns:0 frame:0
TX packets:109789 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:67865926 (64.7 MiB) TX bytes:14932948 (14.2 MiB)
Base address:0x8000 Memory:c0220000-c0240000

eth1 Link encap:Ethernet HWaddr 00:0E:35:9C:A4:DE
inet addr:192.168.0.101 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::20e:35ff:fe9c:a4de/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:362981 errors:0 dropped:30 overruns:0 frame:0
TX packets:143722 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:179266132 (170.9 MiB) TX bytes:20116166 (19.1 MiB)
Interrupt:11 Base address:0x6000 Memory:c0214000-c0214fff

Notice that it's down:

[root@sleepy /]# ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.

--- 127.0.0.1 ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 4999ms

And everything else works just fine!

[root@sleepy /]# ping google.com
PING google.com (216.239.57.99) 56(84) bytes of data.
64 bytes from 216.239.57.99: icmp_seq=0 ttl=237 time=95.4 ms
64 bytes from 216.239.57.99: icmp_seq=1 ttl=237 time=94.9 ms
64 bytes from 216.239.57.99: icmp_seq=2 ttl=237 time=95.3 ms
64 bytes from 216.239.57.99: icmp_seq=3 ttl=237 time=94.0 ms

--- google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3001ms
rtt min/avg/max/mdev = 94.050/94.944/95.438/0.550 ms, pipe 2

See? Ya learn something new everyday.

Posted: 4/28/2005 2:37:12 PM EDT

[#14]

This story screams script kiddy. Probably some guy, 26 (like story says), lost virginity to Hairy Plam and her five sisters, and still lives in Mom's basement.

Oh... and more than likely 127.0.0.1 as stated above.

Posted: 4/28/2005 2:48:12 PM EDT

[#15]

it's true though that not all germans hack, but all hackers are german. Can't stand those faaaaaags

Posted: 4/28/2005 2:54:50 PM EDT

[#16]

Quoted:
Quoted:
Quoted:
Quoted:
Sounds like one of my employees. I bet it was 192.168.0.1

127.0.0.1?

That is known as a Loopback address.
Every network interface using TCP/IP has it.
Kind of like a reference point for all computers to connect to
a network, or teh intarwebz.
Without it, it can't connect.

Well...almost. Linux allows you to kill the loopback interface and keep the others. I don't know why you would, but you can. I just did it. I'm posting without it right now, as a matter of fact.

Note that the loopback interface is present:

[root@sleepy /]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:25:42:FD:A5
inet addr:192.168.0.102 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::211:25ff:fe42:fda5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:131788 errors:0 dropped:0 overruns:0 frame:0
TX packets:109565 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:67808234 (64.6 MiB) TX bytes:14866747 (14.1 MiB)
Base address:0x8000 Memory:c0220000-c0240000

eth1 Link encap:Ethernet HWaddr 00:0E:35:9C:A4:DE
inet addr:192.168.0.101 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::20e:35ff:fe9c:a4de/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:362551 errors:0 dropped:30 overruns:0 frame:0
TX packets:143712 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:179068470 (170.7 MiB) TX bytes:20115467 (19.1 MiB)
Interrupt:11 Base address:0x6000 Memory:c0214000-c0214fff

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2095 errors:0 dropped:0 overruns:0 frame:0
TX packets:2095 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2101102 (2.0 MiB) TX bytes:2101102 (2.0 MiB)

Now I'll shut down the interface...

[root@sleepy /]# ifdown lo
[root@sleepy /]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:25:42:FD:A5
inet addr:192.168.0.102 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::211:25ff:fe42:fda5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:131974 errors:0 dropped:0 overruns:0 frame:0
TX packets:109789 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:67865926 (64.7 MiB) TX bytes:14932948 (14.2 MiB)
Base address:0x8000 Memory:c0220000-c0240000

eth1 Link encap:Ethernet HWaddr 00:0E:35:9C:A4:DE
inet addr:192.168.0.101 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::20e:35ff:fe9c:a4de/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:362981 errors:0 dropped:30 overruns:0 frame:0
TX packets:143722 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:179266132 (170.9 MiB) TX bytes:20116166 (19.1 MiB)
Interrupt:11 Base address:0x6000 Memory:c0214000-c0214fff

Notice that it's down:

[root@sleepy /]# ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.

--- 127.0.0.1 ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 4999ms

And everything else works just fine!

[root@sleepy /]# ping google.com
PING google.com (216.239.57.99) 56(84) bytes of data.
64 bytes from 216.239.57.99: icmp_seq=0 ttl=237 time=95.4 ms
64 bytes from 216.239.57.99: icmp_seq=1 ttl=237 time=94.9 ms
64 bytes from 216.239.57.99: icmp_seq=2 ttl=237 time=95.3 ms
64 bytes from 216.239.57.99: icmp_seq=3 ttl=237 time=94.0 ms

--- google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3001ms
rtt min/avg/max/mdev = 94.050/94.944/95.438/0.550 ms, pipe 2

See? Ya learn something new everyday.

Then it was an old wives tale wasn't it???

Actually I never really thought about shutting the loopback down.
Never needed to mess with it, really.

Warning

Confirm Action

[ARCHIVED THREAD] - Hacker Hacks Own Computer?

[ARCHIVED THREAD] - Hacker Hacks Own Computer?