FlareProx Deploy Cloudflare Worker pass-through proxies for ... #222
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
🎯 Content Summary
Overview
FlareProx is a Python tool that auto-deploys Cloudflare Workers to act as HTTP pass-through proxies, providing simple IP masking and endpoint rotation (similar in spirit to FireProx). It supports all HTTP methods and lets you specify the upstream target via a query parameter or custom header. Because traffic egresses from Cloudflare’s network, the target sees Cloudflare IPs rather than the tester’s. Cloudflare’s free tier allows ~100,000 requests/day.
How it works...
🔧 Technical Details
Cloudflare Worker pass-through proxying: Host a Worker that reads an upstream from either
?url=orX-Target-URL, then forwards the original method/headers/body to that upstream and relays the response. Targets observe Cloudflare egress IPs, enabling authorized testing without exposing your origin IP.Simple operational rotation: Create multiple Worker endpoints (e.g.,
flareprox.py create --count N) and randomly select one per request to distribute traffic and reduce basic IP/heuristic blocking. Validate endpoints withflareprox.py testand remove them withflareprox.py cleanup.Tooling drop-in: Replace the target in scanners/proxies (e.g., Burp) with the Worker URL and convey the real destination via
?url=orX-Target-URL, preserving HTTP semantics while masking your source IP.🤖 Agent Actions
I analyzed the repository and existing Cloudflare coverage and found no content describing the FireProx-style abuse of Cloudflare Workers as pass-through proxies for IP rotation. The current Cloudflare section only includes security review checklists and general advice, so adding a dedicated technical page about this technique is appropriate.
What I added
New page: Abusing Cloudflare Workers as pass-through proxies (IP rotation, FireProx-style)
Cross-link from Cloudflare Security main page:
Files created/modified
References used
No other related pages existed that covered this technique, so a new page under Cloudflare Security was the best fit and is now linked from the Cloudflare Workers section.
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.
📚 Repository Maintenance
All .md files have been checked for proper formatting (headers, includes, etc.).
🗑️ File Cleanup