<?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 Medxploit on Medium]]></title>
        <description><![CDATA[Stories by Medxploit on Medium]]></description>
        <link>https://medium.com/@muhammedabdulazeez770?source=rss-41d6a878651b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*mcJI-aG-Xzxl35o4YpzNHg.jpeg</url>
            <title>Stories by Medxploit on Medium</title>
            <link>https://medium.com/@muhammedabdulazeez770?source=rss-41d6a878651b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 03:25:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@muhammedabdulazeez770/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 New Challenge Begins: Conquering All PortSwigger Web Security Labs]]></title>
            <link>https://medium.com/@muhammedabdulazeez770/a-new-challenge-begins-conquering-all-portswigger-web-security-labs-67f72f16711e?source=rss-41d6a878651b------2</link>
            <guid isPermaLink="false">https://medium.com/p/67f72f16711e</guid>
            <dc:creator><![CDATA[Medxploit]]></dc:creator>
            <pubDate>Thu, 22 Jan 2026 18:15:40 GMT</pubDate>
            <atom:updated>2026-01-22T18:15:40.825Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FNhQvHtWpZkv777nqBVlQA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GNx8BD8PDkX6p9q9CdULfA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a51TtrbVMCk1BVmfqJcQBQ.png" /></figure><p>Today, I’m starting a challenge I’ve been thinking about for a while: <strong>solving every single lab on PortSwigger’s Web Security Academy</strong>.</p><p>PortSwigger’s labs are widely respected in the security community for a reason. They don’t just explain vulnerabilities — they force you to <em>think like an attacker</em>. From classic issues like <strong>SQL Injection and Cross-Site Scripting (XSS)</strong> to more advanced topics such as <strong>Server-Side Request Forgery (SSRF), authentication logic flaws, access control vulnerabilities, and prototype pollution</strong>, the labs mirror real-world web application security problems.</p><p>This challenge isn’t about speed or bragging rights. It’s about <strong>depth</strong>. I want to fully understand:</p><ul><li><em>Why</em> a vulnerability exists</li><li><em>How</em> it can be exploited in different ways</li><li><em>What</em> effective remediation actually looks like in practice</li></ul><p>As I progress, I’ll be documenting my journey in a series I’m calling <strong>WebHackDiaries</strong>. I’ll share:</p><ul><li>Key technical learnings</li><li>Interesting or tricky bypasses</li><li>Common mistakes and misconceptions</li><li>Reflections on labs that truly stretch my thinking</li></ul><p>The goal is not only to grow personally, but also to <strong>share practical knowledge</strong> that others on a similar path can benefit from — whether you’re into <strong>penetration testing, bug bounty hunting, or defensive security</strong>.</p><p>Web security is a field where hands-on practice matters more than theory, and PortSwigger provides one of the best environments to sharpen that skill set.</p><p>This is the beginning of a long but rewarding journey.<br> Let’s see how far consistency, curiosity, and practice can go.</p><p>— <em>WebHackDiaries begins.</em></p><p><strong>Tags:</strong><br> #WebHackDiaries #PortSwigger #WebSecurity #CyberSecurity #BugBounty #RedTeam</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67f72f16711e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Software Supply Chain Failures: When Trusted Software Becomes the Attack Vector]]></title>
            <link>https://medium.com/@muhammedabdulazeez770/software-supply-chain-failures-when-trusted-software-becomes-the-attack-vector-5865672f1d1b?source=rss-41d6a878651b------2</link>
            <guid isPermaLink="false">https://medium.com/p/5865672f1d1b</guid>
            <category><![CDATA[supply-chain]]></category>
            <dc:creator><![CDATA[Medxploit]]></dc:creator>
            <pubDate>Wed, 31 Dec 2025 03:36:16 GMT</pubDate>
            <atom:updated>2025-12-31T03:36:16.264Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wg-3ZLlKoZeQUlyinbs1kw.png" /></figure><p>Modern software development is built on trust.</p><p>Developers trust open-source libraries.<br> Organizations trust vendors and update mechanisms.<br> Teams trust CI/CD pipelines, containers, and now AI models.</p><p>And attackers exploit that trust.</p><p>Software supply chain failures have become one of the most dangerous and least understood security risks today — not because developers write insecure code, but because <strong>the software they depend on becomes compromised</strong>.</p><h3>What Is a Software Supply Chain Failure?</h3><p>A software supply chain failure occurs when an application relies on <strong>external components</strong> that are:</p><ul><li>Compromised</li><li>Malicious</li><li>Outdated</li><li>Improperly verified</li></ul><p>These components may include:</p><ul><li>Open-source libraries</li><li>Third-party APIs or SaaS services</li><li>Containers and base images</li><li>Build tools and CI/CD systems</li><li>Pre-trained AI models and datasets</li></ul><p>The vulnerability doesn’t live in <em>your</em> code — it lives in <strong>what your code trusts</strong>.</p><p>Attackers exploit these weak links to inject malicious logic, bypass security controls, or steal sensitive data — often without directly attacking the target organization.</p><h3>Why Software Supply Chain Failures Matter</h3><p>Modern applications are no longer standalone systems. A single application may rely on:</p><ul><li>Hundreds of third-party dependencies</li><li>Automated build and deployment pipelines</li><li>External services and cloud infrastructure</li><li>AI models trained by unknown parties</li></ul><p>If <strong>one dependency is compromised</strong>, the entire system can be compromised.</p><p>Supply chain attacks are especially dangerous because they:</p><ul><li>Scale automatically</li><li>Are difficult to detect</li><li>Bypass traditional perimeter defenses</li><li>Affect thousands of organizations at once</li></ul><p>In many cases, the victim installs the malware themselves — believing it is legitimate software.</p><h3>A Real-World Wake-Up Call: SolarWinds (2021)</h3><p>The SolarWinds Orion breach is one of the most infamous supply chain attacks in history.</p><p>Attackers:</p><ul><li>Inserted malicious code into a <strong>legitimate software update</strong></li><li>Signed and distributed it through official SolarWinds channels</li><li>Infected <strong>thousands of organizations</strong> automatically</li></ul><p>This wasn’t a vulnerability in SolarWinds’ business logic.<br> It was a failure in <strong>build security, update verification, and trust assumptions</strong>.</p><p>Organizations didn’t download malware — they installed a trusted update.</p><h3>Supply Chain Risk in the Age of AI</h3><p>As AI becomes embedded into applications, the supply chain grows even more complex.</p><p>Organizations now rely on:</p><ul><li>Pre-trained third-party models</li><li>Fine-tuned datasets of unknown origin</li><li>External AI inference APIs</li></ul><p>A malicious or poorly designed model can:</p><ul><li>Leak sensitive data through outputs</li><li>Contain hidden backdoors triggered by specific inputs</li><li>Produce biased or harmful behavior</li><li>Log or exfiltrate prompts and responses</li></ul><p>Unlike traditional code, AI models often operate as <strong>black boxes</strong>, making malicious behavior harder to detect.</p><h3>Common Software Supply Chain Failure Patterns (With Scenarios)</h3><h3>1. Using Unverified or Unmaintained Dependencies</h3><p><strong>Scenario:</strong><br> A developer installs a popular open-source library without reviewing its maintenance history. The project has been abandoned, and a known vulnerability exists.</p><p>An attacker exploits that vulnerability to execute malicious code on the server.</p><p><strong>Lesson:</strong><br> Popularity does not equal security.</p><h3>2. Automatic Updates Without Integrity Verification</h3><p><strong>Scenario:</strong><br> An organization enables automatic updates for dependencies. A compromised update server delivers a malicious version that is automatically installed in production.</p><p>Because the update is “official,” it is trusted.</p><p><strong>Lesson:</strong><br> Updates must be verified, not blindly trusted.</p><h3>3. Over-Reliance on Third-Party AI Models</h3><p><strong>Scenario:</strong><br> A company integrates a third-party AI model for document processing. Under certain prompts, the model begins leaking sensitive internal data.</p><p>The behavior went unnoticed because the model appeared to function normally.</p><p><strong>Lesson:</strong><br> AI models are part of your attack surface.</p><h3>4. Insecure CI/CD Pipelines</h3><p><strong>Scenario:</strong><br> An attacker gains access to a CI/CD system using leaked credentials. They inject malicious logic during the build process.</p><p>The source code remains clean — but the compiled application is compromised.</p><p><strong>Lesson:</strong><br> If the build pipeline is compromised, every deployment is compromised.</p><h3>5. Poor Dependency Ownership and Provenance Tracking</h3><p><strong>Scenario:</strong><br> A widely used package is taken over by a malicious maintainer after the original author abandons it. A new version includes malicious code.</p><p>Organizations update the dependency without realizing ownership has changed.</p><p><strong>Lesson:</strong><br> Knowing <em>who</em> maintains a dependency matters as much as <em>what</em> it does.</p><h3>6. No Post-Deployment Dependency Monitoring</h3><p><strong>Scenario:</strong><br> A vulnerability is disclosed in a popular library. The organization continues using the vulnerable version for months.</p><p>Attackers exploit the known flaw using public exploits.</p><p><strong>Lesson:</strong><br> Supply chain security doesn’t end at deployment.</p><h3>Why Attackers Love Supply Chain Attacks</h3><p>Supply chain attacks are attractive because they:</p><ul><li>Bypass traditional defenses</li><li>Require minimal direct interaction</li><li>Scale across many victims</li><li>Exploit trust instead of weaknesses</li></ul><p>Instead of breaking into one system, attackers compromise <strong>an entire ecosystem</strong>.</p><h3>Final Thoughts</h3><p>Software supply chain failures highlight a critical truth:</p><blockquote><strong><em>Security is not only about the code you write — it’s about the software you trust.</em></strong></blockquote><p>Every dependency, update mechanism, build tool, and AI model is part of your security boundary.</p><p>In modern security, trust must be:</p><ul><li>Verified</li><li>Monitored</li><li>Continuously reassessed</li></ul><p>Because sometimes, the most dangerous threat doesn’t come from an attacker — <br> it comes from a trusted update.</p><p>Cybersecurity Software Engineering Cloud Security DevSecOps AI Security OWASP</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5865672f1d1b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Security Misconfigurations: The Silent Threat Behind Major Data Breaches]]></title>
            <link>https://medium.com/@muhammedabdulazeez770/security-misconfigurations-the-silent-threat-behind-major-data-breaches-1a732620d555?source=rss-41d6a878651b------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a732620d555</guid>
            <dc:creator><![CDATA[Medxploit]]></dc:creator>
            <pubDate>Wed, 31 Dec 2025 03:04:38 GMT</pubDate>
            <atom:updated>2025-12-31T03:04:38.510Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0IjLKiOBUOKxoASIBlBx5A.png" /></figure><p>When people think about hacking, they often imagine complex exploits, zero-day vulnerabilities, or elite attackers writing advanced code. In reality, many of the <strong>most damaging security breaches happen because of simple configuration mistakes</strong>.</p><p>These mistakes are known as <strong>security misconfigurations</strong> — and they remain one of the most common, yet overlooked, security risks in modern systems.</p><h3>What Are Security Misconfigurations?</h3><p>Security misconfigurations occur when systems, servers, applications, or cloud services are deployed with <strong>unsafe defaults, incomplete settings, or excessive permissions</strong>.</p><p>They are <strong>not coding bugs</strong>. Instead, they are errors in:</p><ul><li>Environment setup</li><li>Cloud permissions</li><li>Network exposure</li><li>Access control</li><li>Software maintenance</li></ul><p>Because modern applications rely on complex stacks — cloud services, APIs, containers, and third-party tools — <strong>one small misstep can expose the entire system</strong>.</p><h3>Why Security Misconfigurations Matter</h3><p>Security misconfigurations are dangerous because they:</p><ul><li>Create <strong>easy entry points</strong> for attackers</li><li>Require little to no skill to exploit</li><li>Are often discoverable through automated scans</li><li>Can expose sensitive data at massive scale</li></ul><p>A single exposed admin panel, open storage bucket, or unrestricted API can lead to:</p><ul><li>Data breaches</li><li>Account takeovers</li><li>Privilege escalation</li><li>Infrastructure compromise</li></ul><h3>Real-World Example: Uber’s 2017 Data Breach</h3><p>In 2017, Uber suffered a major breach where attackers accessed sensitive data of <strong>57 million users and drivers</strong>. The cause was not a sophisticated hack — it was a <strong>misconfigured AWS S3 bucket</strong> containing credentials.</p><p>The bucket was publicly accessible, allowing attackers to download data <strong>without needing valid credentials</strong>.</p><p>This incident highlights a critical truth:</p><blockquote><strong><em>Deployment mistakes can be just as dangerous as software vulnerabilities.</em></strong></blockquote><h3>Common Security Misconfigurations (With Scenarios and Detection Methods)</h3><h3>1. Default Credentials or Weak Passwords</h3><p><strong>Scenario:</strong><br> A system is deployed using default credentials such as admin:admin or root:root. The administrator forgets to change them.</p><p><strong>Impact:</strong><br> Attackers gain full administrative access within seconds.</p><p><strong>How Attackers Find It:</strong></p><ul><li>Scan for login pages (/admin, /login)</li><li>Try known default credentials</li><li>Use brute-force or credential-stuffing tools</li></ul><p><strong>Red Flag:</strong><br> The system allows login without enforcing a password change.</p><h3>2. Unnecessary Services Exposed to the Internet</h3><p><strong>Scenario:</strong><br> Internal services like SSH, FTP, MongoDB, or Redis are exposed publicly, even though they were intended for internal use only.</p><p><strong>Impact:</strong><br> Attackers connect directly, brute-force access, or dump databases.</p><p><strong>How Attackers Find It:</strong></p><ul><li>Port scanning with tools like Nmap</li><li>Internet-wide scanners such as Shodan or Censys</li><li>Reviewing cloud firewall rules</li></ul><p><strong>Red Flag:</strong><br> Critical services responding publicly without restrictions.</p><h3>3. Misconfigured Cloud Storage (S3, Azure Blob, GCP Buckets)</h3><p><strong>Scenario:</strong><br> A cloud storage bucket containing backups or user data is set to <strong>public read or write access</strong>.</p><p><strong>Impact:</strong><br> Anyone can download sensitive data or upload malicious files.</p><p><strong>How Attackers Find It:</strong></p><ul><li>Guess common bucket names (company-backup, prod-data)</li><li>Use cloud security scanning tools</li><li>Check permission policies</li></ul><p><strong>Red Flag:</strong><br> Sensitive files accessible without authentication.</p><h3>4. Unrestricted API Access or Broken Authorization</h3><p><strong>Scenario:</strong><br> An API endpoint allows access without authentication or lets users access data belonging to others.</p><p><strong>Impact:</strong><br> Mass data leakage and account compromise.</p><p><strong>How Attackers Find It:</strong></p><ul><li>Intercept API requests using tools like Burp Suite</li><li>Modify user IDs or remove tokens</li><li>Test role and permission boundaries</li></ul><p><strong>Red Flag:</strong><br> API returns data without validating identity or role.</p><h3>5. Verbose Error Messages in Production</h3><p><strong>Scenario:</strong><br> A production application displays full error messages, including stack traces, file paths, or database details.</p><p><strong>Impact:</strong><br> Attackers gain valuable information for further exploitation.</p><p><strong>How Attackers Find It:</strong></p><ul><li>Input malformed data</li><li>Force application errors</li><li>Access invalid routes</li></ul><p><strong>Red Flag:</strong><br> Detailed technical errors shown to users instead of generic messages.</p><h3>6. Outdated Software and Unpatched Systems</h3><p><strong>Scenario:</strong><br> Servers or applications run outdated versions with known vulnerabilities.</p><p><strong>Impact:</strong><br> Attackers exploit publicly available vulnerabilities with ready-made tools.</p><p><strong>How Attackers Find It:</strong></p><ul><li>Check HTTP headers for version info</li><li>Use vulnerability scanners</li><li>Search CVE databases</li></ul><p><strong>Red Flag:</strong><br> Running software with known public exploits.</p><h3>7. Exposed AI/ML Endpoints Without Access Controls</h3><p><strong>Scenario:</strong><br> AI inference or prediction endpoints are publicly accessible without authentication or rate limiting.</p><p><strong>Impact:</strong><br> Attackers abuse compute resources, steal models, or extract sensitive training data.</p><p><strong>How Attackers Find It:</strong></p><ul><li>Inspect frontend network traffic</li><li>Fuzz API endpoints</li><li>Test rate limits and authentication</li></ul><p><strong>Red Flag:</strong><br> AI endpoints callable by anyone on the internet.</p><h3>Why Attackers Love Misconfigurations</h3><p>Attackers favor misconfigurations because:</p><ul><li>They require minimal effort</li><li>They are easy to automate</li><li>They often go unnoticed for long periods</li><li>They bypass traditional security defenses</li></ul><p>In many cases, <strong>the attacker doesn’t break in — they simply walk in</strong>.</p><h3>Final Thoughts</h3><p>Security misconfigurations are a reminder that <strong>security is not just about writing secure code</strong>, but about <strong>deploying systems correctly and maintaining them continuously</strong>.</p><p>Regular audits, proper access controls, least-privilege permissions, and automated security checks can prevent most of these issues.</p><p>In cybersecurity, sometimes the biggest threats come not from advanced attackers — but from <strong>simple mistakes</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a732620d555" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hiding Secrets in Plain Sight: My Hands-On With Steghide ️]]></title>
            <link>https://medium.com/@muhammedabdulazeez770/hiding-secrets-in-plain-sight-my-hands-on-with-steghide-%EF%B8%8F-75f0db2d288d?source=rss-41d6a878651b------2</link>
            <guid isPermaLink="false">https://medium.com/p/75f0db2d288d</guid>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Medxploit]]></dc:creator>
            <pubDate>Fri, 26 Sep 2025 06:05:27 GMT</pubDate>
            <atom:updated>2025-09-26T06:05:27.319Z</atom:updated>
            <content:encoded><![CDATA[<p>Hiding Secrets in Plain Sight: My Hands-On With Steghide 🔐🖼️</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U618PfQWIFDOIGi3C3deYw.jpeg" /></figure><p>Introduction</p><p>Steganography has always fascinated me — the art of hiding information in plain sight. Unlike encryption, which scrambles data, steganography hides it within another file so it doesn’t even look suspicious. Recently, I experimented with Steghide, a lightweight command-line tool that makes this possible.</p><p>In this post, I’ll walk you through my short lab where I embedded a text file into an image and later extracted it. Along the way, I’ll share why this matters in cybersecurity and how it’s used in both ethical and malicious contexts.</p><p>Step 1: Preparing the Files</p><p>I started by downloading an image and renaming it:</p><p>mv picture.jpg malware.jpg</p><p>Then I created a simple text file using Nano:</p><p>nano love.txt</p><p>Inside, I wrote a short love letter — nothing malicious, just a simple way to test how Steghide hides data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/951/1*CMfyh3LkDh_OE6tvwk80LA.jpeg" /></figure><p>Step 2: Embedding the Text File</p><p>With both files ready, I used Steghide to embed love.txt inside malware.jpg.</p><p>steghide embed -cf malware.jpg -ef love.txt -p &quot;I love&quot;</p><p>Here:</p><p>-cf = cover file (the image)</p><p>-ef = embedded file (the text)</p><p>-p = passphrase (“I love”)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/961/1*ql3HRzMDfsiRztqMz1xDwQ.jpeg" /></figure><p>After running the command, the image still looked the same — but now it secretly contained my love letter.</p><p>Step 3: Extracting the Hidden Data</p><p>To make sure everything worked, I tried extracting the file:</p><p>steghide extract -sf malware.jpg -p &quot;I love&quot;</p><p>Steghide prompted me for the passphrase, and once I entered it, the hidden love.txt appeared again with the exact message I wrote earlier. Success! ✅</p><p>---</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/955/1*HWZg5RyyT7Gq_pz3MKnFmg.jpeg" /></figure><p>Why This Matters</p><p>Steganography isn’t just a fun trick — it has real-world implications:</p><p>Defensive uses: watermarking digital content, protecting intellectual property, or securely transmitting sensitive data.</p><p>Offensive uses: attackers may hide malicious code or instructions inside images, making detection difficult.</p><p>Learning value: in Capture the Flag (CTF) challenges and penetration testing labs, steganography often appears as a puzzle to sharpen investigation skills.</p><p>By practicing in a safe environment, security learners can better understand how hidden data works and how to spot it during investigations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/967/1*xmO0KF_0N_VpQy3CFZP_KQ.jpeg" /></figure><p>Ethical Reminder</p><p>Tools like Steghide are powerful, but they must be used responsibly. Always practice in a controlled environment (your own files, test VMs) — never on systems or data without permission. Ethical hacking is about learning, defending, and improving security, not causing harm.</p><p>Final Thoughts</p><p>This small experiment with Steghide showed me how easy it is to hide data in an image. While my example only hid a harmless love letter, the technique highlights why defenders need to stay alert to steganography in the wild.</p><p>Next time you look at a simple .jpg, remember — there could be more than meets the eye. 👀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75f0db2d288d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ 27 Days of Hacking Starts Now! ]]></title>
            <link>https://medium.com/@muhammedabdulazeez770/27-days-of-hacking-starts-now-23549f5d8539?source=rss-41d6a878651b------2</link>
            <guid isPermaLink="false">https://medium.com/p/23549f5d8539</guid>
            <category><![CDATA[cyber-security-training]]></category>
            <dc:creator><![CDATA[Medxploit]]></dc:creator>
            <pubDate>Wed, 14 May 2025 05:52:53 GMT</pubDate>
            <atom:updated>2025-05-14T05:52:53.859Z</atom:updated>
            <content:encoded><![CDATA[<p>🔐 27 Days of Hacking Starts Now! 🚀</p><p>Hey fam!<br>I’m kicking off #27DaysOfHacking — and you’re invited!</p><p>For the next 27 days, I’ll be dropping daily content on Cybersecurity &amp; Ethical Hacking — from beginner-friendly tools to pro-level tips!</p><p>What to expect: 🛠️ Hands-on hacking demos<br>🕵️‍♂️ Real-world security scenarios<br>💻 Tools like Nmap, Burp Suite, Kali Linux<br>🎯 CTF-style challenges<br>⚠️ Best practices to stay secure</p><p>Follow my page and check in daily —<br>Let’s learn, hack, and grow together in the world of cybersecurity!</p><p>#CyberSecurity #EthicalHacking #LinudinChallenge #HackingCommunity #InfoSec #CTF #TechJourney</p><p>---</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23549f5d8539" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>