Write-ups
Personal WebsiteGithubLinkedIn
  • Home
  • Blue Team Labs Online
    • ATT&CK
    • D3FEND
    • Log Analysis - Privilege Escalation
    • Meta
    • Network Analysis – Web Shell
    • Shiba Insider
    • The Planet's Prestige
    • The Report
  • bWAPP
    • HTML Injection - Reflected (GET)
    • HTML Injection - Reflected (POST)
    • HTML Injection - Reflected (URL)
    • HTML Injection - Stored (Blog)
    • iFrame Injection
  • Command Challenge
    • Command Challenge
    • Oops I deleted my bin/ dir :(
    • Twelve Days of Shell
  • CryptoHack
    • General
      • Encoding
        • ASCII
        • Hex
        • Base64
        • Bytes and Big Integers
      • XOR
        • XOR Starter
        • XOR Properties
        • Favourite byte
      • Mathematics
        • Greatest Common Divisor
        • Extended GCD
  • CSAW 2023
    • Baby's First
    • Baby's Third
    • my_first_pwnie
    • target_practice
  • CTFLearn
    • Binary
      • Simple bof
    • Cryptography
      • 5x5 Crypto
      • Base 2 2 the 6
      • Character Encoding
      • Substitution Cipher
      • Tux!
    • Forensics
      • Forensics 101
      • Git Is Good
      • PDF by fdpumyp
      • Pho Is Tasty!
      • PikesPeak
      • Simple Steganography
      • Taking LS
      • WOW.... So Meta
  • CyberDefenders
    • BlackEnergy
    • Emprisa Maldoc
    • HawkEye
    • HoneyBOT
    • Insider
    • Obfuscated
    • PacketMaze
    • RE101
    • Redline
    • XLM Macros
  • DVWA
    • Brute Force
    • Command Injection
    • CSRF
    • SQL Injection
    • SQL Injection (Blind)
    • Weak Session IDs
    • XSS (DOM)
    • XSS (Reflected)
    • XSS (Stored)
  • Ethernaut
    • 00 - Hello Ethernaut
  • Exploit Education
    • Protostar
      • Stack Zero
      • Stack One
      • Stack Two
      • Stack Three
      • Stack Four
      • Format Zero
  • Google CTF - Beginner's Quest
    • 0000
    • 1837
    • 1943
    • 1965
    • 1987
    • 1988
    • 1989
    • 1990
    • 1994
  • Hacker101
    • Postbook
  • LetsDefend
    • DFIR
      • Phishing
        • Email Analysis
        • Phishing Email
  • Microcorruption
    • New Orleans
    • Sydney
    • Hanoi
    • Reykjavik
    • Cusco
  • NetGarage IO
    • level 1
    • level 2
  • OverTheWire
    • Bandit
  • PicoCTF
    • Forensics
      • information
    • Binary Exploitation
      • Stonks
    • Web Exploitation
      • Cookies
      • dont-use-client-side
      • GET aHEAD
      • Includes
      • Insp3ct0r
      • Insect HTML
      • login
      • where are the robots
  • PortSwigger labs
    • Client-side topics
      • Cross-site scripting (XSS)
        • Reflected XSS into HTML context with nothing encoded
        • Stored XSS into HTML context with nothing encoded
        • DOM XSS in document.write sink using source location.search
        • DOM XSS in innerHTML sink using source location.search
        • DOM XSS in jQuery anchor href attribute sink using location.search source
        • DOM XSS in jQuery selector sink using a hashchange event
        • Reflected XSS into attribute with angle brackets HTML-encoded
        • Stored XSS into anchor href attribute with double quotes HTML-encoded
    • Server-side topics
      • SQL injection
        • SQL injection vulnerability in WHERE clause allowing retrieval of hidden data
        • SQL injection vulnerability allowing login bypass
        • SQL injection attack, querying the database type and version on Oracle
        • SQL injection attack, querying the database type and version on MySQL and Microsoft
        • SQL injection attack, listing the database contents on non-Oracle databases
        • SQL injection attack, listing the database contents on Oracle
        • SQL injection UNION attack, determining the number of columns returned by the query
        • SQL injection UNION attack, finding a column containing text
        • SQL injection UNION attack, retrieving data from other tables
        • SQL injection UNION attack, retrieving multiple values in a single column
      • Authentication
        • Username enumeration via subtly different responses
        • Password reset broken logic
        • Username enumeration via different responses
        • 2FA simple bypass
      • Path traversal
        • File path traversal, traversal sequences stripped non-recursively
        • File path traversal, traversal sequences blocked with absolute path bypass
        • File path traversal, simple case
        • File path traversal, traversal sequences stripped with superfluous URL-decode
        • File path traversal, validation of start of path
        • File path traversal, validation of file extension with null byte bypass
      • Command injection
        • Blind OS command injection with output redirection
        • OS command injection, simple case
        • Blind OS command injection with time delays
      • Business logic vulnerabilities
        • Flawed enforcement of business rules
        • Excessive trust in client-side controls
        • Inconsistent security controls
        • High-level logic vulnerability
      • Information disclosure
        • Authentication bypass via information disclosure
        • Source code disclosure via backup files
        • Information disclosure on debug page
        • Information disclosure in error messages
      • Access control
        • Referer-based access control
        • Multi-step process with no access control on one step
        • Insecure direct object references
        • URL-based access control can be circumvented
        • Method-based access control can be circumvented
        • User ID controlled by request parameter with password disclosure
        • User ID controlled by request parameter with data leakage in redirect
        • User ID controlled by request parameter, with unpredictable user IDs
        • User ID controlled by request parameter
        • User role can be modified in user profile
        • Unprotected admin functionality with unpredictable URL
        • Unprotected admin functionality
        • User role controlled by request parameter
      • Server-side request forgery (SSRF)
        • Basic SSRF against another back-end system
        • Basic SSRF against the local server
        • SSRF with blacklist-based input filter
      • XXE injection
        • Exploiting XXE to perform SSRF attacks
        • Exploiting XXE using external entities to retrieve files
  • Pwn College
    • Assembly Crash Course
    • Building a Web Server
    • Cryptography
    • Debugging Refresher
    • Intercepting Communication
    • Memory Errors
    • Program Interaction
    • Program Misuse
    • Reverse Engineering
    • Sandboxing
    • Shellcode Injection
    • Talking Web
    • Web Security
  • pwanable.kr
    • fd
    • random
  • Root Me
    • App - System
      • ELF x86 - Stack buffer overflow basic 1
    • Web - Client
      • HTML-disabled buttons
      • Javascript - Authentication
      • Javascript - Source
      • Javascript - Authentication 2
      • Javascript - Obfuscation 1
      • Javascript - Obfuscation 2
      • Javascript - Native code
    • Web - Server
      • HTML - Source code
      • HTTP - IP restriction bypass
      • HTTP - Open redirect
      • HTTP - User-agent
      • PHP - Command injection
      • HTTP - Directory indexing
      • HTTP - Headers
      • HTTP - POST
      • HTTP - Improper redirection
      • HTTP - Verb tampering
      • Install files
  • ROP Emporium
    • ret2win
    • split
  • TryHackMe
    • Easy
      • Agent Sudo
      • Anthem
      • Archangel
      • Bounty Hacker
      • Brooklyn Nine Nine
      • Brute It
      • c4ptur3-th3-fl4g
      • Chill Hack
      • Crack the Hash
      • CTF collection Vol.1
      • Cyborg
      • Fowsniff CTF
      • GamingServer
      • h4cked
      • LazyAdmin
      • Lian_Yu
      • OhSINT
      • Overpass
      • Pickle Rick
      • RootMe
      • Searchlight - IMINT
      • Simple CTF
      • Startup
      • Sudo Security Bypass
      • tomghost
      • Wgel CTF
      • Year of the Rabbit
    • Medium
      • Anonymous
      • ConvertMyVideo
      • UltraTech
  • Under The Wire
    • Century
    • Cyborg
  • W3Challs
    • Web
      • Change your browser
  • Websec.fr
    • level01
    • level04
    • level17
    • level25
    • level28
Powered by GitBook
On this page

Was this helpful?

  1. CyberDefenders

HawkEye

Last updated 1 year ago

Was this helpful?

Always open malware in a secure environment like a VM.

We will be using the distribution which is specifically made for reverse engineering.

Q1. How many packets does the capture have?

  • In order to find the number of packets we have to go to the Statistics > Capture File Properties section.

Q2. At what time was the first packet captured?

  • We have to set the format to UTC in the View > Time Display Format section.

  • Alternatively, we can also find the answer in the Capture File Properties section.!

Q3. What is the duration of the capture?

  • Again this answer can be found in the Capture File Properties section.

Q4. What is the most active computer at the link level?

  • If we go to the Statistics > Endpoints section, we can see information about all the devices in the packet transfer.

Q5. Manufacturer of the NIC of the most active system at the link level?

  • Open the Ethernet section of the file.

  • Alternatively, we can also use Wireshark to find the NIC manufacturer.

  • Put the following filter on in order to filter for relevant traffic.

eth.addr==00:08:02:1c:47:ae
  • On applying the filter, we can see the following packet.

  • Same answer as the one we got from A-Packets.

Q6. Where is the headquarter of the company that manufactured the NIC of the most active computer at the link level?

  • A quick Google search tells us where the headquarters are located.

Q7. The organization works with private addressing and netmask /24. How many computers in the organization are involved in the capture?

  • The /24 subnet mask denotes that the first 24 bytes are part of the network and the last 8 bytes are part of the host.

  • This means that every host within the 10.4.10.x/24 subnet is part of the organization.

  • We can see that the first 3 devices are part of the same subnet thus the same organization. Note that the broadcast address is not counted.

Q8. What is the name of the most active computer at the network level?

  • Since we already know the MAC address of the most active host, we can set a filter for that address and dhcp to find the host name.

eth.addr==00:08:02:1c:47:ae && dhcp
  • Let's look at the Host Name option.

Q9. What is the IP of the organization's DNS server?

  • In the DNS section of A-Packets, we can see the IP of the organization.

  • We can also filter for dns packets in Wireshark.

Q10. What domain is the victim asking about in packet 204?

  • Let's analyze the 204th packet.

Q11. What is the IP of the domain in the previous question?

  • Let's look through the Connections section in A-Packets.

  • In order to find the answer in Wireshark, we have to set the following filter:

frame contains proforma-invoices.com
  • Look in the destination IP address field.

Q12. Indicate the country to which the IP in the previous section belongs.

  • We can use the IP Lookup tool in DNSChecker.

Q13. What operating system does the victim's computer run?

  • Let's filter the http requests using the following filter:

eth.addr==00:08:02:1c:47:ae && http.request
  • Go to Follow > TCP Stream in order to see the entire message.

  • We can also find the OS in the HTTP section of A-Packets.

Q14. What is the name of the malicious file downloaded by the accountant?

  • In the HTTP Headers section of A-Packets, we can find the file that is being downloaded. !

  • Alternatively, in Wireshark we can filter for GET request using the following filter:

http.request.method == GET
  • Only the 210th packet is accessing a file.

Q15. What is the md5 hash of the downloaded file?

  • Let's extract the file via File > EXport Objects > HTTP.

  • We can now use md5sum command in order to obtain the file hash.

$ md5sum tkraw_Protected99.exe 
71826ba081e303866ce2a2534491a2f7  tkraw_Protected99.exe

Q17. What software runs the webserver that hosts the malware?

  • In Wireshark, we can again follow the TCP Stream in order to find the server.

Q18. What is the public IP of the victim's computer?

  • Let's filter for all HTTP requests:

http.request
  • If we follow TCP Stream, we can find the public IP.

Q19. In which country is the email server to which the stolen information is sent?

  • We can use the IP Lookup tool in DNSChecker.

Q20. Analyzing the first extraction of information. What software runs the email server to which the stolen data is sent?

  • Put on the following filter:

ip.addr == 10.4.10.132 && smtp.req
  • We can follow the TCP stream.

Q21. To which email account is the stolen information sent?

  • Further down in the TCP stream we can see the email that the information is sent to. !

Q22. What is the password used by the malware to send the email?

  • We will use the same filter as before:

ip.addr == 10.4.10.132 && smtp.req
  • We can see a password. However, it seems to be base64 encoded.

  • Let's use CyberChef to decode the password.

Q23. Which malware variant exfiltrated the data?

  • If we follow the same TCP stream, we can see a huge blob of data.

  • This has been base64 encoded. We have to again use CyberChef to decode it.

Q24. What are the bankofamerica access credentials? (username:password)

  • This information is available in the output for the previous question.

Q25. Every how many minutes does the collected data get exfiltrated?

  • If we look at the SMTP packets, we can see that the email is sent every 10 minutes.

We can use , in order to find the answer easily.

The source address is 00:08:02:1c:47:ae. Let's search this MAC address on .

We can also upload the file to in order to find the file hash.

A-Packets
DNSChecker
VirusTotal
REMnux