Traffic Analysis Quiz: Ugly-Wolf.net

Published: 2020-10-16
Last Updated: 2020-10-16 03:51:07 UTC
by Brad Duncan (Version: 1)
2 comment(s)

Introduction

It's that time of the month again...  Time for another traffic analysis quiz!  This one is from a Windows 10 client logged into an Active Directory (AD) environment.  Details follow:

  • LAN segment:  10.10.16.0/24 (10.10.16.1 through 10.10.16.255)
  • Domain Controller:  Ugly-Wolf-DC at 10.10.16.6
  • Gateway:  10.10.16.1
  • Broadcast address:  10.10.16.255

The pcap and alerts are available on my Github repository at:

The zip archives are password-protected with the term: infected

The alerts archive contains an image of alerts and a text file with the same information.


Shown above:  Alerts image for this quiz, with the alerts blurred (you'll have to download the alerts file to see them).

The alerts file was created using Security Onion running Suricata using the EmergingThreats Pro ruleset, and the alerts were viewed using Sguil.

The alerts should give away the type of infection(s) happening on the Windows computer at ugly-wolf.net.  Since this is an AD environment, you should also be able to find the user account name that was logged into the Windows host before it became infected.  In a real-world situation, this could help you track down an infected user and perform incident response actions.

You can also use this quiz to practice drafting an incident report.

If the answers are not obvious, feel free to leave a comment in the comments section, and I'll answer when I get the time.

---
Brad Duncan
brad [at] malware-traffic-analysis.net

Keywords:
2 comment(s)

Comments

Is the actual file removed? I can see the file name being downloaded but when I look at the HTTP object list it isn't there. I tried a different pcap and can see files in it so I feel it should work, or I'm missing something. I got the PC name, OS version, browser, user, and website right away. Good practice! Thanks for this!
Thanks for the reply! The file names listed in the export HTTP object list are based on the last part of the URL. For example, the URL to filmtalks[.]co that returned an EXE ended with /YZ, so that object will show up as "YZ" as the Filename in the HTTP object list. The URL to vastraindia[.]com that ended with /haVu4Afjor4px returned the Word document, so that object shows up as "haVu4Afjor4px" for the Filename in the HTTP object list.

These won't show up as whatever the "filename" line shows from the HTTP response headers.

Hope this helps.

Diary Archives