<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Aadarsh Anand (ScreaMy7)</title><description>Security researcher focused on Android, native code and fuzzing. Research, writeups and tools by Aadarsh Anand (ScreaMy7).</description><link>https://screamy7.github.io/</link><item><title>An AI agent in the fuzzing loop: re-finding CVE-2017-11729 in libming</title><link>https://screamy7.github.io/blog/cve-2017-11729-libming-swftophp/</link><guid isPermaLink="true">https://screamy7.github.io/blog/cve-2017-11729-libming-swftophp/</guid><description>Re-finding CVE-2017-11729, a heap over-read in libming&apos;s SWF decompiler, with an AI coding agent running the fuzzing. Here&apos;s where it tried to lie to me.</description><pubDate>Sat, 03 Oct 2026 00:00:00 GMT</pubDate><category>Blog</category><category>fuzzing</category><category>cve</category><category>libming</category><category>afl</category><category>llm</category><category>security-research</category></item><item><title>Check reachability before you fuzz for a CVE</title><link>https://screamy7.github.io/notes/check-reachability-before-fuzzing-a-cve/</link><guid isPermaLink="true">https://screamy7.github.io/notes/check-reachability-before-fuzzing-a-cve/</guid><description>When I pick a known CVE to re-find by fuzzing, the question that matters isn&apos;t how bad the bug is or who found it. It&apos;s how many conditions a fuzzer has…</description><pubDate>Sat, 03 Oct 2026 00:00:00 GMT</pubDate><category>Note</category><category>fuzzing</category><category>cve</category><category>llm</category></item><item><title>herdr + omp: my terminal setup for agent-driven security work</title><link>https://screamy7.github.io/notes/herdr-and-omp-agent-setup/</link><guid isPermaLink="true">https://screamy7.github.io/notes/herdr-and-omp-agent-setup/</guid><description>Two tools do most of my agent work now. omp (oh my pi, a fork of Mario Zechner&apos;s Pi) is the coding agent. herdr is the terminal it lives in. They solve…</description><pubDate>Sat, 03 Oct 2026 00:00:00 GMT</pubDate><category>Note</category><category>llm</category><category>agents</category><category>workflow</category><category>fuzzing</category></item><item><title>JS file enumeration, four years later: recon with LLMs</title><link>https://screamy7.github.io/blog/js-file-enumeration-four-years-later/</link><guid isPermaLink="true">https://screamy7.github.io/blog/js-file-enumeration-four-years-later/</guid><description>Follow-up to my 2022 post: how to collect an SPA&apos;s JavaScript, cut it down, and let an LLM read it without burning tokens or trusting a word it says.</description><pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate><category>Blog</category><category>bug-bounty</category><category>javascript</category><category>llm</category><category>recon</category></item><item><title>JS file enumeration for bug bounty hunters</title><link>https://screamy7.github.io/blog/js-file-enumeration-for-bug-bounty-hunters/</link><guid isPermaLink="true">https://screamy7.github.io/blog/js-file-enumeration-for-bug-bounty-hunters/</guid><description>Why reading JavaScript files pays off in bug bounty, my workflow for collecting and inspecting them, and two findings that came out of it.</description><pubDate>Thu, 03 Mar 2022 00:00:00 GMT</pubDate><category>Blog</category><category>bug-bounty</category><category>javascript</category><category>recon</category></item></channel></rss>