<?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 popalltheshells on Medium]]></title>
        <description><![CDATA[Stories by popalltheshells on Medium]]></description>
        <link>https://medium.com/@popalltheshells?source=rss-3d20cd388733------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*-b6WuCfmjt3_kUbryMzqvw.jpeg</url>
            <title>Stories by popalltheshells on Medium</title>
            <link>https://medium.com/@popalltheshells?source=rss-3d20cd388733------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 04:28:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@popalltheshells/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[CAPTCHA bypass is still a thing in 2026]]></title>
            <link>https://popalltheshells.medium.com/captcha-bypass-is-still-a-thing-in-2026-948de351660e?source=rss-3d20cd388733------2</link>
            <guid isPermaLink="false">https://medium.com/p/948de351660e</guid>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[application-security]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[popalltheshells]]></dc:creator>
            <pubDate>Thu, 01 Oct 2026 14:26:01 GMT</pubDate>
            <atom:updated>2026-10-01T14:26:01.703Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Posts are delayed for months or sometime a year at a time to ensure vulnerabilities I post are fixed.</blockquote><p>Oh mein gott, guys it’s been forever since I lasted my last write up, life had been hectic. Took another role elsewhere, but I didn’t align with my personal goals, so I settled back to an Individual Contributor as a lowly and pesky tester. To celebrate my no-longer-too-stressed life, I brought you “CAPTCHA bypass is this still a thing in 2026”, spoiler alert: yes it’s that simple.</p><p>Before we start, there are a few things I’d like you to know before you start complaining:</p><ul><li>No, on its own this is not a vulnerability (per-se), it is an intended function of what registration pages are supposed to be.</li><li>No rate limiting adds impact of this misconfiguration.</li><li>To solve this, add rate limiting AND validate CAPTCHA token on every request rather than relying on a specific parameter.</li></ul><p>OK, so a few months ago I was doing a test for a company who has account enrollment page open. When a normal user tries to create a an account using a regular workflow, the application will prompt the user to complete a Google CAPTCHA prompt to complete.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/381/1*RTiASpo1QVJ7T6F7m8TKmg.png" /></figure><p>When you go through this CAPTCHA prompt and select “verify”, the application will then send a request to the server containing the new user enrollment information, along with <strong>CAPTCHA token for that session</strong>, and a “ReCaptchaValidated:false” parameter.</p><p>Ok now at this point you should know where this is going. Like any L33T Hax0rs would do, I sent this request to my repeater. BUT, when you actually send the same request again with a different username, you will get a 401 unauthorized. Changing this value from <strong>“false” to “true”</strong> will bypass this CATPCHA, give you a 200 OK response, allowing anyone to flood the application server with arbitrary accounts, filling up its database.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2ki9XnYf5xpFFY2_IsMpWg.png" /><figcaption>200 OK response after changing parameter value</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vOp62Pb9J7CVFTDgOcg-LQ.png" /><figcaption>Confirmation e-mail that the account has been created</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=948de351660e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One Photo. One Prompt. Exact Coordinates. [Claude Opus 5]]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://infosecwriteups.com/one-photo-one-prompt-exact-coordinates-claude-opus-5-6c3c5c854e24?source=rss-3d20cd388733------2"><img src="https://cdn-images-1.medium.com/max/1397/1*b7MgYw0bg097g04g4uc7vg.png" width="1397"></a></p><p class="medium-feed-snippet">Hey ya&#x2019;ll haven&#x2019;t seen you in awhile. So this time I was bored, so I decided to test Claude&#x2019;s ability to identify an exact coordinate of a&#x2026;</p><p class="medium-feed-link"><a href="https://infosecwriteups.com/one-photo-one-prompt-exact-coordinates-claude-opus-5-6c3c5c854e24?source=rss-3d20cd388733------2">Continue reading on InfoSec Write-ups »</a></p></div>]]></description>
            <link>https://infosecwriteups.com/one-photo-one-prompt-exact-coordinates-claude-opus-5-6c3c5c854e24?source=rss-3d20cd388733------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c3c5c854e24</guid>
            <category><![CDATA[osint]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[threat-intelligence]]></category>
            <category><![CDATA[red-team]]></category>
            <dc:creator><![CDATA[popalltheshells]]></dc:creator>
            <pubDate>Wed, 29 Jul 2026 00:09:24 GMT</pubDate>
            <atom:updated>2026-08-10T08:58:44.362Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Simple (but time consuming) guide to hunt for DOM XSS without a scanner]]></title>
            <link>https://popalltheshells.medium.com/simple-but-time-consuming-guide-to-hunt-for-dom-xss-without-a-scanner-f5b65a262073?source=rss-3d20cd388733------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5b65a262073</guid>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[web-application-security]]></category>
            <category><![CDATA[xss-attack]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[popalltheshells]]></dc:creator>
            <pubDate>Wed, 22 Oct 2025 02:33:27 GMT</pubDate>
            <atom:updated>2025-10-22T02:35:18.751Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*JZ4RWk-GlOiY45IO.jpg" /></figure><p>As I continue my love-hate relationship with XSS, I am slowly but surely building a better understanding of more advanced XSS techniques. I have always known the basics of DOM XSS but never really dug deeper into it until recently. There are a lot of good XSS scanner tools out there such as XSSStrike, but running just tools is no fun unless you understand the underlying techniques they are using.</p><p>In this blog, I&#39;d like to share how you can find DOM XSS without tools — with just 8 hours of time to kill (lol).</p><p>First, we need to understand the basics. For an XSS vulnerability to be exploited, you need to have some sort of input source that you can control. Some common ones include:</p><pre>location.href, location.search, document.referrer, location.hash, etc.</pre><p>The second thing you need to be aware of is that for DOM XSS to exist, there must be a dangerous function or property that can execute HTML or JavaScript payloads. These are called <strong>“sinks.”</strong> You can think of some of the following:</p><pre>.innerHTML, document.write(), eval(), Function(), .action, etc.</pre><p><strong><em>DOM XSS only happens if YOUR source (input you control) reaches the sink.</em></strong></p><p>Finding your sink is pretty simple. Armed with a web browser and DevTools, you can start filtering for keywords such as the ones above. When you find multiple lines that contain those sinks, mark each one that may have dynamic data written to it.</p><p>The next step is to reverse-trace which data/source reaches the sink. For example, if you found something like this in your search:</p><pre>element.innerHTML = vulnVAR;</pre><p>We would need to ask ourselves, where does the vulnVar come from? CTRL+F for the win and identify if you can control the value of vulnVar. By searching the following value, you may be able to find the source of vulnVar and what value it is being assigned with:</p><pre>var someVar = </pre><p>As you navigate through the tedious lines of codes, keep notes if any of the source (location, referrer, user input, etc.) is used to assign the value of someVar. You need to also read how the values are assigned and see if any escaping or sanitization functions are implemented to secure the sink. If not, this could indicate a potential XSS avenue. Once you suspect that there is a source to sink flow, you can check for reflection.</p><p>Next we would have to check if your input characters are reflected in the browser. As an example, you supply an input to the search query of a site</p><pre>victim.com/search=11aa11</pre><p>Once the page is loaded, you can now open elements tab “F12” and search for your marker “11aa11” inside the DOM. If it is reflected, you will know that DOM XSS is most likely be there. The next thing for you to do is to develop a payload such as</p><pre>&lt;img src=x onerror=alert()&gt;</pre><p>If it renders, then DOM XSS is present in the application. Keep in mind this is a simple example, and for more advanced filtering/WAF in place you may need to implement some obfuscation/escape/cool techniques to get your payload to render. Sometimes you’ll see suspicious HTML, but it’s passed through a sanitizer first — which makes everything more complicated for us.</p><p>A few considerations when you are hunting:</p><ul><li><strong>Network traces</strong>: If you don’t find reflection in the DOM, go to Network tab, and search for your identifier “11aa11”. If you see any requests (GET or POST) containing 11aa11 in the <strong>URL, query string, request body, or headers</strong>, then the page sent your marker somewhere. Check its destination, if it is sent to a tracker — that just means it’s being sent for analytics, not reflected on the site itself.</li><li>WAF needs to be bypassed</li></ul><p>Summary checklist for your guidance to hunt for DOM XSS:</p><ul><li>Search for sinks (innerHTML, eval, etc.).</li><li>Trace back variable sources.</li><li>Inject markers in URL/hash/referrer.</li><li>Look for reflection in DOM.</li><li>Use breakpoints to inspect runtime data flow.</li><li>Test safe payloads.</li><li>Confirm JS execution.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5b65a262073" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Broken Access Control to XSS]]></title>
            <link>https://popalltheshells.medium.com/broken-access-control-to-xss-1c0b745bf5f7?source=rss-3d20cd388733------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c0b745bf5f7</guid>
            <dc:creator><![CDATA[popalltheshells]]></dc:creator>
            <pubDate>Mon, 15 Sep 2025 19:32:00 GMT</pubDate>
            <atom:updated>2025-09-15T19:32:00.290Z</atom:updated>
            <content:encoded><![CDATA[<p>While testing a web application, I found that as an admin, I could access the user management portal using a URL like:</p><pre>https://target.com/wps/&lt;redacted&gt;/S8ejksPUhsa…/?overlayUrl=&lt;redacted&gt;/Home/user</pre><p>Out of curiosity,<strong> I copied this same URL</strong> into a <strong>browser session </strong>as a low-privileged user. Surprisingly, it worked — the low-priv user could now access the user management interface. This included functionality like viewing and managing user access and permissions, which should have been restricted to admins only.</p><h3><strong>This revealed a clear access control issue</strong>:</h3><p>the application wasn’t validating the user’s role properly. Instead, it seemed to rely solely on the path or overlay in the URL to decide what to show.</p><p>I also noticed part of the URL looked like a Base64-encoded string. I tried removing that portion and used a simpler version:</p><pre>https://target.com/wps/&lt;redacted&gt;/?overlayUrl=&lt;redacted&gt;/Home/user</pre><p>That resulted in a path error. The page tried to load but failed, likely because the app was trying to resolve resources locally and the required path structure was no longer intact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/751/1*3p_g9svK9wxl4Vd2TA4-lA.png" /></figure><p>So the access control was effectively tied to a static URL pattern, not the user’s actual session or privilege level. That allowed a low-priv user to access admin-level features just by guessing the right URL.</p><p>While digging further, I remembered that some redirects can end up rendering JavaScript if not properly sanitized. I tested this by entering a simple payload:</p><pre>javascript:alert(document.cookie)</pre><p>It worked — the browser executed the XSS payload.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ueitwhHe3xEPgUS1V4qgSw.png" /></figure><p>This means you can craft a URL with the javascript: payload and send it to an admin user. If they click the link, their browser will run the script. In this case, it pops up their cookies, but it could just as easily be used to capture their session token.</p><p>With that token, it’s possible to impersonate the admin and access their privileges directly.</p><p>So this exposed a reflected XSS vulnerability via a redirect endpoint, which can be chained with the session access to escalate privileges.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c0b745bf5f7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[XSS Escape backticks (`) — Strings/Template literals]]></title>
            <link>https://infosecwriteups.com/xss-escape-backticks-strings-template-literals-92b3f31b37a8?source=rss-3d20cd388733------2</link>
            <guid isPermaLink="false">https://medium.com/p/92b3f31b37a8</guid>
            <category><![CDATA[xss-attack]]></category>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[popalltheshells]]></dc:creator>
            <pubDate>Sat, 16 Aug 2025 16:26:04 GMT</pubDate>
            <atom:updated>2025-08-16T16:53:47.715Z</atom:updated>
            <content:encoded><![CDATA[<h3>XSS Escape backticks (`) — Strings/Template literals</h3><p>I have been doing a lot of labs and reading resources to understand more about XSS and techniques that come with it. Recently I came across an old trick that you can know if you — have programmed in the past/read language documentations, played around with XSS payloads, or anything that relates to writing codes.</p><p>If you haven’t, this blog is hopefully useful to summarize on how you can potentially trigger an XSS when your payload is reflected and enclosed within backticks (`) and the common characters are escaped/encoded:</p><pre>&lt;,&gt;,&#39;,&quot;,\,/,;</pre><h3>Template Literal XSS</h3><p>Modern JavaScript introduced a pretty cool feature called <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals"><strong>template literals</strong> </a>— but when used without proper sanitization, they can be troublesome.</p><p>In this quick blog-note, we’ll break down:</p><ul><li>What template literals are</li><li>How ${} works</li><li>How attackers abuse them</li><li>A real payload</li></ul><p>Traditionally, JavaScript strings are wrapped in single (&#39;) or double (&quot;) quotes. Template literals use <strong>backticks</strong> instead to allow entries of multiple lines of strings:</p><pre>`<br>line 1<br>line2<br>line3<br>`</pre><p>If you ever come across something that reflects your input in backtick such as the following:</p><pre>var searchTerm = `PAYLOAD`;</pre><p>That is an indication that your payload will be contained within a template literal. Controlling the PAYLOAD, you can <strong>AVOID </strong>attempts of breaking out of the string context and execute JS directly using the following value:</p><pre>${alert(1)}</pre><p>Payload will be reflected as follow:</p><pre>var searchTerm = `${alert(1)}`;</pre><p>Once rendered, an XSS vulnerability will be triggered with your alert box.</p><p>The ${} syntax (<strong>string interpolation — </strong><a href="https://stackoverflow.com/questions/70243954/how-to-make-string-interpolation-in-javascript">https://stackoverflow.com/questions/70243954/how-to-make-string-interpolation-in-javascript</a>) lets you run <strong>real JavaScript code <em>inside</em> the string literal.</strong></p><p>Although the purpose of string interpolation inside template literal is commonly used to substitute <em>variables, </em>it can also evaluate JavaScript expressions such as:</p><pre>alert(1), prompt(), etc.</pre><p>A good lab to test how this all works:</p><p><a href="https://portswigger.net/web-security/cross-site-scripting/contexts/lab-javascript-template-literal-angle-brackets-single-double-quotes-backslash-backticks-escaped">Lab: Reflected XSS into a template literal with angle brackets, single, double quotes, backslash and backticks Unicode-escaped | Web Security Academy</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*ME5ufWTzGK4gyIb_mHd1uw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92b3f31b37a8" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/xss-escape-backticks-strings-template-literals-92b3f31b37a8">XSS Escape backticks (`) — Strings/Template literals</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ETW patching for EDR evasion (What is it?)]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://infosecwriteups.com/etw-patching-for-edr-evasion-what-is-it-1ca1bd9104c8?source=rss-3d20cd388733------2"><img src="https://cdn-images-1.medium.com/max/2000/0*nCIxi3b0nY1Y2qpz" width="2000"></a></p><p class="medium-feed-snippet">Holy cow it has been awhile since I last posted anything; mostly because of burn out. Burn out is mega real folks&#x200A;&#x2014;&#x200A;I&#x2019;m sure that&#x2019;s just&#x2026;</p><p class="medium-feed-link"><a href="https://infosecwriteups.com/etw-patching-for-edr-evasion-what-is-it-1ca1bd9104c8?source=rss-3d20cd388733------2">Continue reading on InfoSec Write-ups »</a></p></div>]]></description>
            <link>https://infosecwriteups.com/etw-patching-for-edr-evasion-what-is-it-1ca1bd9104c8?source=rss-3d20cd388733------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ca1bd9104c8</guid>
            <category><![CDATA[red-teamer]]></category>
            <category><![CDATA[pentest]]></category>
            <category><![CDATA[vulnerability-research]]></category>
            <category><![CDATA[pentester]]></category>
            <category><![CDATA[red-team]]></category>
            <dc:creator><![CDATA[popalltheshells]]></dc:creator>
            <pubDate>Tue, 22 Apr 2025 12:55:40 GMT</pubDate>
            <atom:updated>2025-04-22T12:55:40.648Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Tool Spotlight — Unveiling the Power of WebCopilot: An Automation Tool for Web App Recon]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://popalltheshells.medium.com/tool-spotlight-unveiling-the-power-of-webcopilot-an-automation-tool-for-web-app-recon-d99a90b29457?source=rss-3d20cd388733------2"><img src="https://cdn-images-1.medium.com/max/827/1*lxG0X9EaEp04KMQchO8n6w.png" width="827"></a></p><p class="medium-feed-snippet">Amidst this digital skirmish, reconnaissance plays a pivotal role, offering the initial glimpse into a target. WebCopilot, an ingenious&#x2026;</p><p class="medium-feed-link"><a href="https://popalltheshells.medium.com/tool-spotlight-unveiling-the-power-of-webcopilot-an-automation-tool-for-web-app-recon-d99a90b29457?source=rss-3d20cd388733------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://popalltheshells.medium.com/tool-spotlight-unveiling-the-power-of-webcopilot-an-automation-tool-for-web-app-recon-d99a90b29457?source=rss-3d20cd388733------2</link>
            <guid isPermaLink="false">https://medium.com/p/d99a90b29457</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[pentest]]></category>
            <dc:creator><![CDATA[popalltheshells]]></dc:creator>
            <pubDate>Sat, 23 Mar 2024 03:27:54 GMT</pubDate>
            <atom:updated>2024-03-23T03:27:54.337Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Payload Storage in Malware Development: Code Section]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://popalltheshells.medium.com/payload-storage-in-malware-development-code-section-6db3485ab9e1?source=rss-3d20cd388733------2"><img src="https://cdn-images-1.medium.com/max/1000/0*xR7RUZgH-Ib5sOM6" width="1000"></a></p><p class="medium-feed-snippet">In the complex world of malware development, one crucial aspect that often stumps even seasoned cybersecurity professionals is the optimal&#x2026;</p><p class="medium-feed-link"><a href="https://popalltheshells.medium.com/payload-storage-in-malware-development-code-section-6db3485ab9e1?source=rss-3d20cd388733------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://popalltheshells.medium.com/payload-storage-in-malware-development-code-section-6db3485ab9e1?source=rss-3d20cd388733------2</link>
            <guid isPermaLink="false">https://medium.com/p/6db3485ab9e1</guid>
            <category><![CDATA[stealth-techniques]]></category>
            <category><![CDATA[payload-storage]]></category>
            <category><![CDATA[malware-development]]></category>
            <category><![CDATA[windows-api]]></category>
            <category><![CDATA[executable-sections]]></category>
            <dc:creator><![CDATA[popalltheshells]]></dc:creator>
            <pubDate>Fri, 12 Jan 2024 15:38:44 GMT</pubDate>
            <atom:updated>2024-01-12T15:38:44.847Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Holistic Approach to Penetration Testing: Strengthening Your Client’s Cybersecurity Posture]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://popalltheshells.medium.com/the-holistic-approach-to-penetration-testing-strengthening-your-clients-cybersecurity-posture-fc3c3e6856f1?source=rss-3d20cd388733------2"><img src="https://cdn-images-1.medium.com/max/600/1*w7_oktnkZ3Kqfv1Rknw68w.png" width="600"></a></p><p class="medium-feed-snippet">Pentest and offensive security has been recognized as an essential addition for assessing an organization&#x2019;s vulnerabilities and security&#x2026;</p><p class="medium-feed-link"><a href="https://popalltheshells.medium.com/the-holistic-approach-to-penetration-testing-strengthening-your-clients-cybersecurity-posture-fc3c3e6856f1?source=rss-3d20cd388733------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://popalltheshells.medium.com/the-holistic-approach-to-penetration-testing-strengthening-your-clients-cybersecurity-posture-fc3c3e6856f1?source=rss-3d20cd388733------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc3c3e6856f1</guid>
            <category><![CDATA[penetration-test]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[data-privacy]]></category>
            <dc:creator><![CDATA[popalltheshells]]></dc:creator>
            <pubDate>Wed, 08 Nov 2023 02:31:51 GMT</pubDate>
            <atom:updated>2023-11-08T02:32:42.250Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Hunting 0days for a better world]]></title>
            <link>https://popalltheshells.medium.com/hunting-0days-for-a-better-world-7b25dafc70a0?source=rss-3d20cd388733------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b25dafc70a0</guid>
            <category><![CDATA[awareness]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[offensive-security]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <dc:creator><![CDATA[popalltheshells]]></dc:creator>
            <pubDate>Sun, 13 Aug 2023 12:11:16 GMT</pubDate>
            <atom:updated>2023-08-13T12:11:16.335Z</atom:updated>
            <content:encoded><![CDATA[<p>A zero-day vulnerability refers to a software security flaw that is exploited by hackers before the software’s creator becomes aware of it. Since developers have “zero days” to address or fix the issue, systems are left vulnerable. Attackers take advantage of this window to breach systems, steal data, or cause damage. Zero-day vulnerabilities often lead to targeted cyberattacks and can impact various software, including operating systems, applications, and browsers. They pose a significant threat as there’s no time for users or developers to apply patches or protective measures. Detecting and mitigating zero-day vulnerabilities requires constant monitoring, robust cybersecurity practices, and rapid response strategies.</p><p>The act of hunting for these vulnerabilities is not a nefarious endeavor; quite the opposite. These skilled individuals, often ethical hackers and cybersecurity researchers, embark on a journey to illuminate the dark corners of software systems. Their goal is to unveil weaknesses, not for personal gain, but to contribute to the greater good. By identifying vulnerabilities before malicious actors do, they enable developers to deploy patches and safeguards, fortifying the digital realm against potential threats.</p><p>The ripple effects of zero-day vulnerability hunting extend beyond the binary realm. It’s a contribution to the global community, a symphony of efforts that resonates in the intricate symmetries of the virtual universe. By sharing their discoveries with software vendors and organizations, these hunters pave the way for collaboration, ensuring that the software we rely on becomes more resilient and secure. It’s a collective endeavor to create an online ecosystem where individuals can transact, communicate, and create without constant fear of unseen threats.</p><p>My favourite way to start 0day hunting is by exploring the never-ending repositories of open-source projects that talented developers have developed, some are heavily adopted by well known organizations. That’s why I encourage every single one of you to do it.</p><p>If you have any tricks and tips on how you hunt for one, the comment section is an open space for all hackers to share knowledge.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b25dafc70a0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>