<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recon on AnkhCorp</title><link>https://ankhcorp.net/tags/recon/</link><description>Recent content in Recon on AnkhCorp</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 03 Oct 2026 17:59:47 -0300</lastBuildDate><atom:link href="https://ankhcorp.net/tags/recon/index.xml" rel="self" type="application/rss+xml"/><item><title>From Recon to Root: Chaining Exposures in a Web Pentest</title><link>https://ankhcorp.net/journal/recon-to-root/</link><pubDate>Fri, 02 Oct 2026 00:00:00 +0000</pubDate><guid>https://ankhcorp.net/journal/recon-to-root/</guid><description>Exploitation Context During a web penetration test, I initiated the reconnaissance phase using a custom script that was already part of my toolkit.
Prior to the test, I had enhanced the script by adding new intelligence sources and integrations to expand its asset discovery capabilities.
It was during this phase that one of the investigation&amp;rsquo;s most interesting findings emerged.
Reconnaissance Phase The first step was to run the reconnaissance script against the client&amp;rsquo;s environment.</description></item></channel></rss>