s225645819/malware-traffic-analysis-nuclear-ek
GitHub: s225645819/malware-traffic-analysis-nuclear-ek
Stars: 0 | Forks: 0
# Malware Traffic Analysis — Nuclear Exploit Kit Infection
A network forensics investigation of a real malware infection, analyzed from a packet
capture (PCAP) in **Wireshark**. This report reconstructs a drive-by-download attack in
which a Windows host was compromised via the **Nuclear Exploit Kit** after visiting a
legitimate-but-hacked website, and documents the full infection chain, extracted malware
samples, indicators of compromise (IOCs), and MITRE ATT&CK mapping.
## Executive Summary
A Windows workstation (`K34EN6W3N-PC`, `172.16.165.165`) became infected after a user
browsed to a compromised website. The site silently redirected the browser through a gate
to a Nuclear Exploit Kit server, which fired **Flash and Java exploits** against the
victim's outdated browser plugins. Exploitation succeeded and the kit delivered an
**obfuscated Windows executable (~401 KB)** disguised as an MP3 request. The full chain
was reconstructed from HTTP traffic, and all three malicious files (payload + two exploits)
were extracted and hashed.
## Victim Host Identification
| Attribute | Value | How it was found |
|---|---|---|
| IP address | `172.16.165.165` | `Statistics → Conversations → IPv4` — busiest internal host, fanning out to many external IPs |
| MAC address | `f0:19:af:02:9b:f1` | Ethernet conversation (3,000 pkts / 2 MB) + Ethernet II layer |
| Host name | `K34EN6W3N-PC` | NBNS traffic (`nbns` filter) — "Refresh NB K34EN6W3N-PC" |
&num=&PHPSSESID=`, serving exploits by type:
- `req=swf` → Adobe Flash exploit (`application/x-shockwave-flash`)
- `req=jar` → Java exploit (`application/java-archive`)
- `req=mp3` → the malware payload (`application/x-msdownload`, disguised by the "mp3" label)
The victim's outbound request advertised `x-flash-version: 11,2,2...`, indicating the
vulnerable Flash plugin the kit targeted.
**Stage 4 — Payload delivery.**
The kit delivered a ~401 KB Windows executable three times (`num=16`, `num=95`,
`num=803295`) over HTTP. The file is obfuscated in transit (does not present a clean PE
header on the wire), a common EK technique to evade network detection; the browser exploit
decodes it on execution.
## Extracted Artifacts & IOCs
All three malicious files were carved from the PCAP via `Export Objects → HTTP` and hashed
offline. **No file was executed.**