<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Home on Sicksec</title><link>https://blog.sicks3c.io/</link><description>Recent content in Home on Sicksec</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Sicksec</copyright><lastBuildDate>Sat, 24 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.sicks3c.io/index.xml" rel="self" type="application/rss+xml"/><item><title>Hunting Account Takeovers in the Wild West of MCP OAuth Servers</title><link>https://blog.sicks3c.io/research/ato-via-open-mcp-dcr/</link><pubDate>Sat, 24 Jan 2026 00:00:00 +0000</pubDate><guid>https://blog.sicks3c.io/research/ato-via-open-mcp-dcr/</guid><description>&lt;p>&lt;strong>TL;DR:&lt;/strong> We discovered that many MCP (Model Context Protocol) servers powering AI integrations like ChatGPT and Claude have critically misconfigured OAuth implementations. Open Dynamic Client Registration (DCR) combined with missing redirect URI validation and optional PKCE enforcement creates a perfect storm for one-click account takeover attacks.&lt;/p>
&lt;hr>
&lt;h2 id="whats-an-mcp-server-anyway">What&amp;rsquo;s an MCP Server Anyway?&lt;a class="heading-anchor" href="#whats-an-mcp-server-anyway" aria-label="Link to What’s an MCP Server Anyway?">#&lt;/a>&lt;/h2>
&lt;p>If you&amp;rsquo;ve been following the AI ecosystem lately, you&amp;rsquo;ve probably noticed something interesting: AI assistants are getting &lt;em>connected&lt;/em>. They can now deploy your code, manage your cloud infrastructure, send emails—basically act as your digital butler.&lt;/p></description></item><item><title>Abusing URL Shorteners for Fun and Profit</title><link>https://blog.sicks3c.io/research/abusing-url-shortners-for-fun-and-profit/</link><pubDate>Wed, 26 Feb 2025 07:32:53 +0800</pubDate><guid>https://blog.sicks3c.io/research/abusing-url-shortners-for-fun-and-profit/</guid><description>&lt;p>&lt;strong>Hello Security Researchers&lt;/strong>&lt;/p>
&lt;p>Have you ever encountered a bug where it’s hard to show impact due to the lack of enumeration of a certain value of a parameter ?
Well if yes, In this writeup I will talk about how you can find and abuse URL shortners to ATO or Information disclosure&lt;/p>
&lt;p>Many companies use URL shortners to send private invite and passwordless logins and things along those lines and it’s really difficult to guess or to brute these but there’s always a way to do things by thinking outside the box 📦&lt;/p></description></item><item><title>How I Scored $2K via an Easy IDOR</title><link>https://blog.sicks3c.io/posts/how-i-scored-2k-bounty-via-an-idor/</link><pubDate>Wed, 26 Feb 2025 07:32:53 +0800</pubDate><guid>https://blog.sicks3c.io/posts/how-i-scored-2k-bounty-via-an-idor/</guid><description>&lt;p>&lt;strong>Hello Security Researchers&lt;/strong>&lt;/p>
&lt;p>In this writeup I will talk how I was able to find an IDOR in one of the largest Russian Company nothing other than Mail.ru
So approaching targets with huge scope can be frustrating sometimes since you don’t know where to start, For me I started looking in the main scope of &lt;code>Mail.ru Games&lt;/code>&lt;/p>
&lt;ol>
&lt;li>I fired up Burp&lt;/li>
&lt;li>Created an account&lt;/li>
&lt;li>Adding things in my cart&lt;/li>
&lt;li>Viewing the &lt;code>blog&lt;/code>&lt;/li>
&lt;li>Creating a support ticket&lt;/li>
&lt;/ol>
&lt;p>Before testing anything the ticket link looked kind of suspicious since it had &lt;code>/ticket/INTEGER&lt;/code>&lt;/p></description></item><item><title>Account Takeover via an Unsanitized Facebook OAuth Redirect Scheme</title><link>https://blog.sicks3c.io/research/ato-via-facebook-oauth-due-unsanitized-schema-allows-to-steal-oauth-token/</link><pubDate>Fri, 01 Sep 2023 07:32:53 +0800</pubDate><guid>https://blog.sicks3c.io/research/ato-via-facebook-oauth-due-unsanitized-schema-allows-to-steal-oauth-token/</guid><description>&lt;h1 id="deep-dive-into-an-oauth-exploit-a-0-day-case-study">Deep Dive into an OAuth Exploit: A 0-Day Case Study&lt;a class="heading-anchor" href="#deep-dive-into-an-oauth-exploit-a-0-day-case-study" aria-label="Link to Deep Dive into an OAuth Exploit: A 0-Day Case Study">#&lt;/a>&lt;/h1>
&lt;p>&lt;strong>Hello Everyone,&lt;/strong>&lt;/p>
&lt;p>In our continuous hunt for novel attack vectors and security challenges, &lt;a href="https://x.com/wld_basha" target="_blank" rel="noreferrer">&lt;strong>mainteemoforfun&lt;/strong>&lt;/a> and I embarked on an in-depth exploration of &lt;strong>mobile authentication mechanisms&lt;/strong>. Our efforts culminated in the discovery of a striking &lt;strong>0-day vulnerability&lt;/strong> back in &lt;strong>2023&lt;/strong> that has since been patched.&lt;/p>
&lt;p>This vulnerability enabled us to potentially hijack user sessions on websites utilizing &lt;strong>Facebook’s “Login With Facebook”&lt;/strong> feature. By manipulating the &lt;strong>&lt;code>redirect_uri&lt;/code>&lt;/strong> parameter in the &lt;strong>OAuth&lt;/strong> flow, an attacker could redirect authentication tokens to a host under their control.&lt;/p></description></item><item><title>How I RCE'd the Largest RU Company</title><link>https://blog.sicks3c.io/posts/how-i-got-rce-in-the-world-largest-russian-company/</link><pubDate>Thu, 19 Aug 2021 07:32:53 +0800</pubDate><guid>https://blog.sicks3c.io/posts/how-i-got-rce-in-the-world-largest-russian-company/</guid><description>&lt;p>&lt;strong>Hello Security Researchers&lt;/strong>&lt;/p>
&lt;p>In this writeup I will explain how I was able to find RCE in &lt;code>Mail.ru&lt;/code> which is considered the world largest internet company,
Before starting to hack I was wondering on how I should approach the target and what most people would miss in the program, they have a huge scope which means it should be something out there sitting for me to find&lt;/p>
&lt;p>I started looking with the Favicon using this &lt;a href="https://gist.github.com/yehgdotnet/b9dfc618108d2f05845c4d8e28c5fc6a" target="_blank" rel="noreferrer">script&lt;/a>
Where I replace the link with the Mail.ru favicon, once generate I go to shodan.io and search for it&lt;/p></description></item><item><title>How I Scored 1K Bounty Using Waybackurls</title><link>https://blog.sicks3c.io/posts/how-i-scored-1k-bounty-using-waybackurls/</link><pubDate>Tue, 03 Aug 2021 07:32:53 +0800</pubDate><guid>https://blog.sicks3c.io/posts/how-i-scored-1k-bounty-using-waybackurls/</guid><description>&lt;p>&lt;strong>Hello Security Researchers&lt;/strong>&lt;/p>
&lt;p>In this write-up, I want to share with you a finding that I discovered in a public bug bounty program that ended up paying me 1K just using a single command on the terminal&lt;/p>
&lt;p>I won’t be able to disclose the name of the program since the leak was huge and they are still merging all the previous algorithm they used before to a new one and the deprecated API is still reachable&lt;/p></description></item><item><title>Tale of XSS in Angular</title><link>https://blog.sicks3c.io/posts/tale-of-xss-in-angular/</link><pubDate>Sun, 01 Aug 2021 00:00:00 +0000</pubDate><guid>https://blog.sicks3c.io/posts/tale-of-xss-in-angular/</guid><description>&lt;p>&lt;figure class="article-figure">
 &lt;img src="https://cdn-images-1.medium.com/max/800/0*67LG7dce-XrL1Pdk" alt="Angular XSS Featured Image" loading="lazy" decoding="async">
 &lt;figcaption>Angular XSS Featured Image&lt;/figcaption>
&lt;/figure>
&lt;/p>
&lt;p>&lt;strong>Hello Security Researchers and Hackers&lt;/strong>&lt;/p>
&lt;p>In this writeup I explain how I found 2 rXSS vulnerabilities in Angular using automation.&lt;/p>
&lt;hr>
&lt;h2 id="tools-used">Tools Used&lt;a class="heading-anchor" href="#tools-used" aria-label="Link to Tools Used">#&lt;/a>&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://findomain.app/" target="_blank" rel="noreferrer">Findomain&lt;/a> for subdomain monitoring&lt;/li>
&lt;li>Wappalyzer for technology detection&lt;/li>
&lt;/ul>
&lt;hr>
&lt;h2 id="discovery-process">Discovery Process&lt;a class="heading-anchor" href="#discovery-process" aria-label="Link to Discovery Process">#&lt;/a>&lt;/h2>
&lt;ol>
&lt;li>
&lt;p>Received Telegram alert for new subdomains&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Identified Angular 1.6 using Wappalyzer&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Found reflected error parameter:&lt;/p>
&lt;p>&lt;code>https://redacted.com/Home/Error?error=USER_NOT_AUTHORIZED&lt;/code>&lt;/p>
&lt;/li>
&lt;/ol>
&lt;hr>
&lt;h2 id="exploitation">Exploitation&lt;a class="heading-anchor" href="#exploitation" aria-label="Link to Exploitation">#&lt;/a>&lt;/h2>
&lt;p>Used payload from &lt;a href="https://github.com/swisskyrepo/PayloadsAllTheThings" target="_blank" rel="noreferrer">PayloadsAllTheThings&lt;/a>:&lt;/p></description></item></channel></rss>