TryHackMe Walkthrough – Phishing Analysis Tools

Task 1: Introduction

Question 1: No answer needed

Task 2: What information should we collect?

Question 1: No answer needed

Task 3: Email header analysis

Question 1: What is the official site name of the bank that capitai-one.com tried to resemble?

This should be self-explanatory, google capitol one to see what their domain is.

Answer: capitalone.com

Continue reading TryHackMe Walkthrough – Phishing Analysis Tools

Phishing Email Example | How To Report Phishing Attempts in Gmail

I received this email this morning and I thought it would be a great example to point out the issues in the email that flag it as a phishing email.

Alright, here we have Jr. emailing us regarding an invoice. Two things off the bat, I’m not expecting anything from someone named Jr. and I have no idea what invoice I should be expecting. The last name Hade is not familiar to me. Next this attacker used Hello and Dear right after each other. This isn’t done. Then instead of using Jason to address me he uses my email address. Next looking at the attached PDF file name, which you should never open or download, the file name is just gibberish. The attacker didn’t even go to the bother of naming it “invoice” or anything that would make more sense. If we keep looking we see that their email is gibberish too and its from a gmail domain, who does legit business with a gmail address and not a real domain like bestbuy.com or something are slim.

Okay, so I know this is a phishing attempt, but what do I do with it? I could just delete it, but that doesn’t flag as something that gmail can research and prevent other users from getting this message. I could report spam, but it’s worse than just an unsolicited marketing email. This thing is malicious, so let’s see what gmail suggest.

Okay so I click on The three dots near reply and I can submit a phishing attempt.

After clicking on the message we get a pop-up that says…

And the email is removed from my inbox. We’re done. Great job and keep vigilant, Always be suspicious!

TryHackMe Walkthrough – Phishing Emails in Action

Task 1: Introduction

Question 1: No answer needed

Task 2: Cancel your PayPal order

Question 1: What phrase does the gibberish sender email start with?

This answer is in the reading. Look at the email address highlighted with a red circle 2.

Answer: noreply

Continue reading TryHackMe Walkthrough – Phishing Emails in Action

TryHackMe Walkthrough – Phishing Analysis Fundamentals

Task 1: Introduction

Question 1: No answer needed.

Task 2: The Email Address

Question 1: Email dates back to what time frame?

Answer is in the reading. Second paragraph.

Answer: 1970s

Continue reading TryHackMe Walkthrough – Phishing Analysis Fundamentals

Weekly Cybersecurity Wrap-up 11/13/23

Learn Cybersecurity with me. I’m posting my journey here.

Webinars/Videos

Articles

Podcasts

  • Cyberwire – Ep 1949 | 11.16.23 – Shopping during wartime? Focus, people.

Projects

LinkedIn Learning – CompTIA Security+ Module 8: Network Security Design and Implementation | Complete!

TryHackMe – SOC Level 1(92 % Complete): Intro to Malware Analysis

UDemy – Python for Cybersecurity – Gitlab

TryHackMe – Intro to Malware Analysis Walkthrough

In this walkthrough we will go step by step to answer the questions.

Task 1: Introduction

No questions here, so let’s keep moving.

Task 2: Malware Analysis

Question: Which team uses malware analysis to look for IOCs and hunt for malware in a network?

The answer can be found in the reading in “The purpose behind Malware Analysis” section. Specifically, the Threat Hunt bullet.

Threat Hunt teams analyze malware to identify IOCs, which they use to hunt for malware in a network.

Answer: threat hunt teams

Continue reading TryHackMe – Intro to Malware Analysis Walkthrough

Weekly Cybersecurity Wrap-up 11/06/23

Webinars

Some good youtubes this week…

Great for me as I finished up Snowden’s autobiography this week as well.

Articles

Projects

LinkedIn Learning – CompTIA Security+ Module 8: Network Security Design and Implementation | This is a long one, I’m still working on it.

TryHackMe – SOC Level 1(91 % Complete): TheHive – Complete

UDemy – Python for Cybersecurity – Gitlab

Smishing Example

What is Smishing?

Smishing, a portmanteau of “phishing” and “SMS,” the latter being the protocol used by most phone text messaging services, is a cyberattack that uses misleading text messages to deceive victims. The goal is to trick you into believing that a message has arrived from a trusted person or organization, and then convincing you to take action that gives the attacker exploitable information (like bank account login credentials, for example) or access to your mobile device.

I received this lately and I wanted to share it so you see a real-life example. I’ve blocked out the link for safety.

I did not go to this website, but you can bet they copied the look of USPS’s website along with a login page. This login page will not work for you to login, because this is a fake site. What it will do is capture you’re password and email.

So what, right? No harm done. Well here is another term to learn. Credential stuffing.

What is Credential Stuffing?

Credential stuffing is the automated injection of stolen username and password pairs (“credentials”) in to website login forms, in order to fraudulently gain access to user accounts.

Since many users will re-use the same password and username/email, when those credentials are exposed (by a database breach or phishing attack, for example) submitting those sets of stolen credentials into dozens or hundreds of other sites can allow an attacker to compromise those accounts too.

Credential Stuffing is a subset of the brute force attack category. Brute forcing will attempt to try multiple passwords against one or multiple accounts; guessing a password, in other words. Credential Stuffing typically refers to specifically using known (breached) username / password pairs against other websites.

https://owasp.org/www-community/attacks/Credential_stuffing

This is exactly what these bad guys or hackers will do. They might also sell the list that they get to other hackers. which will then in turn try the same thing. So use a password manager and don’t use the same password on more than one site. Don’t click on anything you are not expecting. If you’re unsure, contact the source directly. In this case, I am not expecting anything from USPS, and I see so many red flags on this I know it is smishing.

Those red flags are:

  • I’m not expecting it.
  • The senders address – It is not usps.gov which is what I would expect instead it is ups.gidaew24lw@usps.tw. What the heck is that?!
  • The URL didn’t make sense either. I would expect usps.gov, but it is a .com and it wasn’t usps.com either. So strange, right?

TryHackMe – TheHive Project Walkthrough

Task 1 & 2 are easy “I read this” ones, so let’s skip to…

Task 3

Question 1: Which open-source platform supports the analysis of observables within TheHive?

In the reading under “Observable Enrichment with Cortex” bullet it explains that

One of the main feature integrations TheHive supports is Cortex

Answer: Cortex

Continue reading TryHackMe – TheHive Project Walkthrough

Weekly Cybersecurity Wrap-up 10/30/23

Happy Halloween! It’s already the end of the year! Time files when you are learning cybersecurity!

Videos

What Hiring Mangers Really Think
Insider Threat

Articles

Podcasts

Cyberwire Daily – Ep 1940 | 11.2.23 – The beginning of an international consensus on AI governance may be emerging from Bletchley Park.

Projects

LinkedIn Learning – CompTIA Security+ Module 8: Network Security Design and Implementation | This is a long one, I’m still working on it.

TryHackMe – SOC Level 1(90 % Complete): Velociraptor – Complete

UDemy – Python for Cybersecurity – Gitlab