<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://eve-maina.github.io/</id><title>CyberB4dd!3</title><subtitle>Sharing cybersecurity knowledge through CTF write-ups, technical blogs, and creative projects.</subtitle> <updated>2025-12-10T22:10:17+00:00</updated> <author> <name>Eve Maina</name> <uri>https://eve-maina.github.io/</uri> </author><link rel="self" type="application/atom+xml" href="https://eve-maina.github.io/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://eve-maina.github.io/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2025 Eve Maina </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>P3RF3CTR00TCTF 2025-Web Writeup</title><link href="https://eve-maina.github.io/posts/P3RF3CTR00TCTF-2025-Web-Writeup/" rel="alternate" type="text/html" title="P3RF3CTR00TCTF 2025-Web Writeup" /><published>2025-12-10T00:00:00+00:00</published> <updated>2025-12-10T21:59:51+00:00</updated> <id>https://eve-maina.github.io/posts/P3RF3CTR00TCTF-2025-Web-Writeup/</id> <content type="text/html" src="https://eve-maina.github.io/posts/P3RF3CTR00TCTF-2025-Web-Writeup/" /> <author> <name>Eve Maina</name> </author> <category term="CTF" /> <category term="Web" /> <summary>This write-up details the process of identifying and exploiting a Server-Side Request Forgery (SSRF) vulnerability to gain administrative access and retrieve the flag. The challenge provided us with this zip file . We were provided with this landing page on visiting the site: Step 1: Reconnaissance:The Code Review (Hunting for Bugs) The first thing I did was crack open the provided sour...</summary> </entry> <entry><title>AUTO SCALING IN AWS</title><link href="https://eve-maina.github.io/posts/AUTO-SCALING-IN-AWS/" rel="alternate" type="text/html" title="AUTO SCALING IN AWS" /><published>2025-11-07T00:00:00+00:00</published> <updated>2025-11-08T00:19:33+00:00</updated> <id>https://eve-maina.github.io/posts/AUTO-SCALING-IN-AWS/</id> <content type="text/html" src="https://eve-maina.github.io/posts/AUTO-SCALING-IN-AWS/" /> <author> <name>Eve Maina</name> </author> <category term="CLOUD" /> <category term="Compute" /> <summary>Project Overview In this project, I use the AWS Command Line Interface (CLI) to launch an Amazon EC2 instance that hosts a web server and create an Amazon Machine Image (AMI) from it. The AMI then serves as the foundation for deploying a system that automatically scales under variable workloads through Amazon EC2 Auto Scaling. To ensure high availability and efficient traffic distribution, I a...</summary> </entry> <entry><title>247 CTF-ICMP Tunneling</title><link href="https://eve-maina.github.io/posts/247-CTF-ICMP-Tunneling/" rel="alternate" type="text/html" title="247 CTF-ICMP Tunneling" /><published>2025-10-31T00:00:00+00:00</published> <updated>2025-10-31T00:00:00+00:00</updated> <id>https://eve-maina.github.io/posts/247-CTF-ICMP-Tunneling/</id> <content type="text/html" src="https://eve-maina.github.io/posts/247-CTF-ICMP-Tunneling/" /> <author> <name>Eve Maina</name> </author> <category term="CTF" /> <category term="Networking" /> <summary>This write-up covers extracting a hidden flag from ICMP traffic — a hands-on look at ICMP tunneling / data exfiltration, showing protocol discovery, payload extraction &amp;amp; reassembly, file carving of the embedded image, and practical defenses to detect and mitigate such attacks. Provided is the following pcap file to analyse. The first thing I did was get a feel for the capture and confirm...</summary> </entry> <entry><title>I&amp;M BANK 2025 CTF-Network Forensics Writeup</title><link href="https://eve-maina.github.io/posts/I&amp;M-BANK-2025-CTF-Network-Forensics-Writeup/" rel="alternate" type="text/html" title="I&amp;amp;M BANK 2025 CTF-Network Forensics Writeup" /><published>2025-10-12T00:00:00+00:00</published> <updated>2025-11-07T23:49:56+00:00</updated> <id>https://eve-maina.github.io/posts/I&amp;M-BANK-2025-CTF-Network-Forensics-Writeup/</id> <content type="text/html" src="https://eve-maina.github.io/posts/I&amp;M-BANK-2025-CTF-Network-Forensics-Writeup/" /> <author> <name>Eve Maina</name> </author> <category term="CTF" /> <category term="Network Forensics " /> <summary>Catch if you can We were given this pcap file analyze. Given this pcap file, the first thing I did was apply the filter frame contains “flag” to check if any packets contained references to a flag. Two packets appeared, each with a GET request—one for flag.txt and the other for flaggy.txt. This looked like the right place to find the flag, so I followed each stream. I started with flag.tx...</summary> </entry> <entry><title>I&amp;M BANK 2025 CTF - Incident Response Write Up</title><link href="https://eve-maina.github.io/posts/I&amp;M-BANK-2025-CTF-Incident-Responce-Writeup/" rel="alternate" type="text/html" title="I&amp;amp;M BANK 2025 CTF - Incident Response Write Up" /><published>2025-10-07T00:00:00+00:00</published> <updated>2025-11-07T23:49:56+00:00</updated> <id>https://eve-maina.github.io/posts/I&amp;M-BANK-2025-CTF-Incident-Responce-Writeup/</id> <content type="text/html" src="https://eve-maina.github.io/posts/I&amp;M-BANK-2025-CTF-Incident-Responce-Writeup/" /> <author> <name>Eve Maina</name> </author> <category term="CTF" /> <category term="Incident Response" /> <summary>Compromised server-1 We were given this pcap file analyze. Given such a challenge, the first thing I did was to identify the attacker’s IP address. This helps in getting a better understanding of the traffic flow. To achieve this, I used wireshark - a packet analysis tool. After opening the pcap file on wireshark, Under Statistics &amp;gt;Conversations&amp;gt; IPv4 , I sorted the packets in descend...</summary> </entry> </feed>
