Contents

Analyzing Malicious Email - Phishing Analysis #1

Source:

InfoSec Handlers Diary Blog - SANS Internet Storm Center https://isc.sans.edu/diary/October+2021+Contest+Forensic+Challenge/27960
October 2021 Contest: Forensic Challenge, Author: Brad Duncan

Malware-Traffic-Analysis.net - 2021-10-22 - Files for an ISC diary (October 2021 Forensic Contest)
https://www.malware-traffic-analysis.net/2021/10/22/index.html

Malicious Emails can be found above ☝️☝️

2021-10-21-malicious-email-1102-UTC.eml /images2/image-39.webp /images2/image-40.webp

Email header:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
Return-Path: <karen.marshall@olympus.co.uk>
Delivered-To: macrus.cobb@enemywatch.net
Authentication-Results: mail.enemywatch.net; dkim=none; dmarc=none; spf=fail 
(mail.enemywatch.net: domain of karen.marshall@olympus.co.uk does not designate 37.0.10.22 as
permitted sender) smtp.mailfrom=karen.marshall@olympus.co.uk
Received: from olympus.co.uk (unknown [37.0.10.22])
by mail.enemywatch.net (Postfix) with ESMTP id 4HZl1q6rCqz9sVx
for <macrus.cobb@enemywatch.net>; Thu, 21 Oct 2021 11:02:34 +0000 (UTC)
From: KAREN MARSHALL
To: macrus.cobb@enemywatch.net
Subject: RE:New Order
Date: 21 Oct 2021 04:02:30 -0700
Message-ID: <20211021040230.7ED68DD78D4A19F2@olympus.co.uk>
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_NextPart_000_0012_D6D683E4.D392FCEB"

This is a multi-part message in MIME format.

The processes of analyzing phishing emails:

  1. Was the email sent from the correct SMTP server?

For instance: The person who sent the email was from: olympus.co.uk

I would pull up the MX toolbox and search: olympus.co.uk.

The IP of the olympus.co.uk (104.47.56.110) /images2/image-41.webp

Then I would compare the IP that I have in my email.

If the IP doesn’t align, that’s a sign that the email got spoofed.

In this case, IP is 37.0.10.22, which tells us that the address was spoofed. That’s a red flag. /images2/image-42.webp


2. Are the data “From” and “Return-Path / Reply-To” the same? /images2/image-43.webp

In this case, yes.


3. Look up the IP that it was sent from.

For this case, the IP was flagged as malicious in virus total. /images2/image-44.webp

Alienvault: /images2/image-45.webp /images2/image-46.webp

VirusTotal, AbuseIPDB, and AlienVault are indicating that the IP is malicious

4.  Are there any grammar mistakes? /images2/image-47.webp

The use of Co-ordinator instead of coordinator and PLS instead of “please”.

Down under the job title of Karen Marshall, I’m assuming OMEA is a company and that the adversary forgot to change it to olympus.co.uk. The story doesn’t add up.

5. Suspicious Attachments

Attachments in a legitimate email are usually alluded to within the body. The sender may say, for instance, “I am attaching the report.” This makes it easy to check the attachment because its name should correlate with what was mentioned in the message.

With a phishing email, the attachment may have nothing to do with the contents of the body of the email. It may also be unnecessary—for example, an email about a report but with an attachment containing instructions on resetting your password.

Source: Fortinet

For this email, the attachment fits the story of the body.

6. Usually, in an Isolated environment, I would download the attachment, get the hash value of the attachment, and plug the hash into an OSINT website.

In this case, MD5 hash of Order.7z is 734e991a781c52b6441526029efa8da1 https://www.virustotal.com/gui/file/c7b83c5b3ab7114127fac61933145960b3b4e580eeab2f88eb31880fa447b910 /images/image-48.webp

Hybrid Analysis:
https://www.hybrid-analysis.com/sample/5bf04dc0a6c58392ab02344da78d8cf471f522f94a845974f33dac13a1e51af2/6186eaf1c76b4005501f68d4


Second Malicious Email

2021-10-21-malicious-email-1739-UTC.eml /images2/image-49.webp

Email Header:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
Return-Path: <info@bardsirishbar.com>
Delivered-To: agnes.warren@enemywatch.net
X-NCJF-Version: 12
Authentication-Results: mail.enemywatch.net; dkim=none; dmarc=none; spf=none 
(mail.enemywatch.net: domain of info@bardsirishbar.com has no SPF policy when checking 52.168.183.87) 
smtp.mailfrom=info@bardsirishbar.com
Received: from mail.travelserver.net (mail.travelserver.net [52.168.183.87])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by mail.enemywatch.net (Postfix) with ESMTPS id 4HZvqh41vfzBrtj
for <agnes.warren@enemywatch.net>; Thu, 21 Oct 2021 17:39:23 +0000 (UTC)
Received: from localhost (135.red-2-136-209.staticip.rima-tde.net [2.136.209.135])
by mail.travelserver.net with ESMTPA
; Thu, 21 Oct 2021 17:39:11 +0000
Message-ID: <1F1E1CA5-0BA0-4B43-A68C-7B5E502B9724@mail.travelserver.net>
From: "Roger Morganheimer" <info@bardsirishbar.com>
Date: Thu, 21 Oct 2021 17:39:11 +0000
To: agnes.warren@enemywatch.net
Subject: =?UTF-8?B?UmU6IFJlOiBOZXh0IG1vbnRoJ3MgbWVldGluZw==?=
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 16.0
Content-Type: multipart/mixed; boundary=89a9d21c64b4fa2232a01489a02e26cd

The process:

  1. Was the email sent from the correct SMTP server?
  2. Are the data “From” and “Return-Path / Reply-To” the same?
  3. Look up the IP that the email was sent from.
  4. Are there any grammar mistakes?
  5. Analyze the attachments

Was the email sent from the correct SMTP server?

I tried looking up bardsirish.com, but there’s no site record. /images2/image-50.webp

Additionally, if we look at the Received Section, the email came from: mail.travelserver.net [52.168.183.87].

bardsirishbar.com is an entirely different domain than mail.travelserver.net. For me, that’s a red flag.

Are the data “From” and “Return-Path / Reply-To” the same?

From: "Roger Morganheimer" info@bardsirishbar.com

Return Path: info@bardsirishbar.com

Result: Yes

Look up the IP that the email was sent from

mail.travelserver.net [52.168.183.87]

VirusTotal:
/images2/image-51.webp /images2/image-53.webp

According to VirusTotal, the domain is clean. However, a malicious WIN32 executable has been communicating with the domain since 2019-10-06.

AbuseIPDB:
/images2/image-55.webp

AlienVault: /images2/image-56.webp

/images2/image-57.webp

Even though none of the OSINT websites flag the domain as malicious, there were executables communications to the domain, which raises suspicion.


2.136.209.135

AbuseIPDB:
/images2/image-58.webp

However, if you look up the actual domain… /images2/image-59.webp

VirusTotal:
/images2/image-61.webp /images2/image-60.webp

AlienVault: /images2/image-62.webp

Even though the domain is clean on alien vault. AbuseIPDB and VirusTotal saw the domain as malicious, and a bunch of malicious files was communicating with telefonica.com

Are there any grammar mistakes?

Nope, I don’t see any grammar mistakes.

Analyze the attachments

VirusTotal https://www.virustotal.com/gui/file/705166d5a107122554448752482515ac0a4a6aeffcdd668625db55d9f84f2af4

MD5: 8a184c701108cb94056055da8f026db7 /images2/image-63.png

According to VirusTotal, inside the .zip file is an excel spreadsheet with a malicious macro. /images2/image-64.webp

Result:

After going through the process and especially analyzing the attachment, I can surely say this email is malicious.


Third Malicious Email

/images2/image-65.webp

Was the email sent from the correct SMTP server?

There’s no mail server for enemywatch.net /images2/image-66.webp

But the email came from 198.71.247.251, which is an email server. /images2/image-67.webp

Are the data “From” and “Return-Path / Reply-To” the same?

From: Enemy Watch webmaster@enemywatch.net

Return-Path: webservices@webserver.enemywatch.net

Reply To: kweigandphotography@yahoo.ca

The data from the “FROM” field match with “Return-Path”. But the “reply-to” is entirely different, primarily the domain. Instead of  o com, it’s yahoo.ca

Look up the IP that the email was sent from

VirusTotal:
/images2/image-69.webp

AbuseIPDB:
/images2/image-70.webp

Are there any grammar mistakes?

No grammar mistakes.

Analyze the attachments

For this email, instead of having attachments in the email, there’s a link.

VirusTotal https://www.virustotal.com/gui/url/aaec52ae21b00d2d2f2feab0d0390386df16648dc1439a628266fa3dda2f6451/detection

According to VirusTotal, the URL is malicious. /images2/image-71.webp

Conclusion:

This malicious mail was well written. However, the thing that gave it away was the link.

The link redirects to stoage.googleapis.com. But if you were sharing a document with someone, why would you share a link that goes to googleapis and not google drive?

Furthermore, the “reply-to” email address was yahoo.ca instead of yahoo.com, which is a red flag. This is an example of TypoSquatting.