<?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 Favouriloanya on Medium]]></title>
        <description><![CDATA[Stories by Favouriloanya on Medium]]></description>
        <link>https://medium.com/@favouriloanya007?source=rss-499d3adadf63------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*PBHEPFBnGAEJHfIu</url>
            <title>Stories by Favouriloanya on Medium</title>
            <link>https://medium.com/@favouriloanya007?source=rss-499d3adadf63------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 15:34:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@favouriloanya007/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[Building My Malware Analysis Lab: Setting Up FLARE-VM and REMnux]]></title>
            <link>https://medium.com/@favouriloanya007/building-my-malware-analysis-lab-setting-up-flare-vm-and-remnux-ee30d5757723?source=rss-499d3adadf63------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee30d5757723</guid>
            <dc:creator><![CDATA[Favouriloanya]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 17:41:47 GMT</pubDate>
            <atom:updated>2026-11-17T17:41:47.603Z</atom:updated>
            <content:encoded><![CDATA[<p>Every cybersecurity analyst needs a place to experiment, investigate, break things (safely), and learn.</p><p>For me, that meant building my own isolated lab using FLARE-VM and REMnux for my Malware Analysis.</p><p>This environment would serve as where I could examine suspicious files, observe malware behaviour, analyse network traffic, and understand what happens behind the scenes during a malware attack.</p><p>So, I got to work.</p><p>STEP 1: Setting up FLARE-VM</p><p>I downloaded and created a Windows 11 virtual machine and allocated resources to it. In my current configuration, FLARE-VM has 8 GB of RAM and four processors.</p><p>Next came the FLARE-VM installation process. I used its PowerShell installation script and watched as the setup began preparing the environment and checking internet connectivity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*y0ipePSVIgZmcp6wZ-ZSig@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*RYuqPypuj4U3ZcQ-dnI3_Q@2x.jpeg" /></figure><p>STEP2: Setting up REMnux</p><p>After downloading on my host machine, I imported the REMnux virtual appliance into VirtualBox and started working through its configuration.</p><p>I also checked the downloaded OVA file using PowerShell’s SHA-256 hashing command. This gave me a way to verify the downloaded file against its official checksum.</p><p>Inside REMnux, I explored the INetSim configuration file. INetSim is useful for simulating internet services in a controlled lab, allowing analysts to observe how suspicious software attempts to communicate with external services.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/584/1*isZur0Gsco8DS6LF-PEp9A@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/470/1*J6EE4HgvCcoC2rP9Rb0Rmg@2x.jpeg" /></figure><p>STEP3: Configuring the lab</p><p>A malware analysis lab needs more than working virtual machines. It needs isolation.</p><p>I began examining network settings, including static IP configuration, and how the virtual machines would communicate within the lab.</p><p>The goal is to create a controlled environment where I can observe malware behaviour without exposing my everyday computer or network to unnecessary risk.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/405/1*U2wi39JX8IeudoErSuvO9Q@2x.jpeg" /></figure><p>The goal isn’t just to install the tools. It was to understand how to use them to investigate threats.</p><p><em>One lab at a time. One investigation at a time.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee30d5757723" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Inside the Qilin Ransomware Group: My Journey into Threat Intelligence Investigation]]></title>
            <link>https://medium.com/@favouriloanya007/inside-the-qilin-ransomware-group-my-journey-into-threat-intelligence-investigation-5a3e910026a6?source=rss-499d3adadf63------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a3e910026a6</guid>
            <dc:creator><![CDATA[Favouriloanya]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 07:16:44 GMT</pubDate>
            <atom:updated>2026-11-17T07:16:44.013Z</atom:updated>
            <content:encoded><![CDATA[<p>What happens behind a ransomware attack? How do threat actors operate, what techniques do they use, and how can we understand their activities before they cause significant damage?</p><p>These were some of the questions that inspired my recent investigation into the Qilin ransomware group.</p><p>I wanted to go beyond reading about ransomware attacks. I wanted to understand the adversary, investigate its behaviour, and see how its tactics and techniques connect throughout an attack.</p><p>So, I got to work!</p><p>I started by researching Qilin using publicly available threat intelligence sources. I explored MITRE ATT&amp;CK to identify its documented tactics, techniques, and procedures (TTPs), while BleepingComputer provided useful insights into reported Qilin campaigns and real-world attacks.</p><p>I also used VirusTotal to investigate indicators and gather supporting intelligence, while WHOIS helped me examine domain registration and infrastructure information.</p><p>But one part of the investigation particularly caught my attention: <strong><em>MITRE ATT&amp;CK Navigator.</em></strong></p><p>I used Navigator to map and colour-code the identified adversary techniques, turning my research into a visual representation of Qilin’s attack behaviours.</p><p>Seeing the techniques mapped across different stages of the attack lifecycle helped me understand something important: ransomware attacks are rarely just about encrypting files. They involve a series of activities that can work together to achieve an attacker’s objectives.</p><p>Another important lesson was learning not to treat intelligence findings as absolute conclusions. For instance, an indicator not being flagged by VirusTotal does not automatically make it safe. Context, correlation, and further investigation matter.</p><p>Overall, this was more than just a research exercise. It was an opportunity to apply OSINT, investigate threat intelligence, analyse adversary behaviour, and translate research into meaningful security insights.</p><p>One lesson I’ll carry forward:</p><blockquote>To understand an attack, you must first understand the adversary behind it.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*o3uGE_3JsYEW7XwYMc1eLg@2x.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a3e910026a6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>