<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>API Security on </title>
    <link>https://n9o.xyz/tags/api-security/</link>
    <description>Recent content in API Security on </description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© 2026 Vaishnav Baraskar</copyright>
    <lastBuildDate>Sun, 18 May 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://n9o.xyz/tags/api-security/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>APISEC-CON CTF – Exception Excavation &amp; Render Bender</title>
      <link>https://n9o.xyz/capturetheflag/apisec/</link>
      <pubDate>Sun, 18 May 2025 00:00:00 +0000</pubDate>
      
      <guid>https://n9o.xyz/capturetheflag/apisec/</guid>
      <description>&lt;h2 class=&#34;relative group&#34;&gt;0x00 – The Setup 
    &lt;div id=&#34;0x00--the-setup&#34; class=&#34;anchor&#34;&gt;&lt;/div&gt;
    
    &lt;span
        class=&#34;absolute top-0 w-6 transition-opacity opacity-0 ltr:-left-6 rtl:-right-6 not-prose group-hover:opacity-100&#34;&gt;
        &lt;a class=&#34;group-hover:text-primary-300 dark:group-hover:text-neutral-700 !no-underline&#34; href=&#34;#0x00--the-setup&#34; aria-label=&#34;Anchor&#34;&gt;#&lt;/a&gt;
    &lt;/span&gt;        
    
&lt;/h2&gt;
&lt;p&gt;API challenges always make me pause. They&amp;rsquo;re subtle, often logic-based, and prone to mishandling by developers chasing &amp;ldquo;RESTful perfection.&amp;rdquo; When I saw two challenges dropped back-to-back—&lt;strong&gt;Exception Excavation&lt;/strong&gt; and &lt;strong&gt;Render Bender&lt;/strong&gt;—I knew there was potential for mischief.&lt;/p&gt;</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://n9o.xyz/capturetheflag/apisec/feature.gif" />
    </item>
    
    <item>
      <title>Coffee, Curiosity &amp; an API – JWT &#39;alg:none&#39; Exploit in HealthTrack</title>
      <link>https://n9o.xyz/bugbounty/healthtrack/</link>
      <pubDate>Mon, 19 Feb 2024 00:00:00 +0000</pubDate>
      
      <guid>https://n9o.xyz/bugbounty/healthtrack/</guid>
      <description>&lt;h1 class=&#34;relative group&#34;&gt;&lt;strong&gt;Prologue: Coffee, Curiosity &amp;amp; an API&lt;/strong&gt; 
    &lt;div id=&#34;prologue-coffee-curiosity--an-api&#34; class=&#34;anchor&#34;&gt;&lt;/div&gt;
    
    &lt;span
        class=&#34;absolute top-0 w-6 transition-opacity opacity-0 ltr:-left-6 rtl:-right-6 not-prose group-hover:opacity-100&#34;&gt;
        &lt;a class=&#34;group-hover:text-primary-300 dark:group-hover:text-neutral-700 !no-underline&#34; href=&#34;#prologue-coffee-curiosity--an-api&#34; aria-label=&#34;Anchor&#34;&gt;#&lt;/a&gt;
    &lt;/span&gt;        
    
&lt;/h1&gt;
&lt;p&gt;It was one of those quiet February evenings. No caffeine left in the mug, but my curiosity was wide awake. The glow from the screen illuminated my desk, casting a soft digital haze. I was drifting through recon mode—scrolling API docs, poking endpoints, intercepting calls like I was casually flipping through a dusty book in a forgotten archive.&lt;/p&gt;</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://n9o.xyz/bugbounty/healthtrack/feature.jpg" />
    </item>
    
    <item>
      <title>Broken Authentication: Uncovering Twitter&#39;s OAuth Vulnerability</title>
      <link>https://n9o.xyz/bugbounty/twitter/</link>
      <pubDate>Fri, 07 Apr 2023 00:00:00 +0000</pubDate>
      
      <guid>https://n9o.xyz/bugbounty/twitter/</guid>
      <description>A technical deep dive into an authentication vulnerability in Twitter&amp;rsquo;s legacy API that allowed bypassing signature validation, exposing user data through inconsistent OAuth enforcement.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://n9o.xyz/bugbounty/twitter/feature.png" />
    </item>
    
  </channel>
</rss>
