Skip to content

shankarsharma507/Post-Attack-Network-Session-Analysis-of-PCAP-Files-using-Wiresahrk

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

9 Commits
Β 
Β 
Β 
Β 

Repository files navigation

Post-Attack Network Session Analysis of PCAP Files using Wireshark

πŸ“ Project Overview

This project focuses on performing network forensic analysis on a captured .pcap file using Wireshark. It simulates a post-attack investigation in a Windows Active Directory environment to uncover attacker behavior and extract key Indicators of Compromise (IoCs).

🎯 Objective

To analyze malicious network traffic after a simulated cyber attack using NeSA and Wireshark, identify the infected client, and understand attacker activity.

πŸ§ͺ Dataset Details

  • PCAP Source: Malware-Traffic-Analysis.net
  • Exercise Name: 2025-06-13 - IT'S A TRAP!
  • LAN Subnet: 10.6.13.0/24
  • AD Domain: massfriction.com
  • Capture Duration: ~34 minutes (21:03:55 to 21:38:23)
  • Total Packets: 48,877
  • Total Sessions: 212

πŸ› οΈ Tools Used

  • NeSA (Network Session Analyser by CDAC)
  • Wireshark
  • Threat Intel Portals (VirusTotal, AbuseIPDB)

πŸ” What Was Analyzed

  • Basic traffic statistics (packets, sessions, top talkers, protocol distribution)
  • Identification of infected Windows client:
    • IP address
    • MAC address
    • Hostname
    • User account
  • Detection of:
    • Suspicious DNS & HTTP requests
    • Malicious domains & IPs
    • Encrypted Command-and-Control (C2) communication
    • Signs of data exfiltration
  • Attack timeline reconstruction

πŸ“Š Key Findings

Forensic Element Value
Infected IP 10.6.13.133
MAC Address 24:77:03:ac:97:df
Hostname DESKTOP-5AVE44C
Username gaines
Malicious Domains hillcoweb.com, windows-msgas.com, event-datamicrosoft.live, varying-rentals-calgary-predict.trycloudflare.com
External IPs 67.217.228.199, 83.137.149.15, 205.174.24.80, 104.21.112.1, 104.21.80.1, 104.21.16.1
Protocols Used TLS/443 (C2), HTTP/80 (fake Microsoft C2, exfiltration), SMB, Kerberos, DNS

βœ… Forensics Checklist Followed

  • Basic information extraction
  • Session and protocol analysis
  • HTTP and DNS traffic inspection
  • Malicious session identification
  • Timeline building
  • IOC extraction and reporting
  • Answered specific forensic questions (infected IP, MAC, hostname, user)

πŸ“ Report Structure

The complete analysis is documented in the report with:

  • Timeline of attack
  • Session tables and findings
  • Indicators of Compromise (IoCs)
  • Screenshots of NeSA and Wireshark output
  • Key recommendations

πŸ‘€ Author

Shankar Sharma
Cyber Forensics & Security | CDAC Project | 2025

πŸ“˜ Disclaimer

This project is for educational and research purposes only. The PCAP file is sourced from public malware training data and does not represent a real organization's data.

About

This project focuses on performing network forensic analysis on a captured ".pcap" file using Wiresharks Tool

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published