The Thread Killer®

Status
Not open for further replies.
Just go up to her, without saying a word, imitate the sound she makes, ask if she likes it and then sit down.
 
Sep 28 02:01:03 info.auth sshd[6892]: Failed password for root from 211.94.66.203 port 63351 ssh2
Sep 28 02:01:09 info.auth sshd[6894]: Failed password for root from 211.94.66.203 port 63665 ssh2
Sep 28 02:01:14 info.auth sshd[6896]: Failed password for root from 211.94.66.203 port 63996 ssh2
Sep 28 02:01:20 info.auth sshd[6908]: Failed password for root from 211.94.66.203 port 64338 ssh2
Sep 28 02:01:25 info.auth sshd[6910]: Failed password for root from 211.94.66.203 port 64675 ssh2
Sep 28 02:01:31 info.auth sshd[6912]: Failed password for root from 211.94.66.203 port 1089 ssh2
Sep 28 02:01:36 info.auth sshd[6914]: Failed password for root from 211.94.66.203 port 1431 ssh2
Sep 28 02:01:42 info.auth sshd[6916]: Illegal user bin from 211.94.66.203
Sep 28 02:01:42 info.auth sshd[6916]: Failed password for illegal user bin from 211.94.66.203 port 1805 ssh2
Sep 28 02:01:48 info.auth sshd[6918]: Failed password for root from 211.94.66.203 port 2184 ssh2
Sep 28 02:01:53 info.auth sshd[6920]: Failed password for root from 211.94.66.203 port 2538 ssh2
Sep 28 02:01:59 info.auth sshd[6922]: Failed password for root from 211.94.66.203 port 2869 ssh2
Sep 28 02:02:04 info.auth sshd[6924]: Failed password for root from 211.94.66.203 port 3203 ssh2
Sep 28 02:02:10 info.auth sshd[6926]: Illegal user comi from 211.94.66.203
Sep 28 02:02:10 info.auth sshd[6926]: Failed password for illegal user comi from 211.94.66.203 port 3528 ssh2
Sep 28 02:02:15 info.auth sshd[6931]: Failed password for root from 211.94.66.203 port 3867 ssh2
Sep 28 02:02:21 info.auth sshd[6940]: Failed password for root from 211.94.66.203 port 4244 ssh2
Sep 28 02:02:26 info.auth sshd[6942]: Failed password for root from 211.94.66.203 port 4619 ssh2
Sep 28 02:02:32 info.auth sshd[6944]: Failed password for root from 211.94.66.203 port 4985 ssh2
Sep 28 02:02:37 info.auth sshd[6946]: Failed password for root from 211.94.66.203 port 5436 ssh2
Sep 28 02:02:43 info.auth sshd[6948]: Failed password for root from 211.94.66.203 port 5814 ssh2
Sep 28 02:02:48 info.auth sshd[6950]: Failed password for root from 211.94.66.203 port 6240 ssh2
Sep 28 02:02:53 info.auth sshd[6952]: Failed password for root from 211.94.66.203 port 6681 ssh2
Sep 28 03:03:59 info.auth sshd[7566]: Did not receive identification string from 188.19.96.3
Sep 28 03:04:11 info.auth pam_nexg[7569]: 'root' user access denied[0001] from '188.19.96.3' on sshd

MUWAHAHAHAHA!!! You'll never get in you silly cracker! He can't even guess the port LOL
 
Sep 28 02:01:03 info.auth sshd[6892]: Failed password for root from 211.94.66.203 port 63351 ssh2
Sep 28 02:01:09 info.auth sshd[6894]: Failed password for root from 211.94.66.203 port 63665 ssh2
Sep 28 02:01:14 info.auth sshd[6896]: Failed password for root from 211.94.66.203 port 63996 ssh2
Sep 28 02:01:20 info.auth sshd[6908]: Failed password for root from 211.94.66.203 port 64338 ssh2
Sep 28 02:01:25 info.auth sshd[6910]: Failed password for root from 211.94.66.203 port 64675 ssh2
Sep 28 02:01:31 info.auth sshd[6912]: Failed password for root from 211.94.66.203 port 1089 ssh2
Sep 28 02:01:36 info.auth sshd[6914]: Failed password for root from 211.94.66.203 port 1431 ssh2
Sep 28 02:01:42 info.auth sshd[6916]: Illegal user bin from 211.94.66.203
Sep 28 02:01:42 info.auth sshd[6916]: Failed password for illegal user bin from 211.94.66.203 port 1805 ssh2
Sep 28 02:01:48 info.auth sshd[6918]: Failed password for root from 211.94.66.203 port 2184 ssh2
Sep 28 02:01:53 info.auth sshd[6920]: Failed password for root from 211.94.66.203 port 2538 ssh2
Sep 28 02:01:59 info.auth sshd[6922]: Failed password for root from 211.94.66.203 port 2869 ssh2
Sep 28 02:02:04 info.auth sshd[6924]: Failed password for root from 211.94.66.203 port 3203 ssh2
Sep 28 02:02:10 info.auth sshd[6926]: Illegal user comi from 211.94.66.203
Sep 28 02:02:10 info.auth sshd[6926]: Failed password for illegal user comi from 211.94.66.203 port 3528 ssh2
Sep 28 02:02:15 info.auth sshd[6931]: Failed password for root from 211.94.66.203 port 3867 ssh2
Sep 28 02:02:21 info.auth sshd[6940]: Failed password for root from 211.94.66.203 port 4244 ssh2
Sep 28 02:02:26 info.auth sshd[6942]: Failed password for root from 211.94.66.203 port 4619 ssh2
Sep 28 02:02:32 info.auth sshd[6944]: Failed password for root from 211.94.66.203 port 4985 ssh2
Sep 28 02:02:37 info.auth sshd[6946]: Failed password for root from 211.94.66.203 port 5436 ssh2
Sep 28 02:02:43 info.auth sshd[6948]: Failed password for root from 211.94.66.203 port 5814 ssh2
Sep 28 02:02:48 info.auth sshd[6950]: Failed password for root from 211.94.66.203 port 6240 ssh2
Sep 28 02:02:53 info.auth sshd[6952]: Failed password for root from 211.94.66.203 port 6681 ssh2
Sep 28 03:03:59 info.auth sshd[7566]: Did not receive identification string from 188.19.96.3
Sep 28 03:04:11 info.auth pam_nexg[7569]: 'root' user access denied[0001] from '188.19.96.3' on sshd

MUWAHAHAHAHA!!! You'll never get in you silly cracker! He can't even guess the port LOL

Dude is this on your Cisco router???
 
Dude is this on your Cisco router???

No, it's on a test Vforce router. Aka fishbone.

I'm doing a port scan on this guy so I can somehow try to get to the login for his machine and enter:

user: gethefuck
apssword: offmybox

:D

I love doing that hahahaha :p
 
No, it's on a test Vforce router. Aka fishbone.

I'm doing a port scan on this guy so I can somehow try to get to the login for his machine and enter:

user: gethefuck
apssword: offmybox

:D

I love doing that hahahaha :p
bwahahahahahahahahahahahahahahaahahha... What port scanner are you using?? :p

I did a tracert route and it looks like the prick is American...
 
bwahahahahahahahahahahahahahahaahahha... What port scanner are you using?? :p

I did a tracert route and it looks like the prick is American...

I'm using nmap dude.

This is what I've found so far:

Starting Nmap 5.00 ( http://nmap.org ) at 2011-04-06 14:07 SAST
NSE: Loaded 0 scripts for scanning.
Initiating Ping Scan at 14:07
Scanning 41.130.68.96 [2 ports]
Completed Ping Scan at 14:07, 5.18s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 14:07
Completed Parallel DNS resolution of 1 host. at 14:07, 0.00s elapsed
Initiating Connect Scan at 14:07
Scanning 41.130.68.96 [1000 ports]
Discovered open port 21/tcp on 41.130.68.96
Completed Connect Scan at 14:08, 56.05s elapsed (1000 total ports)
Host 41.130.68.96 is up (0.37s latency).
Interesting ports on 41.130.68.96:
Not shown: 983 closed ports
PORT STATE SERVICE
21/tcp open ftp
22/tcp filtered ssh
23/tcp filtered telnet
24/tcp filtered priv-mail
25/tcp filtered smtp
26/tcp filtered rsftp
30/tcp filtered unknown
32/tcp filtered unknown
33/tcp filtered dsp
37/tcp filtered time
42/tcp filtered nameserver
43/tcp filtered whois
49/tcp filtered tacacs
53/tcp filtered domain
70/tcp filtered gopher
79/tcp filtered finger
80/tcp filtered http

The only open port is ftp, but that's not helping :D Haha.

I don't know what port his incoming ssh connections are mapped to so I can't even ssh root@ :(
 
I'm using nmap dude.

This is what I've found so far:

Starting Nmap 5.00 ( http://nmap.org ) at 2011-04-06 14:07 SAST
NSE: Loaded 0 scripts for scanning.
Initiating Ping Scan at 14:07
Scanning 41.130.68.96 [2 ports]
Completed Ping Scan at 14:07, 5.18s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 14:07
Completed Parallel DNS resolution of 1 host. at 14:07, 0.00s elapsed
Initiating Connect Scan at 14:07
Scanning 41.130.68.96 [1000 ports]
Discovered open port 21/tcp on 41.130.68.96
Completed Connect Scan at 14:08, 56.05s elapsed (1000 total ports)
Host 41.130.68.96 is up (0.37s latency).
Interesting ports on 41.130.68.96:
Not shown: 983 closed ports
PORT STATE SERVICE
21/tcp open ftp
22/tcp filtered ssh
23/tcp filtered telnet
24/tcp filtered priv-mail
25/tcp filtered smtp
26/tcp filtered rsftp
30/tcp filtered unknown
32/tcp filtered unknown
33/tcp filtered dsp
37/tcp filtered time
42/tcp filtered nameserver
43/tcp filtered whois
49/tcp filtered tacacs
53/tcp filtered domain
70/tcp filtered gopher
79/tcp filtered finger
80/tcp filtered http

The only open port is ftp, but that's not helping :D Haha.

I don't know what port his incoming ssh connections are mapped to so I can't even ssh root@ :(

yeh whats the bet its someone playing a prank!! :p

We used to do that via BDSL lines...
 
Sup guys. Oooh, beat him at his own game and get into his box :P

That reminds me, I need to set up firewalls and a home SSH proxy for my linux box...oh, procrastination, how I hate you...tomorrow...
 
Portscanning and Network hacking... My favourite topic to talk about ANYDAY!!! :p

Haha, sorry for partying, but I'm trying to find out how to find an exploit to come in through an ftp server.. But it doesn't look like it's going to work. If you secure you're shit well enough, like say, close all the port and protect it with an access list, there really isn't shit you can do.

For example, say I put an access list on my router saying to only accept incoming connections from a certain host or IP range, you can't for a push get in.

That's why those hacking movies always piss me off. It's so unrealistic. You literally always need an inside man to give you some credentials to hack into certain devices, and from there you will be able to access others. You need inside info, otherwise you can't do shit. lol

And those networks in the movies are always so unprotected, how dumb is that! HAHA
 
Status
Not open for further replies.
Back
Top