Rootkits is a computer security threat that is designed to modify the core software components of the system, inserting code which attempts to hide the “infection” and provides some additional feature or service to the attacker.
Some advanced trojan also has the capability to hide itself using rootkits techniques. One example is Bifrost which is able to unhook kernel mode hooks to allow bypassing more firewalls. Nowadays many security suite software such as Kaspersky Internet Security and Norton Internet Security is able to detect and defend against rootkits. If you are like me who doesn’t like to install and use bloated security suites, you can try this very small and simple yet powerful hidden process detector. It claims to detect most of rootkits technologies! DeepMonitor is an hidden process detector, for Window Xp2 only, defeating most of rootkits technologies. It can also detect some hidden injected modules techniques. Although it is very good in detecting hidden process, this tool can’t tell you if a normal running process that can be seen at Windows Task Manager is dangerous or not. Let’s take svch0st.exe for an example. By looking at the filename, it is obviously a virus or spyware because the letter O has been replaced by the number zero (0). If you run DeepMonitor, it will also show scvh0st.exe but it will not warn you because it is not a hidden process. One technique that many trojan authors will use to defeat traditional security measures is to co-opt other applications to do their dirty work. For example, an application can take control of privileged applications, such as Internet Explorer or Firefox, to carry out all of its malicious activity. This will cause all of the attacks to come from Internet Explorer or Firefox, not the actual trojan. One of the trojan that does this is Bifrost. This trojan injects code into the explorer.exe process, which then spawns a non visible Internet Explorer (iexplorer.exe) or Firefox (firefox.exe) process. The trojan then injects extra code into iexplore.exe (not as an extra dll, it just writes the malicious code directly into the memory space of iexplore.exe). This extra code then causes iexplore.exe to act as a backdoor into the computer from which an attacker has complete visibility of the file system and registry. I tried infecting my own computer with Bifrost with DeepMonitor monitoring my system. DeepMonitor detects a hidden process and shows a warning through tray balloon notification. When I launched DeepMonitor from Windows tray bar, it shows firefox.exe in red which is a hidden process. The blue ones are legitimate processes. I can double click on the process for more information or kill the process. When I check Windows Task Manager, firefox.exe also appears in the list but I wouldn’t know whether it has been tampered or not.
Download: DeepMonitor
DeepMonitor - Detect Hidden Process and Rootkit
Breaking Captcha Images
-- Breaking Captcha Images --
By Chuckie_Ice from HTS
I'll start by saying that this overview isn't for everyone. It's intended for those who have a good programming background and hopefully have worked with imaging a bit. Even if you haven't worked with images and pixel manipulation, this may be the answer to some prayers out there when people are asking themselves, "How in the world do I even start to break this thing?!?!". It is important to realize though that many times when advanced warping techniques are used it becomes almost impossible to break, all that means though is that it's -almost- impossible, not impossible ;)
So, what's the purpose of breaking a captcha image? The reasons may vary, but most of the time it's to be able to use a bot to automate some process (what captcha images are meant to prevent). For example, say in HTS, Real 1 there was a way to register at "Uncle Arnold's Local Band Review" that used a captcha image. Well we know by the challenge that we have to get the band "Raging Inferno" up to the top. In a real world situation that didn't have the same type of security flaws as the Real 1 challenge, we could register hundreds of bots that simply vote the band up to the top, and to do this we'd have to break the captcha image at registration.
Remember though, Captcha images are never universal, every different site has their own specialized captcha, so there's no simple "global" fix for all of them. With that said, however, it's easy to take code once you've written it and transfer it into another captcha breaking project.
This overview is meant to establish the groundwork so that you can break captcha images easier in the future. You can use virtually any language, however, I recommend C/C++ or C# just for speed reasons. One of these examples I've done in PHP and it works quite well, though it goes slower than most.
Now lets begin our overview of captcha breaking!
[Step 1: Analyze and Prepare]
This is more of a step that you would take after you have read this entire overview, however, I'll fill you in on it now. When starting to break a captcha, look it over, refresh it several times, and find all aspects of the captcha. Does it use different fonts? Does the background change? Is there a background image? Does the text change from bold to italics? Does the text move around on the image? Is the text a completely different color than the image? What characters/charset does it use? Is it case sensitive? These questions and more are all things you must ask yourself and analyze while looking at the different variations of the captcha image.
Now that we've got a good idea of what's what, we need to be able to start the breaking process. This just depends on what language you want to use, but make sure you have a way to open the image into your language and read all the bits into an array. Whether you do this by looping through all the pixels and putting them into an RGB array, or by using some function like LockBits or GetDIBits. This part is essential to being able to work with the image. Never try to manipulate the image using single pixel functions, like functions that get or set the color of an individual pixel. These functions usually take an extreme amount of time to perform simple tasks. The only time you'd ever use those functions is when you're reading the pixels into an array. Okay, now that you've got the general idea, on to Step 2!
[Step 2: Get rid of the crap!]
A lot of people who write captcha images like to think that they are very crafty and cunning with the garbage they put in to throw you off. Here's a big morale booster... 99% of the time it's just that, crap. You can easily write image filters to go through and wipe out the junk.
Looking for ways to get rid of garbage often times includes looking for patterns in the image. You have to really think hard about what you can and cannot use against them. For example, you come across a captcha image that has black text, but unfortunately it has an image in the background. How do we filter out the text from the image? Simple, write a filter to include only back and colors close to it (when saving in JPG, not all colors will be perfect so you have to account for some variation in color). By filtering out all pixels that aren't close to black, we're left with just the text. One way of thinking is to ask yourself, "How is it possible that I can read this? How come I can distinguish the text from the garbage and noise?". A lot of times these questions will bring you to the answer. Lets look at some examples.
Now, start by asking yourself what you notice in this image. Is it the dark text that jumps out at you? How about the light background? Both of those we can use to our advantage. Now what about those lines? For now, we'll deal with those after we get rid of the background. So we think we have an idea of how to break it... but what happens if they throw something like this at us?
The text is barely visible! Not to mention the amount of noise is cluttering up the screen. Lets think about this, how is it possible that we can read this? Simple, the text is still slightly darker than the background. So, for our filter we'll write it to turn all pixels that are darker than a certain amount to black, and all pixels that are lighter than that certain amount to white. I find that when working with captcha images, it's really nice to be able to convert them to monochrome for working with, since monochrome is just black and white. You can then use a simple 2 dimensional array for the width and height, and just use 0 and 1 for black and white. Here's our result:
Wow, now the text sure stands out! But what about that annoying background noise? Notice how it looks like there are very distinct lines going horizontally. If you look at both the original images very closely, you'll notice they aren't lines, but rows of dots! Getting rid of this is simple, all we have to do is scan the image for a pixel that's white, then a pixel that's black, then another pixel that's white again. By scanning the image for that pattern, we will be able to find and isolate the dots. Since if we look at it, it's actually both columns and rows of dots, we'll do a 2 way filter. One that looks for dots going up and down, and the other left and right. Pseudo code for left-right would look like this:
if (Pixel[x,y] == 0 && Pixel[x + 1] == 1 && Pixel[x + 2, y] == 0)
Then we have a dot in the middle! We could also do another if that flips the black with the white to scan for white dots, but we don't need to now. The same can be done for scanning up and down, just by adding 1 and 2 to the y instead of the x. The last part of our code here is to set the middle dot to white. Here's what we've got now:
Much better, we've eliminated the majority of the background and some parts of those random black lines. A big hint here now on what to do is that you can actually use the same and or close to the same filter that we just wrote above to remove these black lines. If we write something that looks for individual pixels that are not touching more than 3 other black pixels (there are 9 pixels around any single pixel that is not on the border of the image), then we can eliminate almost all of the noise.
Now that's looking really good. Unfortunately here this is the point where the above filter probably ends, since if we go any further and, lets say, try to eliminate pixels that aren't touching more than 5 or 6 black pixels, we'll start eating away too much of the text. Keeping the text close to it's original look is key for cracking captcha images. What we're going to do now is a method that I've come up with which uses Flood-Filling to eliminate random garbage. If you're going to top performance, you can always write your own FloodFill function, or you can find GD libraries that include FloodFill functions. PHP for example has the function "imagefilltoborder" which is exactly what I want. I also decided to write a performance version of this same application in C#, which I wrote my own FloodFill function. So you might ask, how are we going to use FloodFill to eliminate garbage? If we look at the image we have now, we notice that all the garbage is in really small parts, while the text is very thick and large. This gives us an advantage to breaking it, because we can simply go through every black pixel, run a FloodFill on it, count the amount of pixels that got filled, then if it's less than a certain amount... throw it out. The smaller pieces of garbage will only have a pixel count of usually 20 pixels or less, so we write our function to get rid of anything that fits our needs. You may or may not even need this step, however, if you do use it the pixel count will have to be adjusted based off of your image and how much garbage you have. After we run this new filter, our image looks like this:
Alright! Now just to let you know, depending on the captcha, not all the junk needs to be filtered out. This will also depend on the method you choose in Step 3.
[Step 3: Define our letters]
The third step is usually easier than the second. Whereas before we were just cleaning the image up, now we're going to actually define where our letters are on the image. Lucky for us, the letters are still there and pretty thick, so how should we do this? Here are our options:
Method 1: Break the letters into individual cells
OR
Method 2: Create a bounding box around our letters that will be used as a scanning area.
The advantages of the first method is that it's quick and fairly painless to break up a captcha when you have a nice thick font. It's also much faster in Step 4 (You'll see why). The disadvantage of breaking them up is when the captcha uses thin and small fonts that could get broken by the previous filters, or we could end up connecting two letters if the previous filters weren't good enough to destroy all lines between the letters.
The advantages of the second method are that it doesn't require us to do extra compensation and image checks for connected letters or broken up letters, and it allows us to easily work with small and thin fonts. The disadvantages are that it takes much more processing power, and takes a much longer time.
Lets look at the How-To: We can break the letters up in this captcha by using the same FloodFill method that we used above to eliminate noise... but instead, make it look for blocks of black that have more than 80 pixels or so (based off how thick the letters are). One thing you might ask is "Why did we have to eliminate the garbage then with that last FloodFill filter if we're just going to use it again to grab the text?" The answer is that you don't have to, since none of the small garbage which we eliminated in that last filter would have been touching the text. Now just to summarize what we're doing here, the letters get filled in by our function, then because so much of it was filled in, the program identifies that it is a character, puts it into it's own image cell, then moves on to the next ones until all 4 are in individual cells.
For our second method, we'll again use something similar to the FloodFill, however, this time we would have needed to eliminate most if not all of the garbage. We do a simple FloodFill scan to find out where the majority of the black pixels are (should be where the text is), then we find the left most, right most, upper most, and lower most borders. This should create a box around our text. It's always a good thing to expand this box a few pixels, say maybe 4 just in case one of our garbage filters took off a thin layer of the text. Now that we've got our region identified or characters into cells, onto Step 4!
[Step 4: LERN TO REED!]
The title of Step 4 may sound condescending, but for this part you actually have to make your program "read" the text. There are a few methods of doing this. The simplest is to build up a character set and scan the letters you have against the charset. Whether you do this by comparing black pixels, overall pixels, or what have you, it's your choice. The other options are to build a point profile for each letter and compare them against a pre-made set of point profiles for an the entire character set. For now, I'm going to stick with comparing the two using pixels.
If you wondered why we said Method 2 would be a lot more intensive on your computer, the simple answer is this: In order to read this captcha, you have to loop through every letter in your charset. On top of that, you'd have to loop through the entire region that we setup earlier, and lastly on top of that you'd have to do the individual scan that compares the character with the image. So there's a scan which is however man pixels the character is, then loop through every position in our region that it could possibly be, then lastly loop through every character, now you understand why it takes a long time. Method 2 works when after all the scanning is complete, the top 4 (or however many letters your captcha image is) matches are chosen and their corresponding letters are outputted as a string/text.
With Method 1, the only loop you have to do is looping through the characters in the charset, then scanning the character with the cell image to see if it's a match. Once you get the characters that match, you simply output their corresponding letters.
Unfortunately since there's no real "Imagery" done at this point, I have nothing to show you, but be assured it works very well!
[Step 5: Complications with Step 4]
This last step is only for the really hard to break captchas. Say we have letters that are rotated or distorted in some way. Rotated letters can be fixed by finding a way to "un-rotate" them. As you'll see in an example below, I "un-rotated" the letters by finding the rotation with the least width. Distorted letters are another case, since it's hard to undo a distortion. I've personally never attempted, but with some of the more simpler distortions, such as ones that use a sine wave or ones that simply stretch the text as it gets further to the end seems that it could be reversed with the right tweaks.
Now that we've established the ground rules for breaking captchas, take a look at a few more examples and see what you can think of:
The captcha from above in the process of breaking:
A captcha from Rapidshare:
http://chuckie-ice.com/CaptchaArticle/Rapidshare1.bmp
Breaking down the Rapidshare Captcha:
Our after filters and identifying the character cells:
Finally!
And lastly the compact version:
Now go back and look at the original Rapidshare captcha before it was broken, and think to yourself how you would go about breaking it. For this, I simply noticed that the background noise text was thinner than that of the main text. So I wrote a filter to thin down the walls of all the text about 8 times until it completely eliminated the background text. Once that was done, I was left with a very thin text, so I built it back up again putting 8 layers on top it, and only filling in those 8 layers where there was black on the original image. Then I separated the letters into cells, rotated them each with a 45 degree range both CW and CCW (to avoid going upside-down) and found the rotation with the minimum width. After that, I built a character set based off of the letters that were left and that was all it needed.
Lets look at some more examples and try and think what you see as a vulnerability, then read the list of what I noticed and compare:
1. Only black and white, no need to write filters to differentiate
2. Dots are easily removed
3. The text is thicker than the dots, thus it can be filtered out easily.
4. They only use numbers!
5. The text is centered in the middle, and the letters are from a monospaced font meaning that every letter will be in the same place.
*coughs*
http://www.hackthissite.org/pages/operations/createimage
What can you find wrong with this one
*coughs*
With all that said, here is our final example:
[img]http://chuckie-ice.com/CaptchaArticle/Badongo.jpg' style='border:0px' />
1. All the letters are the same color, makes it easy to pull the text from the background.
That's about the only thing this person did wrong with their captcha. The letters are spaced unevenly apart from each other, though you could call that a vulnerability because it makes it easy to distinguish which letter is which (no connecting letters). The letters are rotated, and on top of that a different font is used per letter, as well as bolding! This is an example of an extremely well made captcha image, but as well made as it is, through much programming it is still breakable.
[Step 6: From a hacking standpoint]
One last final thing about captcha images. There's always a chance that you can exploit the server along with your captcha breaking program. For example, right here on HTS they use the captcha generating script:
http://www.hackthissite.org/pages/operations/createimage.php
If you notice, this script seems to generate the same captcha text with every refresh. The only time it chooses a new set of letters is when the register page is refreshed and the session variable holding the captcha text is updated. This in itself is a vulnerability, because you could write a program to say break 5 of those, and if your program had any trouble breaking one of them, it could check against 4 others to find the best guess answer.
There is also the possibility, though slim, that you can use the session ID or captcha ID for a captcha that's already been submitted. Say for example you enter in the text for the captcha and it validates, and you notice that a session ID is attached along with the html form you just submitted. By modifying future session IDs to match that same one, there is a chance that you could trick the server into thinking that you're entering the text from the new captcha, but in fact it was a captcha that was already shown.
Cross Site Scripting (XSS)
Cross Site Scripting, or know as XSS, is the most common basic web hacking tehnique… and harmless, as many would say… but on this mather I don’t realy agree, that’s why I wrote this article.
About
XSS as I knew it is a very abstract definition for javascript injection, or at least this is what I have thought until reading RSnake’s website [speak about it a bit later]…
In fact XSS is more than javascript injection, because we can modify a page entire structure through XSS, not only create some actions…
In a small definition: XSS=javascript+html
The Call Of Javascript
Even if XSS is more than just javascript, you will have to basicaly have some javascript knowlege before you can feel the real taste of cross site scripting. For the ones who don’t know javascript I recomend them http://www.javascript.com… After learning the basics of this wonderful scripting language, you will be ready to go…
Info: did I mention that Javascript was developed by Netscape, and at the beginigs had the name LiteScript?
Posibilities
With XSS you can do “extreme” stuff.. let me explain you in a small amount of words what you can do…. the most simple thing is to redirect the curent page to one you like… an ilustrative example:
Also you could do something like poping up the cookie:
And if you know a little php you could create a page that save’s data received via get and stores them in a file/database…
Also there are more posibilities with XSS, you just need some creativity…
More XSS
I have found a website where I have learned much about XSS… there is also a little script which encodes the normal text to ASCII, hex, decimal and Base64… also the different types of attacks are shown on which browsers there are available… check out Rsnake’s page on XSS: ha.ckers.org/xss.html
How to clone GSM Sim
let's talk about the fun stuff. The first trick I will discuss is an activity that is becoming quite prevalant, SIM cloning. If you have paid attention to any cell phone related tutorials in the past, then you may remember cloning being made popular by certain public figures like Kevin Mitnick in order to place calls on the bill of another subscriber. Well, even with GSM this trick still holds relevant. How could such a flaw exist in a system that is obviously concentrated on preventing such fraudulant use? The flaw is within the COMP128 authentication algorithm used as an instantiation of A3/A8 widely used by gsm providers. Unfortunately for these providers, the COMP128 algorithm is just not strong enough to prevent fraud. We attack the algorithm by using a chosen-challenge attack, which works by forming a number of specially-chosen challenges and querying the SIM card for each one. Then by analyzing the responses from these queries, we are able to determine the value of the secret key that is used for authentication. So how do we perform this attack?
Well there are a few things you need before you start. First you will need to buy a SIM card reader, a card programmer, empty silver pic 2 card, and an unregulated adapter, and if you don't have one a 9 pin male to female extension cable. You can probably put a bid on ebay for most of this hardware, or just google up some sites that sell them. You will also need some software for this trick. First you will need a SIM card editor. An excellent piece of software to use in this instance is Cardinal Sim Editor, which you can find (including the crack for it) at the below link...
http://www.cracksweb.com/news.php?go=82
Another tool you will is CardMaster, which once again you can find at the below link...
http://cardmaster.dk/download2.php
Finally what you will need is a SIM card emulator. An excellent example of an emulator to use is SIMEMU, which you can find at the below link...
http://simemu.cjb.net/
Note for those of you who feel the need to read the instructions on the site, just go to www.freetranslation.com to translate the web page from Spanish to English. Now let's go ahead and get started shall we. You will first want to plug your SIM Reader into your com port. Then run Cardinal and then click where it says "Click Here" and then click Settings. You will then select your com/serial port and the baud rate. Then you will close this out, and then left click where it says "Click Here", go to smartcard, and click SIM editor. The program will from there start up, and you will go to SIM, then SIM Info, and click the load button. After doing this you will see the IMSI code, take note of this code as you will need it. Now close the SIM Info and go to Security/Find key KI. When this window opens just click Start and wait. It will take approximately 4 hours to find the key. Once it is found take note of this KI and exit. Now you should have the IMSI and KI noted, if so lets continue with the next step. Now take your silver card. Within the unzipped file within you will find two files. SEE50s.hex (EEPROM) and SEF50sEN.hex (PIC). Now connect your programmer to a com port and go to the setup menu on your CardMaster program and choose the appropriate com port. You should then see a yellow rectangle at the bottom of the program that says that there is no card. Now insert your smartcard into the programmer, and the rectangle should change to green and you will see "Card ready". Now go to where it says "Card type:" and select "Silvercard". NOw go to the "File to Pic:" field and upload SEF50sEN.hex, then go to the "File to Eeprom:" field and upload SEE50s.hex. Now go to Edit and click "Auto Program". Now once this is finished you will need to cut the card so that it will fit into the phone. Instructions for how the card needs to be cut is provided on the GSM solutions web site that will be listed in the Sites to Visit section at the bottom of this page. Now insert the newly cut silvercard into the phone. If it asks for
. If it asks for a pin just punch in 111. Then from the main menu open up "Sim-Emu". Now from this menu go to Set Phone #, then -GSM #1 (or any slot), then Configure, then Edit #. Now edit GSM #X to any name, and then press ok. Now go to Config.Pos. and it will ask for PIN2, which will be 1234. It will then ask you what position you want the card to be, choose Position 1. It will then ask you for the IMSI, which you will punch in the IMSI you got from Cardinal. It will then ask you for the KI, which again you punch in the KI you got from Cardinal. It will then ask you to enter your PUK which can be anything up to 8 digits. Then it will ask you to enter your PIN which can be anything up to 4 digits. There you go, now you have cloned another SIM card, and are now free to call away all you want to on someone elses bill. There have also been rumors that on certain services there are ways to clone a SIM remotely, but none have been tested so this can't be proven. So now that we're finished talking about SIM cloning, let's get into another trick involving exploiting gsm phones, bluejacking. What is bluejacking you ask? Bluejacking is exploiting the BlueTooth wireless communication system common among PDAs, cell phones, and of course laptops. In essense this is nothing more than a harmless little prank, similar to defacing web sites. For bluejacking gsm phones what we are trying to do is first create a phonebook contact that says something like "haha I haxor3d j00r ph0n3!", and then send it to any bluetooth enabled device in the facinity. This in essense amounts up to at most a harmless little prank, but it's fun to watch their faces when they get the message. However, I won't bother explaining the details of how to bluejack, since the methods are models and manufacturer dependant, and are explained on a site that will be listed at the bottom of this tutorial. Don't believe that the possibilities for exploiting bluetooth enabled gsm phones ends there though. Another activity that we can jump onto is called bluebugging.
Bluebugging is the process of sniffing out communication from a bluetooth-enabled cell phone. Like, for example, sms messages. Yup, now you can sit in a coffee shop, open up your laptop, and spy on everyone else who is using their phone. This concept was first introduced to the world in a presentation at DefCon 11, and is now available to the public in the form of a tool called BlueSniff that works as a bluetooth wardriving utility to play big brother. Go to the below address to get a copy of this tool...
http://bluesniff.shmoo.com/bluesniff-0.
Another nice tool to use for such means is btscanner, which can be used to gather as much information as possible on a bluetooth-enabled device. Yet again, this wonderful tool can be found at the below address...
http://www.pentest.co.uk/src/btscanner-
(Warning do it ur known risk)
Google - Peep into other's email Boxes
The idea is, one Google advanced search string is filetype: . It is used to find out any file only. Now I'm using this string as a tool,
I am searching for filetype:eml eml intext:"Content-Type: image/jpeg".
Look at the keyword. It is finding a file with extension eml and that eml should have a Line Content-Type: image/jpeg. Now remember the old days, MIME encoding of a email. When ever we are attaching a .jpg file, that line should come in .eml file. So, the full keyword is searching for filename any with extension .eml which is email file extension, and it should contain a .jpg file, may be some photo or other picture from the web. You can't belive if you are not checking it yourself.
Keyword : filetype:eml eml intext:"Content-Type: image/jpeg"
Here is ur example lollxxx
http://www.google.com.pk/search?hl=en&q=filetype%3Aeml+eml+intext%3A%22Content-Type%
Telnet - A Tutorial to Telnet and Hacking
Now you may be looking at this going, "What the hell is Telnet?". If you are, don't worry, I'll explain everything. First of all, Telnet is software that allows you to connect to another Telnet Host.
In windows systems Telnet is usually called Telnet32.exe or Telnet.exe. In newer versions of windows it is Telnet32.exe.
*** Note to Windows XP users: Don't go and get the old version of Telnet, because you have a DOS-Based one. I'll give commands along this guide so you can enjoy it too. You have to either run "Telnet" or "cmd" and then "Telnet".
Telnet is not illegal and is used by thousands of remote computers to interchange data, share connections, and do many other things that would be impossible without it.
The default port for Telnet is port 23. When I say for instance, 'Connect to the sys' I am referring to connecting on the system's default port for Telnet. Sometimes you can't determine a port so you will have to port scan a sys to find the Telnet Ports.
Port 25 is the 'Sendmail Protocol' port. We will be dealing with this port as well.
Telnet Security
Because there are so many problems with Telnet today involving cyber crime and hacking, SysAdmins often restrict anonymous use of their sys's Telnet Proxies. This is cheap and can be bypassed easily.
Most SysAdmins are amatures at what they do and make me laugh. They restrict the Telnet proxies on port 23 and think that we can't telnet to other ports such as 81 and 25 because we can't use the Telnet Proxy. Well they are wrong. We can easily do it and we will. Let me point out a system that has this and was not effective. I will star out the IP for privacy.
Welcome to Mcft Telnet. Telnet32.exe.
o
connecting to 202.232.**.** 23 (The port number)
Connected.
Connection to host lost (unauthorized use of Telnet Proxy(ies).
o
Connecting to 202.232.**.** 25 (Watch this..)
Welcome to ********.net Sendmail Program. Welcome to all staff.
vrfy bin
..550
vrfy sys
..550
vrfy root
..550
vrfy admin
..550
vrfy games
..550
vrfy uucp
..550
q
..550
c
Connection to host lost on command.
Ok people is there a problem there? How many addys did I get? Am I supposed to have those? Do I care? No. I am just demonstrating how bad Unix-System security is and how easy it is to use the Telnet Proxy to your advantage. Here, I wil list some commands for all of you running under DOS.
C - Close the Current Connection
D - Display the sys's operating paremeters
O - Connect to a host name (on default port 23) [port]
q - Quit (Exit Telnet).
Set- Set Options
Send - Send data/strings to server
Telnet, as you know so far, is a very useful tool for hackers. Hell, if you can't connect to a computer, you can't hack it. Its that simple.
Now the best thing about Telnet is that virtually every Windows computer has it, comes with it, and is able to run it.
THINGS GOING WRONG ON HACKING OR TELNET
I have a Windows 98 computer and I am running Telnet. It gives me a lot more options when connecting to a computer, and these commands don’t go anywhere! What do I do? I get the hostname part and all that, just what does Term-Type mean?
Ok people, so many people have asked me this I'm ready to start getting an auto-flame response on my e-mail box LoL. Anyway, here goes:
Term Type means Terminal Type. It is the version of the Telnet Terminal that the host or server is running. You have to specify this, Telnet is not hacker-friendly.
In Windows 98/95/ME you are not running a DOS-Based version of Telnet. You get a client program, somewhat considered shit for me. I like the DOS based one and frankly, I find it a lot easier to use.
I can't connect to the host!
Well, the host either doesn't exist, does not support Telnet Packets or Connections, or is currently restricting proxy access or usage from your addy or all addresses.
I went further than you because I thought I knew what I was doing! I got this message saying my hacking attempt was logged! Am I going to go to jail!?!?!
Don’t worry, as long as its not with the extension .log or .hlog or .hacklog you're fine, as 95 percent of these messages are BS and lies.
IF THEY'RE LIES, how come they knew I was hacking them?
They don't. They simply search for incoming connections not recognized by the server. If the SysAdmins didn't modify the message, you would have gotten this:
"Error 229292: Data not recognized 8191: Distinct Remote Service Lost or Corrupt."
They just modified it. Breath in, breath out, relax.
My dad or mom found out I was hacking, and my dad's an expert on computers! He made it so I can't view anything on AOL. What the hell's going on! Give me a trick to evade this!
Sure thing. Connect to AOL, ping the site you're trying to view, and type in the IP address. You will get to the homepage, but this isn't that good a trick because you can't ping sub-addys and you're going to get text for the sub-urls. This might or might now work.
I was screwing around with my friends computer. I think I left my information somewhere, but where?
Usually, you have a critical system log. If you delete a system file (which unless you're 133t you'd NEVER EVER do) the computer's going to boot and give you a log of what happened before the deletion of the file so you know what went wrong. If you did happen to delete it, it will list something like "deletion from x.x.x.x. (your IP)". If it does, damn, you're busted. But there are ways of getting rid of this "hacker-knock out". First off, get a WAN-Controller, or any sort of program that lets you input screen or Hardware input by the output. This means you can control their computer with yours. But you can't boot this computer, because it will break the connection.
Access the log files usually in system or system32 (both system files located in C:/Windows or C:/). There, you will see encrypted sh1t. CTRL+A will select it all and delete it all. If you do delete this file, (after you do), try recovering the system file. WHATEVER YOU DO DON'T DO A SYSTEM RESTORE, YOU HAVE BEEN WARNED.
Some hacker has my IP and hacks it every time I log on. It's static, which means it doesn't change. How do I make him stop? I don't know what his IP is, either!
Go to start, run, "netstat -a". Hacking is almost equivalent to connecting, if he's hacking you your connected to him and he's connected to you. Netstat -a is a command that allows you to see all your connections to hosts and servers, associated with TCP/IP. If you see a hostname that you don't recognize, log it. In fact, click Print Screen, go to paint, CTRL+V, Crop the image of the DOS window for Netstat, and save it. That should be quite easy.
170 Hacking videos
Code:
1. Installation of soks of proxy of server on vulnerable the system
http://video.antichat.net/file1.html
Code:
2. XSS- vulnerability in forums SMF 1.05
http://video.antichat.net/file2.html
Code:
3. XSS on Wapbbs. Forum vbulletin. Obtaining the password of the privileged user.
http://video.antichat.net/file3.html
Code:
4. XSS on mail Yandex.Ru
http://video.antichat.net/file4.html
Code:
5. Sql injection in cursor php_.fusion
http://video.antichat.net/file5.html
Code:
6. XSS in forums FastBB
http://video.antichat.net/file6.html
Code:
7. XSS in forums XMB
http://video.antichat.net/file7.html
Code:
8. Interception of session on server pochta.ru
http://video.antichat.net/file8.html
Code:
9. Seizure IRC of the channel
http://video.antichat.net/file9.html
Code:
10. We rock mp3 free of charge
http://video.antichat.net/file10.html
Code:
11. COSMO chat. admin it did not advance the right
http://video.antichat.net/file11.html
Code:
12. Breaking of cursor new sploytom (ZENER)
http://video.antichat.net/file12.html
Code:
13. ExBB 1.9.1. PHP-inklhding into adminke and other vulnerabilities
http://video.antichat.net/file13.html
Code:
14. zmail.ru: Sniffer and session. We read strange letters.
http://video.antichat.net/file14.html
Code:
15. Service of the virtual postcards Vcard Lite. Part of 2.
http://video.antichat.net/file15.html
Code:
16. Service of the virtual postcards Vcard Lite. Part 1.
http://video.antichat.net/file16.html
Code:
17. [ FLASH ] rues on IBM AIX
http://video.antichat.net/file17.html
Code:
18. [ FLASH ] sequential of rues ispravlenym eksploytom
http://video.antichat.net/file18.html
Code:
19. Is utilized short hyphen. We make no invisible.
http://video.antichat.net/file19.html
Code:
20. Vulnerability http://www.chatmoscow.ru
http://video.antichat.net/file20.html
Code:
21. IRC. Mockery above Slader-Non
http://video.antichat.net/file21.html
Code:
22. Vulnerabilities SetccMS (XSS)
http://video.antichat.net/file22.html
Code:
23. Installation Apache, Php, Perl, Mysql to localhost
http://video.antichat.net/file23.html
Code:
24. Php- injection in the script of news CuteNews v1.3.1
http://video.antichat.net/file24.html
Code:
25. Method of the interpretation of khesha IPB 2..x and breaking the forum
http://video.antichat.net/file25.html
Code:
26. Breaking Invision Power Board sploytom
http://video.antichat.net/file26.html
Code:
27. New vulnerability PunBB
http://video.antichat.net/file27.html
Code:
28. cuz uze google'n'yandex before askin ' stupid questions %)
http://video.antichat.net/file28.html
Code:
29. WWWThreads Bug
http://video.antichat.net/file29.html
Code:
30. Breaking phpBB 2.0.15 new sploytom
http://video.antichat.net/file30.html
Code:
31. Active XSS in LiveJournal.com
http://video.antichat.net/file31.html
Code:
32. Installation of proxy to unix the machine
http://video.antichat.net/file32.html
Code:
33. XSS in phpBB with use phpNuke
http://video.antichat.net/file33.html
Code:
34. Idea of defeysa of the site through the search demands!
http://video.antichat.net/file34.html
Code:
35. Defeys of the site through the vulnerability in PunBB (php include)
http://video.antichat.net/file35.html
Code:
36. Breaking OF LARGE BROTHER - tntbrat.ru. SQL - injection.
http://video.antichat.net/file36.html
Code:
37. Breaking hack-info.net through PHP injection and GIF the file
http://video.antichat.net/file37.html
Code:
38. Breaking of the mailbox through the holes on the server
http://video.antichat.net/file38.html
Code:
39. SQL- Eng. in IPB 1. *, 2. *. Obtaining khesha of admina
http://video.antichat.net/file39.html
Code:
40. History of the breaking of one site
http://video.antichat.net/file40.html
Code:
41. XSS in MercuryBoard. New.
http://video.antichat.net/file41.html
Code:
42. Vulnerability IkonBoard. Reading it is file
http://video.antichat.net/file42.html
Code:
43. Error of khostera in tuning of system.
http://video.antichat.net/file43.html
Code:
44. Obtaining administrative privelegiy in paBugs
http://video.antichat.net/file44.html
Code:
45. Vulnerability phpBB in module downloads.php
http://video.antichat.net/file45.html
Code:
46. XSS in many search with- swing. It is in detail.
http://video.antichat.net/file46.html
Code:
47. Breaking phpBB new sploytom
http://video.antichat.net/file47.html
Code:
48. XSS in PunBB 1..x
http://video.antichat.net/file48.html
Code:
49. XSS in MercuryBoard 1..x
http://video.antichat.net/file49.html
Code:
50. Vulnerability in SR Guestbook
http://video.antichat.net/file50.html
Code:
51. Breaking of box on e-mail.ru (part of 2)
http://video.antichat.net/file51.html
Code:
52. Breaking of box on nm.ru (part 1)
http://video.antichat.net/file52.html
Code:
53. Seizure of the site through the injection in Zorum
http://video.antichat.net/file53.html
Code:
54. SQL injection in forums Minibb 1.6
http://video.antichat.net/file54.html
Code:
55. XSS in forums phorum
http://video.antichat.net/file55.html
Code:
56. XSS in forums He11.net and LedForums
http://video.antichat.net/file56.html
Code:
57. XSS in vBulletin 2..kh.kh
http://video.antichat.net/file57.html
Code:
58. XSS in forums zorum
http://video.antichat.net/file58.html
Code:
59. Bases of work with John The Ripper
http://video.antichat.net/file59.html
Code:
60. Analysis vzlomanoy BD
http://video.antichat.net/file60.html
Code:
61. Registration KeySpy Generator
http://video.antichat.net/file61.html
Code:
62. Vulnerability in phpBB 2.0.12 (KEZ)
http://video.antichat.net/file62.html
Code:
63. Vulnerability in phpBB 2.0.12 (max_.pain89)
http://video.antichat.net/file63.html
Code:
64. We obtain seriynik for progi through ArtMoney
http://video.antichat.net/file64.html
Code:
65. We read strange letters on mail.ru through the sessions
http://video.antichat.net/file65.html
Code:
66. SQL injection in LedForums
http://video.antichat.net/file66.html
Code:
67. Example Post- Flood through DenyoLaunch III
http://video.antichat.net/file67.html
Code:
68. SQL injection in search.php in phpBB 2.0.6
http://video.antichat.net/file68.html
Code:
69. SQL injection in MercuryBoard 1.1.0
http://video.antichat.net/file69.html
Code:
70. Study of protection WinRAR 3..0b =)
http://video.antichat.net/file70.html
Code:
71. Second method of the theft of nikov in the chat room
http://video.antichat.net/file71.html
Code:
72. CHAT ROOM. Seizure of nikov.
http://video.antichat.net/file72.html
Code:
73. Presence s/n for WinZIP 8..0b
http://video.antichat.net/file73.html
Code:
74. We make patch for BlueFace (CodeFusion)
http://video.antichat.net/file74.html
Code:
75. We make patch for WinZIP 8..0b (CodeFusion)
http://video.antichat.net/file75.html
Code:
76. We penetrate in strange comp. through Remote Administrator
http://video.antichat.net/file76.html
Code:
77. Pincha no longer catches the antivirus
http://video.antichat.net/file77.html
Code:
78. Survey of bagov in cgi scripts.
http://video.antichat.net/file78.html
Code:
79. Idea of brutoforsa amperesecond through HTTP demands.
http://video.antichat.net/file79.html
Code:
80. As to drive away as'ku. One of the methods.
http://video.antichat.net/file80.html
Code:
81. By vlom with the aid of rAdmin Of brutforsera!
http://video.antichat.net/file81.html
Code:
82. one additional method to skachat' paid mp3 c of site mp3search.ru.
http://video.antichat.net/file82.html
Code:
83. Defeys on the rapid. Bagi on the server. Admin did not advance right on the folders.
http://video.antichat.net/file83.html
Code:
84. Vulnerability of site on cursor runcms
http://video.antichat.net/file84.html
Code:
85. Story about troyane pinch 1.0
http://video.antichat.net/file85.html
Code:
86. The new vulnerability Mybb. XSS works in all browsers.
http://video.antichat.net/file86.html
Code:
87. Breaking IcrediBB (SQL-injection)
http://video.antichat.net/file87.html
Code:
88. Baga in the the guest MPM Guesbook Pro
http://video.antichat.net/file88.html
Code:
89. As to rock mp3 for free from site mp3search.ru
http://video.antichat.net/file89.html
Code:
90. Sql-injection on cursor Php-Nuke
http://video.antichat.net/file90.html
Code:
91. SQL-injection in forum Zorum
http://video.antichat.net/file91.html
Code:
92. XSS and SQL-injection MyBB the forum
http://video.antichat.net/file92.html
Code:
93. Seizure Flesch chat room (part of 2)
http://video.antichat.net/file93.html
Code:
94. Seizure Flesch chat room (part 1)
http://video.antichat.net/file94.html
Code:
95. XSS in the forums in sparenykh BB tags VBulletin 3.0. *
http://video.antichat.net/file95.html
Code:
96. As to become adminom of forum ITA V1.49.
http://video.antichat.net/file96.html
Code:
97. Vulnerabilities in Zeroboard.
http://video.antichat.net/file97.html
Code:
98. Video about the the new XSS in the forums in sparenykh BB the tags
http://video.antichat.net/file98.html
Code:
99. UNION in SQL demands. Example of work.
http://video.antichat.net/file99.html
Code:
100. Vozmozhye vulnerabilities in scripts Manlix.
http://video.antichat.net/file100.html
Code:
101. As to become adminom on the site made in Flat-nuke.
http://video.antichat.net/file101.html
Code:
102. Error of adminov with installation Guestbook v1.1. Defeys on the rapid.
http://video.antichat.net/file102.html
Code:
103. Defeys for the small. Defeys on the rapid.
http://video.antichat.net/file103.html
Code:
104. Again PHPBB. if the provider of dull.
http://video.antichat.net/file104.html
Code:
105. XSS vulnerability in forum forum.antichat.ru (vbulletin 3.0.3)
http://video.antichat.net/file105.html
Code:
106. To the article about mail.ru. We steal Cooks in the chat room. More detailed video.
http://video.antichat.net/file106.html
Code:
107. To the article about mail.ru. We steal Cooks in the chat room. We become moderators chat.mail.ru.
http://video.antichat.net/file107.html
Code:
108. php inklyuding KorWeblog
http://video.antichat.net/file108.html
Code:
109. Breaking e-mail'ov 2. Sorting of passwords. Is utilized Brutus (under Windows).
http://video.antichat.net/file109.html
Code:
110. Breaking e-mail'ov. Is utilized THC - Hydra.
http://video.antichat.net/file110.html
Code:
111. Vulnerability Ultimate PHP Board (UPB) v1.9
http://video.antichat.net/file111.html
Code:
112. Forum Russian Board Or as it is not necessary to write authorization system. (found Max_.pain)
http://video.antichat.net/file112.html
Code:
113. As to obtain strange letters on ramblere
http://video.antichat.net/file113.html
Code:
114. LiteForum 2 (SQL-injection)
http://video.antichat.net/file114.html
Code:
115. We look passwords on forum Powered by Web Wiz Forums.
http://video.antichat.net/file115.html
Code:
116. Overcrowding of buffer. Theory.
http://video.antichat.net/file116.html
Code:
117. We steal UIN, having a base of the users
http://video.antichat.net/file117.html
Code:
118. As to steal the Internet on 445 port
http://video.antichat.net/file118.html
Code:
119. Baga ConfYmi 2.1
http://video.antichat.net/file119.html
Code:
120. We obtain root, I use sploita.
http://video.antichat.net/file120.html
Code:
121. Practitioner Flood
http://video.antichat.net/file121.html
Code:
122. VIDEO SQL Injection IPB 2.0. *
http://video.antichat.net/file122.html
Code:
123. Bagi of white resist- site mag.su
http://video.antichat.net/file123.html
Code:
124. Real breaking PHPBB
http://video.antichat.net/file124.html
Code:
125. SQL injection in forum IbProArcade
http://video.antichat.net/file125.html
Code:
126. Breaking PHPBB
http://video.antichat.net/file126.html
Code:
127. Fraud Online of games.
http://video.antichat.net/file127.html
Code:
128. Breaking of forum MiniBB
http://video.antichat.net/file128.html
Code:
129. SQL injection in the forum * He11.net Forums v1.0 *
http://video.antichat.net/file129.html
Code:
130. Seizure of the site through through cosmo-chat. Continuation...
http://video.antichat.net/file130.html
Code:
131. XSS in forum ExBB 1.9.1 THE II rocking shell- A
http://video.antichat.net/file131.html
Code:
132. XSS in forum ExBB 1.9.1
http://video.antichat.net/file132.html
Code:
133. SQL-injection in forum phpBB 2.0.6
http://video.antichat.net/file133.html
Code:
134. XSS in forum Web Wiz Forums v7.7 on securitylab.ru
http://video.antichat.net/file134.html
Code:
135. SQL-injection in the popular forum UBB threads 6.2.3
http://video.antichat.net/file135.html
Code:
136. Fulfillment shell- commands through curved perl- script (sendmail)
http://video.antichat.net/file136.html
Code:
137. We obtain seriynik for progi (php-injection)
http://video.antichat.net/file137.html
Code:
138. XSS in the chat room on kc-camapa.ru
http://video.antichat.net/file138.html
Code:
139. Breaking of the site through cgi- error: paypy
http://video.antichat.net/file139.html
Code:
140. Seizure of the site through cosmo-chat
http://video.antichat.net/file140.html
Code:
141. We drive away paid script free of charge (ezUpload pro 2.2)
http://video.antichat.net/file141.html
Code:
142. Yuzayem random cgi-telnet =)
http://video.antichat.net/file142.html
Code:
143. XSS in the chat room on muz-tv.ru
http://video.antichat.net/file143.html
Code:
144. Breaking of the site through cgi- error: of the byte
http://video.antichat.net/file144.html
Code:
145. Breaking of the site through php-injection and knowledge SQL
http://video.antichat.net/file145.html
Code:
146. We penetrate adminku of the news script Absolute Engine
http://video.antichat.net/file146.html
Code:
147. Breaking of site on cursor shad0wed portal 5
http://video.antichat.net/file147.html
Code:
148. Difeys through the injection in Advanced Guestbook 2.2
http://video.antichat.net/file148.html
Code:
149. Breaking of the school site through the vulnerability on home page of teacher.
http://video.antichat.net/file149.html
Code:
150. Breaking of the site through standard PHP- injection.
http://video.antichat.net/file150.html
Code:
151. Obtaining root rights on server yargsm.ru
http://video.antichat.net/file151.html
Code:
152. 6 video recordings about the recent attack on the living periodical.
http://video.antichat.net/file152.html
Code:
153. The fulfillment of the arbitrary code in Mcft Windows with working WMF it is file.
http://video.antichat.net/file153.html
Code:
154. Demonstartsiya of the filling of shela to forums IPB of version 2.0.4 when the password of administrator is present.
http://video.antichat.net/file154.html
Code:
155. Breaking of program XoftSpy.
http://video.antichat.net/file155.html
Code:
156. Vparivaniye of troyana. Operation of vulnerability "not complete way to the processor" Windows (total) commander.
http://video.antichat.net/file156.html
Code:
157. Obtaining adminki and the filling of shela in cursor e107
http://video.antichat.net/file157.html
Code:
158. Installation IRC of boat under Windows.
http://video.antichat.net/file158.html
Code:
159. Registration of program Advanced Security Level.
http://video.antichat.net/file159.html
Code:
160. interesnya idea about how it is possible to flood Shell to forums phpBB of any versions, if there is access to the administratorskoy panel.
http://video.antichat.net/file160.html
Code:
161. Breaking of paid hosting- provider with the use of old vulnerability in phpBB on one of the sites of hosting and the curvedly disposed server under control FreeBSD.
http://video.antichat.net/file161.html
Code:
162. "Admin Password Exploit" (author)
http://video.antichat.net/file162.html
Code:
163. Breaking e107 with use ImageManager/manager.php - the built-in file is manager.
XSS is not used!
http://video.antichat.net/file163.html
Code:
164. Khalyavnyy Internet in the local network.
http://video.antichat.net/file164.html
Code:
165. Seizure of the IRK- boat, which repeats phrases =)
http://video.antichat.net/file165.html
Code:
166. Video about the breaking of server under control Windows 3.1
http://video.antichat.net/file166.html
Code:
167. Theft of the 6- marking icq through that attached to it e-mail.
http://video.antichat.net/file167.html
Code:
168. Use wwwhack based on example vBulletin.
http://video.antichat.net/file168.html
Code:
169. One additional hole in cursor e107.
http://video.antichat.net/file169.html
Code:
170. Theft it is no in the chat room through breaking e-mail'a (by brutoforsom).
http://video.antichat.net/file170.html
