<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CTF Blogs on Anshik Singh</title><link>https://anshik.in/blogs/ctf/</link><description>Recent content in CTF Blogs on Anshik Singh</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 07 Oct 2026 12:00:00 +0530</lastBuildDate><atom:link href="https://anshik.in/blogs/ctf/index.xml" rel="self" type="application/rss+xml"/><item><title>How I Completed the FAM CTF Secret-Finder Bounty — From APK Strings to Cloud SSRF</title><link>https://anshik.in/blogs/ctf/fam-ctf-secret-finder/</link><pubDate>Wed, 07 Oct 2026 12:00:00 +0530</pubDate><guid>https://anshik.in/blogs/ctf/fam-ctf-secret-finder/</guid><description>This is how I solved the FAM CTF secret-finder bounty end to end — an Android APK (fam.apk, package com.ctf.fam) plus its backends: a Firebase project (fam-ctf), a web portal at ctf.fampay.co/famctf, and a public EC2 &amp;ldquo;NexOps&amp;rdquo; monitoring instance.
Total haul: 950+ pts across static (APK reversing) and dynamic (Firebase, web, cloud/AWS) tracks.
Tools I used: apktool (via a patched secret_finder.py), apkleaks (docker), strings / objdump / readelf for native reversing, curl for all HTTP/REST work, and boto3 for AWS SigV4 signing.</description></item></channel></rss>