Is your PC in 'attack' mode?

Miscellaneous Forums/General Discussion/Is your PC in 'attack' mode?

Check if your PC has been cracked/exploited and therefore being used to attack other PCs. The results from this site (which take a while to emerge) will inform you if your IP address appears in their database:

http://www.dshield.org/warning_explanation.php

I'm not on their database.

Should keep the feds of my back.

You might as well check your defences are tight as well.
Gibson Researches site will attempt to stick a few probes into your PC and see what pops out ...

Shields Up! -> https://www.grc.com/x/ne.dll?bh0bkyd2

Mine is pretty secure but fails the ping test. I happen to consider replying to pings as good practice (not to mention a requirement as per spec).

If someone wants in to my machine badly enough, they'll get in. I'm secure enough to deterr most malware and near enough all script kiddies.

hehe shields up is pretty cool:

Your Internet port 139 does not appear to exist! ...
One or more ports on this system are operating in FULL STEALTH MODE! Standard Internet behavior requires port connection attempts to be answered with a success or refusal response. Therefore, only an attempt to connect to a nonexistent computer results in no response of either kind. But YOUR computer has DELIBERATELY CHOSEN NOT TO RESPOND (that's very cool!) which represents advanced computer and port stealthing capabilities. A machine configured in this fashion is well hardened to Internet NetBIOS attack and intrusion.


well, took me only a Rename of VNBT.386 to VNBTcrap.386 in msdos mode - at least on win98.


Your system has achieved a perfect "TruStealth" rating. Not a single packet — solicited or otherwise — was received from your system as a result of our security probing tests. Your system ignored and refused to reply to repeated Pings (ICMP Echo Requests). From the standpoint of the passing probes of any hacker, this machine does not exist on the Internet. Some questionable personal security systems expose their users by attempting to "counter-probe the prober", thus revealing themselves. But your system wisely remained silent in every way. Very nice.


Finally somebody notices my genius capabilities :o)

yup same here.

(which take a while to emerge)

not for me ;)

Thats not worth much! IP's are changing all the time....

yeah.. I don't do crap and it passed me with flying colors... apparently I am very secure by dumb luck

cool, mine was PERFECT on all tests. Due to harware router/firewall no doubt.

Woo... me passed too. Although I am using this PC to try and hack into the Easter Bonus server to snare a free copy. ;)

splutter! Red Alert, I'll have to put Indiepath's igSF (indiegamer Security Forces) onto you then, be prepared! Or just buy it for a relative :-)

Oh oh... I've heard about igSF! They come round and break your kneecaps, right?!

I'll just go back to playing Xmas Bonus! :)

My PC was perfect on all tests and all I've got is the freebee zone alarm on

Sygate gave me a perfect too.

Mine had a false address posted... hmmm... now did I spoof it or was it just needing a refresh???

Glad to see my PC passes the test with flying colours, but then I'm using Linux.

Glad to see my PC passes the test with flying colours, but then I'm using Linux.

Yeah, me too at the moment. (My just over a year old SATA drive that contains windows died on me). :(

Mine had a false address posted... hmmm... now did I spoof it or was it just needing a refresh???


It would show the address that the web request came in on. If you're behind a home router/modem or hardware firewall, the site would see the IP address of the router/firewall instead of your actual PC.

If you don't have either (or see a different IP than your router has), then either you have a proxy server specified in your webbrowser, are using an 'internet accelerator' product from your ISP, or they have you behind a transparent proxy to save a little on their bandwidth cost.

You may be able to find out more by doing a reverse lookup on the IP address that gets shown.

e.g: nslookup <ipaddress> to see the name of the device associated with the IP in question.