<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Singhvimahi on Medium]]></title>
        <description><![CDATA[Stories by Singhvimahi on Medium]]></description>
        <link>https://medium.com/@singhvimahi1?source=rss-4d6976d73a27------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*EYOXgq3azyfuVeYj9KLw-Q.jpeg</url>
            <title>Stories by Singhvimahi on Medium</title>
            <link>https://medium.com/@singhvimahi1?source=rss-4d6976d73a27------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 12:49:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@singhvimahi1/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Zeek: The Most Underrated Network Security Engine You Should Be Using in 2025]]></title>
            <link>https://medium.com/@singhvimahi1/zeek-the-most-underrated-network-security-engine-you-should-be-using-in-2025-88a0035f7319?source=rss-4d6976d73a27------2</link>
            <guid isPermaLink="false">https://medium.com/p/88a0035f7319</guid>
            <category><![CDATA[network-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[threat-hunting]]></category>
            <category><![CDATA[network-monitoring]]></category>
            <dc:creator><![CDATA[Singhvimahi]]></dc:creator>
            <pubDate>Sun, 30 Nov 2025 09:41:31 GMT</pubDate>
            <atom:updated>2025-11-30T09:41:31.216Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’ve ever worked with network monitoring or threat hunting, you’ve probably heard of tools like <strong>Wireshark</strong>, <strong>Suricata</strong>, or <strong>Snort</strong>.<br> But quietly powering some of the most advanced SOCs and research labs in the world is a tool many newcomers completely overlook:</p><p><strong>Zeek</strong> (formerly Bro) — an insanely powerful, flexible, and scriptable network security monitoring framework.</p><p>Zeek isn’t just another IDS. It’s a <strong>network analysis microscope</strong>, capable of revealing exactly what’s happening inside your traffic with breathtaking detail.</p><p>Let’s dive in.</p><h3>What is Zeek?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/507/1*8KmT3Gv3-J852AJ5rxb33w.png" /></figure><p>Zeek (formerly Bro) is a <strong>network analysis framework</strong> that observes traffic, interprets protocols, detects anomalies, and generates rich logs.<br> Instead of focusing on signatures or alerts, Zeek focuses on <strong>interpreting behavior</strong>.</p><p>Think of it as a <strong>network microscope</strong> that helps you see:</p><ul><li>What protocols are being used</li><li>How systems are communicating</li><li>What files are being transferred</li><li>What domains are being queried</li><li>Whether traffic looks unusual or suspicious</li></ul><p>Zeek never blocks traffic. It observes, analyzes, and transforms raw packets into rich, structured logs.</p><h3>Why Zeek Is So Useful?</h3><h4>1. Deep Protocol Understanding</h4><p>Zeek understands dozens of protocols out of the box, including:</p><ul><li>HTTP</li><li>DNS</li><li>TLS/SSL</li><li>SMTP</li><li>FTP</li><li>SSH</li><li>SMB … and many more.</li></ul><p>This makes it extremely effective for real-world traffic analysis.</p><h4>2. Structured Logs That Actually Make Sense</h4><p>Zeek’s biggest strength is its logs.</p><p>For each protocol, it creates a separate log file — simple, organized, and extremely useful for analysts.</p><p>Some of the most important logs include:</p><ul><li><strong>conn.log</strong> — connection-level details</li><li><strong>dns.log</strong> — all DNS queries</li><li><strong>http.log</strong> — URLs, headers, user-agents</li><li><strong>ssl.log</strong> — certificates &amp; JA3 fingerprints</li><li><strong>files.log</strong> — file hashes &amp; metadata</li><li><strong>weird.log</strong> — anomalies and protocol violations</li></ul><p>These logs are gold for DFIR, threat hunting, and visibility.</p><h4>3. Detects Suspicious Behavior Naturally</h4><p>Zeek analyzes behavior, which means it can highlight:</p><ul><li>Abnormal DNS patterns</li><li>Strange TLS certificates</li><li>Suspicious HTTP traffic</li><li>Unexpected connections</li><li>Protocol misuse</li><li>Possible data exfiltration</li></ul><p>It helps analysts notice things that traditional logs would never show.</p><h4>4. Customizable with Scripts</h4><p>Zeek uses an event-driven scripting language.<br> You can write your own detection logic like:</p><ul><li>Flag repeated failed logins</li><li>Detect beaconing behavior</li><li>Identify suspicious JA3 hashes</li><li>Alert on tunneling patterns</li></ul><p>This makes Zeek infinitely flexible.</p><h3>How Zeek Works (Simple)</h3><ol><li><strong>Capture traffic</strong> (live or from PCAP)</li><li><strong>Parse protocols</strong></li><li><strong>Trigger events</strong></li><li><strong>Scripts decide what to log</strong></li><li><strong>Logs get stored for analysis</strong></li></ol><p>That’s it — simple, clean, powerful.</p><h4>How to Run Zeek (Quick Commands)</h4><p>Run Zeek on a PCAP:</p><pre>zeek -r file.pcap</pre><p>Run Zeek on a live interface:</p><pre>zeek -i eth0</pre><p>Logs will appear in the logs/ directory.</p><h3>Why You Should Learn Zeek</h3><p>Zeek is one of the most valuable tools for:</p><ul><li>SOC analysts</li><li>Threat hunters</li><li>DFIR teams</li><li>Students learning network security</li><li>Anyone analyzing PCAP files or network logs</li></ul><p>It teaches you how real network traffic behaves — and how attackers try to hide inside it.</p><p>If you want to build strong network security skills, Zeek is a tool that will level up your understanding instantly.</p><p><em>Whether you’re a beginner or a professional, Zeek is a tool worth learning and using.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88a0035f7319" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Inside the Shadows: Exploring Fileless Malware Through Hands-On Research]]></title>
            <link>https://medium.com/@singhvimahi1/inside-the-shadows-exploring-fileless-malware-through-hands-on-research-a9d58796eca0?source=rss-4d6976d73a27------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9d58796eca0</guid>
            <category><![CDATA[fileless-malware]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[malware]]></category>
            <category><![CDATA[digital-forensics]]></category>
            <category><![CDATA[infosec]]></category>
            <dc:creator><![CDATA[Singhvimahi]]></dc:creator>
            <pubDate>Sat, 31 May 2025 08:45:23 GMT</pubDate>
            <atom:updated>2025-05-31T08:45:23.887Z</atom:updated>
            <content:encoded><![CDATA[<p>By Mahi Singhvi</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CWu_42M8AENQFJxIggPPpQ.png" /></figure><p>In recent times, cyber threats have evolved into more advanced and evasive forms, with fileless malware standing out as one of the most difficult to detect. Unlike conventional malware that relies on disk-based executable files, fileless malware functions entirely within the computer’s memory. As a result, traditional antivirus programs, which focus on scanning files stored on the hard drive, often fail to identify it. Instead of saving harmful code to disk, fileless malware exploits legitimate system utilities — like PowerShell, Windows Management Instrumentation (WMI), or registry-based scripts — to execute its malicious tasks discreetly</p><p>What sets fileless malware apart is its ability to exploit the trust given to built-in utilities. For example, attackers might craft a malicious PowerShell script that downloads and executes harmful payloads directly into memory without leaving behind traditional files. Since no new or suspicious files are created, most security software struggles to recognize these threats. Moreover, once the system is rebooted, any traces of the malware may be lost from memory, making forensic analysis extremely challenging unless the behavior was logged or captured in real time.</p><p>Fileless attacks are not entirely “without files” — often they start with a small initial trigger, such as a phishing email or malicious link, that launches the fileless payload. However, the actual malicious activity doesn’t rely on dropping executables to disk. This is why these attacks are also called living off-the-land attacks, as they use tools and permissions already present in the operating system to remain hidden.</p><h3><strong>The Research Project: A Practical Dive</strong></h3><p>My goal with this project was simple but ambitious: understand, simulate, analyze, and document fileless malware behavior inside a controlled virtual lab.</p><h4>Lab Setup</h4><ul><li><strong>Attacker Machine</strong>: Kali Linux</li><li><strong>Victim Machine</strong>: FLARE VM (Windows)</li><li><strong>Tools Used</strong>:</li><li>Metasploit &amp; msfvenom for payload generation</li><li>PowerShell for execution</li><li>Regshot, Process Monitor, Process Explorer for analysis</li></ul><h4><strong>Phase 1: Fileless Execution via PowerShell</strong></h4><p>I began by generating a reverse shell payload using msfvenom and encoding it into a Base64 PowerShell command. The idea was to <strong>simulate an in-memory attack</strong> with zero disk footprint.</p><p>Once executed on the victim machine, the payload initiated a reverse shell connection to Kali, confirming remote access without dropping a file.</p><p>To simulate <strong>persistence</strong> in a fileless manner, I created a malicious PowerShell payload by name <em>ConsoleApplication.exe</em> and embedded it into the Windows registry under :</p><p><em>HKCU\Software\Microsoft\Windows\CurrentVersion\Run</em></p><p>Upon reboot, the system automatically executed the payload from the registry, establishing the reverse shell again — <strong>without any file stored on disk</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/760/1*Incp3uGttRxUSngiJG6hbg.png" /><figcaption>Payload executed on victim machine</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/747/1*x_WQtp4TPi2gTRKa7DWvIw.png" /><figcaption>Meterpreter session opened</figcaption></figure><h4><strong>Behavior Analysis</strong></h4><p>Using tools like <strong><em>Process Explorer</em></strong> and <strong><em>Process Monitor</em></strong>, I traced the payload’s behavior:</p><ul><li>Parent-child process relationships (e.g., powershell.exe spawned by explorer.exe)</li><li>Registry access without file creation</li><li>Memory usage spikes at time of execution</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*cZfnk5Gh0yIv8hwqv_Zuig.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/1*1Nb0m43K0ckpu1iJ2klv7Q.png" /></figure><p>Observed the following activities:</p><ul><li>Multiple TCP Send and TCP Receive operations to 192.168.28.129:49671, indicating network communication with the attacker’s system.</li><li>Thread creation and termination activities, suggesting the malware was executing additional processes or injecting code.</li><li>Registry operations under HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run, where the malware added an entry for persistence by pointing to its location at C:\Users\naikt\Desktop\fileless-malware-project\….</li></ul><p><strong><em>Regshot Analysis</em></strong></p><p>Regshot clearly showed:</p><ul><li>Addition of a new registry key</li><li>No new file creation on disk</li><li>Persistence maintained entirely via system configuration</li></ul><h4>Phase 2 : Removal Strategy</h4><p>Once detected, I simulated the <strong>removal process</strong>:</p><ul><li>Deleted malicious registry entries using Regedit</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*q5Fts89f3eQI5Ifhv0t6Og.png" /></figure><ul><li>Terminated suspicious PowerShell processes</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/743/1*truVbHXBMWVSTC89hHNdpA.png" /></figure><ul><li>Cleared memory-resident payloads via system reboot</li></ul><p><strong>Lesson Learned</strong>: Detection is tricky without behavioral or memory-level inspection. Prevention requires strict policy enforcement, endpoint monitoring, and limiting the use of scripting tools like PowerShell.</p><h4>Key Takeaways</h4><ul><li>Fileless attacks are real, stealthy, and increasing — often used in phishing or lateral movement scenarios.</li><li>Traditional antivirus is insufficient; memory analysis and behavior-based detection are crucial.</li><li>Simulating malware in a safe lab environment is an invaluable learning experience for any aspiring cybersecurity professional.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9d58796eca0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>