Malware Traffic Analysis with Wireshark - 1

LetsDefend
2 Nov 202204:54

Summary

TLDRThe video script guides viewers through identifying a victim machine in a network simulation. It explains the process of analyzing IP addresses, distinguishing between private and public addresses, and using packet data to deduce the infected host. The script also covers finding the hostname of the victim machine, noting the absence of NBNS data in the provided pcap file and suggesting manual methods to retrieve it. The tutorial aims to educate on network analysis techniques for detecting malware infections.

Takeaways

  • 🔍 The speaker starts by explaining the process of identifying the IP address of a 'victim machine' in a network analysis scenario.
  • 💡 The 'Victim Machine' (VM) is the one that gets infected, and its IP address can be found by analyzing the most active conversations in the network statistics.
  • 📈 To find the VM, one should look at the statistics, specifically the 'IPv4' section, and identify the IP addresses with the highest number of packets exchanged.
  • 🌐 The distinction between private and public IP addresses is crucial; the private IP is likely the victim, as it's communicating with a public IP address.
  • đŸ€” The speaker speculates that the private IP address was in contact with a potentially malicious website, indicated by the public IP address 217.18.244.196.
  • đŸ•”ïžâ€â™‚ïž Further investigation is done by filtering for HTTP requests to identify the source of the infection, which in this case is the machine that made the request for 'mko.exe', suspected to be malware.
  • 📝 The victim's private IP address is identified as 10.12.x.x, based on its activity and the HTTP request analysis.
  • đŸ–„ïž The hostname of the Windows victim machine is not readily available in the provided pcap file, indicating a missing piece of data.
  • 🔑 The speaker mentions that to find the hostname, one would typically use the 'nbns' filter, but it's not present in this case due to the file's incompleteness.
  • 📚 In a real-world scenario, it's expected that the pcap file would contain the hostname, but for this exercise, it's marked as 'not available'.
  • đŸ› ïž The speaker also discusses the importance of understanding network protocols and the structure of pcap files for comprehensive network analysis.

Q & A

  • What is the purpose of analyzing the IP addresses in the script?

    -The purpose is to identify the victim machine in a network scenario where a machine gets infected. The analysis focuses on IP addresses with the most data transactions, indicating a likely infection point.

  • How does the script differentiate between private and public IP addresses?

    -The script identifies 10.x.x.x as a private IP address and 217.x.x.x as a public IP address. The distinction is important for understanding the network communication context.

  • What is the significance of the IP address 217.18.244.196 in the script?

    -This IP address is identified as a public IP address with which the private IP address has the most communication, suggesting it might be the source of the malware.

  • What method does the script use to find the victim host infected with malware?

    -The script uses HTTP request filtering to identify the source IP address that made a request, which in this case is suspected to have downloaded the malware.

  • What is the role of the 'statistics' and 'conversations' in identifying the victim machine?

    -These features provide insights into the network traffic and communication patterns, helping to pinpoint the machine with the most data transactions, which is likely the victim.

  • Why is the HTTP request important in the script's analysis?

    -The HTTP request shows which machine made a request for a file, in this case 'mko.exe', which is suspected to be malware, thus identifying the victim machine.

  • What is the script's approach to finding the hostname of the victim machine?

    -The script attempts to find the hostname through NBNS (NetBIOS Name Service) records, but notes that not all pcap files contain this information.

  • Why is the hostname not available in the provided pcap file?

    -The hostname is not available because the pcap file was not created with the necessary NBNS data included, possibly due to oversight or limitations in the capture.

  • What additional step is suggested to find the hostname in a complete pcap file?

    -The script suggests looking into the NBNS records, specifically the 'netbios name' and 'additional records' sections, to find the hostname of the computer.

  • How does the script conclude that 10.12.x.x is the victim's private IP address?

    -The script concludes this based on the analysis of the most data transactions and the HTTP request made to a public IP address, indicating that the private IP address is the victim.

  • What is the script's final verdict on the hostname of the victim machine?

    -The script's final verdict is that the hostname is 'not available' due to the lack of NBNS data in the pcap file provided.

Outlines

00:00

đŸ•”ïžâ€â™‚ïž Identifying the Victim Machine via IP Addresses

The speaker begins by discussing the process of identifying the victim machine in a network scenario. They mention setting up questions and providing a link in the description, which they have partially answered. The main focus is on determining the IP address of the 'Victim Machine' (VM). The speaker explains that by examining network statistics and looking at the conversations, one can identify the most active IP addresses. They highlight the importance of distinguishing between private and public IP addresses, and suggest that the private IP address (10.12.3.x) is likely the victim since it is communicating extensively with a public IP address (217.18.244.196). The speaker also describes how to use HTTP request filtering to find the victim host that was infected with malware, pointing out that the private IP address made a GET request for a file named 'mko.exe', which is suspected to be the malware.

Mindmap

Keywords

💡IP Address

An IP address is a unique numerical label assigned to each device connected to a computer network that uses the Internet Protocol for communication. In the video, the IP address is central to identifying the victim machine that gets infected. The script discusses how to find the IP address of the victim machine by analyzing network traffic and identifying the most active IP addresses involved in data transmission.

💡Victim Machine

The term 'Victim Machine' refers to the computer that has been compromised or infected, often by malware or through a security breach. The video's theme revolves around identifying this machine by analyzing network traffic and HTTP requests. The script specifically mentions a private IP address, 10.12.3.101, as the victim machine based on its activity and requests made to a public IP address.

💡Statistics

In the context of the video, 'Statistics' refers to the data collected and presented regarding network traffic and communication between devices. The script describes using the 'Statistics' feature to analyze conversations and identify the most active IP addresses, which is crucial for determining the victim machine.

💡Conversations

In network analysis, 'Conversations' represent the communication between two endpoints, such as IP addresses. The video script mentions scrolling down to the 'Conversations' section to analyze the traffic and identify the IP addresses with the most data exchange, which helps in pinpointing the victim machine.

💡Private IP Address

A private IP address is reserved for use within private networks and is not routable on the public Internet. The script explains the importance of distinguishing between private and public IP addresses, noting that the private IP address 10.12.3.101 is suspected to be the victim machine due to its high volume of data exchange with a public IP address.

💡Public IP Address

A public IP address is globally unique and routable on the Internet. The video script identifies a public IP address, 217.18.244.196, as the likely source of the malware, based on the volume of data being exchanged with the private IP address of the victim machine.

💡Packets

In networking, a 'Packet' is a unit of data sent across an inter-network, which is expected to be delivered to a destination host. The script uses the term 'packets' to describe the data being sent between the IP addresses, with a focus on those with the highest number of packets indicating active communication.

💡HTTP Request

An HTTP request is a message sent from a client to a server to request access to a resource. In the video, the script describes filtering for HTTP requests to find the victim host that was infected with malware, as it shows which source IP address made the request for the file 'mko.exe', suspected to be the malware.

💡Malware

Malware, short for malicious software, refers to any software intentionally designed to cause harm to a computer system or its users. The video's narrative involves identifying the source of malware infection by analyzing HTTP requests and the download of a file named 'mko.exe', which is implied to be the malware.

💡NBNS

NBNS, or NetBIOS over TCP/IP, is a protocol used to resolve NetBIOS names to IP addresses within a local network. The script mentions filtering for NBNS to find the hostname of the victim machine, although it notes that the specific pcap file used in the video did not include this data.

💡Hostname

A 'Hostname' is the label assigned to a device and is used to identify it on a network. The video script discusses finding the hostname of the victim machine by analyzing NBNS data, which would typically be included in a pcap file. However, the script notes that the hostname is 'not available' in the provided example due to the file's incomplete data.

Highlights

Identifying the IP address of the Windows victim machine by analyzing statistics and conversations.

Differentiating between private and public IP addresses to determine the victim machine.

Using packet analysis to find the most active IP addresses involved in data transmission.

Assuming that the private IP address with the most transactions is likely the victim.

Filtering HTTP requests to find the source IP address that requested the malware.

Identifying the victim host by analyzing the HTTP request for the malware file 'mko.exe'.

Concluding that the private IP address is the victim based on data transmission volume and HTTP request analysis.

Explaining the reasons why the private IP address is considered the victim machine.

Searching for the hostname of the Windows victim machine using NBNS filtering.

Noting the absence of NBNS data in the pcap file, requiring an alternative approach to find the hostname.

Accessing the unzipped pcap file to manually find the hostname using additional records.

Highlighting the importance of having the hostname in a real-world scenario for complete analysis.

Acknowledging the limitations of the provided pcap file in containing all necessary data for the exercise.

Providing a workaround for the missing hostname data by using the unzipped pcap file.

Demonstrating the process of manually finding the hostname in the absence of NBNS data.

Stressing the need for complete pcap files in professional settings for accurate analysis.

Concluding the hostname as 'not available' due to the limitations of the provided pcap file.

Transcripts

play00:03

these are the questions i have set up

play00:04

i'll put in the link of the description

play00:06

i already answered a little bit because

play00:08

i don't know why to be honest but

play00:11

i just i just felt like it but don't

play00:13

worry about it so let's let's click the

play00:15

x button

play00:16

all right now comes the good part let's

play00:18

start

play00:20

all right we're going to be answering

play00:21

some questions

play00:23

uh based off like what happened and

play00:25

these are the first questions we usually

play00:27

ask even in the website they usually

play00:28

post these questions so let's see

play00:31

what is the ip address of the windows

play00:34

victor machine vm stands for victim

play00:36

machine that gets infected

play00:38

so how the hell do we like start like

play00:41

this is confusing as well right

play00:43

so the first thing we can do is go to

play00:45

statistics right and go scroll down

play00:47

where you see conversations click on it

play00:50

click on so you start on ethernet click

play00:51

on ipv4

play00:53

alright we see these ip addresses over

play00:55

here

play00:56

click packets

play00:58

so the so the most amount of like data

play01:01

that is sent between computers

play01:03

are like the ones that are talking the

play01:04

most right so basically 10

play01:06

and 217 those ip addresses are talking

play01:09

the most and they're sending the most

play01:10

data that's what packets are there for

play01:12

that's the highest amount

play01:14

so for this part you got to know the

play01:15

difference between private ip address

play01:17

and public if you don't then

play01:19

yeah you're kind of you're going to

play01:20

struggle with this

play01:21

but 10 is a pub like ipaddress and 217

play01:24

is public so these two are talking like

play01:27

crazy

play01:28

so i'm guessing that someone with the

play01:30

private ip address was talking to a

play01:33

a bad website which is 217.18.244.196.

play01:38

they were making the most transactions

play01:40

so i'm going to drill down on this

play01:42

even more by going to uh

play01:44

http

play01:46

by filtering for http

play01:48

request

play01:52

yeah so this is another way to find the

play01:54

victim

play01:56

uh host that was uh infected with the

play01:58

malware

play01:59

so he's the one that requested it we see

play02:01

source right here that's the source ip

play02:03

address destination that's the

play02:04

destination so this source

play02:07

uh he made a request that's what http

play02:10

request means for this filter it means

play02:12

that we want to see who requested what

play02:14

so basically 10.12.3.101

play02:17

made a get request right here in the

play02:19

infotab he's basically saying

play02:21

uh get me this file right here mko.exe

play02:25

right that's most likely the malware

play02:28

obviously because you know i put in the

play02:29

answers so let's let's go back

play02:32

so from looking at the statistics going

play02:34

ipv4 we can conclude that the private ip

play02:37

address

play02:38

is the what you call a victim machine he

play02:41

is the victim

play02:42

so let's put that down

play02:47

10.12.

play02:52

so let's recap the reason why this guy

play02:55

is a victim is because first

play02:57

he's a private i p address and he's

play02:59

making a request to a public ip address

play03:01

and he has the most data talking between

play03:04

that ip address like see the most of the

play03:06

number of packets the second reason why

play03:08

he is the victim is because when we do

play03:10

http that request it shows that he is

play03:13

the only like

play03:15

computer that made a quest to the

play03:17

website and most likely he downloaded

play03:19

the malware

play03:20

so those are the uh reasons all right

play03:22

what is the host name of the

play03:24

windows

play03:26

victim machine that gets infected so we

play03:27

want to find the name of the computer

play03:29

what i usually do is we gotta filter

play03:31

this one out

play03:32

nbns

play03:34

see we don't see anything the reason why

play03:35

we don't see anything is because whoever

play03:37

made the pcap he didn't include that

play03:40

part of the data

play03:41

so we're gonna have to

play03:43

close and minimize this one

play03:45

go back

play03:46

and unzip the this one it's the reason

play03:48

why i wanted to unzip it because i want

play03:50

to show you what it looks like remember

play03:52

the password is infected all lowercase

play03:55

okay

play03:57

actually i go to 2014

play04:01

yeah for this i couldn't find a p cap

play04:02

that contained all the uh answer

play04:05

questions because you know it was pretty

play04:06

hard

play04:07

so

play04:08

what we do is

play04:09

we go for nbns

play04:12

and if you want to find the host name we

play04:14

go to the right you see it says right

play04:15

there that's the name but if you

play04:17

actually want to drill down scroll down

play04:18

to the second box right here

play04:21

and click netbios name minimize this

play04:23

with the arrow go to additional records

play04:27

it shows the name right here and then we

play04:28

go down it also shows the name right

play04:30

here that's how you find the hostname of

play04:31

the computer

play04:32

not all pcapp files are going to have

play04:35

the host name if you're doing it for

play04:36

practice but i'm pretty sure in a real

play04:37

business you're going to see the damn p

play04:39

cap

play04:40

with the name in it so that's the host

play04:42

name but for now i'm just saying not

play04:44

available not available because uh you

play04:46

know the guy was too lazy you know

play04:48

whoever made this crap all right

play04:51

okay

Rate This
★
★
★
★
★

5.0 / 5 (0 votes)

Étiquettes Connexes
Network AnalysisIP AddressVictim MachineHTTP RequestsMalware DetectionData PacketsPrivate IPPublic IPNetBIOS NameSecurity TutorialCybersecurity
Besoin d'un résumé en anglais ?