hunt-cache-poison is a skill for Claude covering cache poisoning and web cache deception against CDN-fronted applications: unkeyed header injection such as X-Forwarded-Host, path-suffix tricks that get an authenticated page cached as a static asset, CDN allowlist gaps, and hop-by-hop header smuggling that lands a poisoned response at the edge. It separates this skill’s scope from hunt-host-header, which owns Host-header injection that reaches app logic without being cached.
The skill maps cache infrastructure signals, a ten-step method for finding unkeyed inputs and proving they are stored and served to other visitors, bypass techniques against WAF-blocked poison headers, and a blast-radius assessment. It names the public research behind each technique, including Omer Gil’s original web cache deception write-up and James Kettle’s 2024 path-normalization research, and cites ten disclosed cases from 2017 to 2024. It is for assets covered by a program or engagement you are authorized to test.
What You Get
- A ten-step method covering cache-infrastructure mapping, unkeyed-header discovery, path-suffix web cache deception, DoS-via-cached-error testing, and blast-radius measurement
- Request patterns for confirming caching behavior, forcing a cache miss for safe testing, and verifying a poisoned entry from a second client
- A defense-to-bypass table covering WAF header-blocking, origin header stripping, and short-TTL cache purging
- A three-question validation gate that requires the poisoned response to be reproduced from a separate client before it counts as a finding
- Ten disclosed report citations from 2017 to 2024, including the original Omer Gil web cache deception write-up and James Kettle’s path-normalization research
Common Use Cases
- Testing whether an unkeyed header like X-Forwarded-Host is reflected into a cached response on a CDN-fronted application
- Checking whether appending a static file extension to an authenticated URL gets the full authenticated page cached and served to other visitors
- Confirming whether a cached error response from a malformed header can deny service to legitimate users of a CDN-served asset
What Makes It Unique
The skill separates poisoning from deception explicitly and draws the boundary against the adjacent hunt-host-header skill, so the same Host-header injection technique is not reported twice under two different names. Its validation gate requires a second, unmodified request from a separate client or IP to show the poisoned response persisting in the cache, ruling out a self-cache that only the attacker’s own browser sees.
Under The Hood
The skill is a single SKILL.md of guidance with no bundled scripts. Following it, the agent sends HTTP requests with manipulated headers such as X-Forwarded-Host and crafted URL paths to cacheable endpoints, inspects response headers for cache-hit signals, and issues a follow-up request from a different context to confirm persistence. Use it only against assets you are authorized to test.