A stealthy TCP-over-CDN tunnel that keeps your connections cozy and comfortable behind Cloudflare's welcoming embrace.
DarkFlare is a clever little tool that disguises your TCP traffic as innocent HTTPS requests, letting them pass through corporate firewalls like a VIP at a nightclub. It's like a tunnel, but with more style and less dirt.
It has two parts: a client-side proxy (darkflare-client) that encodes TCP data into HTTPS requests and sends it to a Cloudflare-protected domain, and a server-side proxy (darkflare-server) that decodes the requests and forwards the data to a local service (like SSH on port 22). It’s protocol-agnostic, secure, and uses Cloudflare's encrypted infrastructure, making it stealthy and scalable for accessing internal resources or bypassing network restrictions.
When using this remember the traffic over the tunnel is only as secure as the Cloudflare protection. Use your own encryption.
Services like Cloudflare, Akamai Technologies, Fastly, and Amazon CloudFront are not only widely accessible but also integral to the global internet infrastructure. In regions with restrictive networks, alternatives such as CDNetworks in Russia, ArvanCloud in Iran, or ChinaCache in China may serve as viable proxies. These CDNs support millions of websites across critical sectors, including government and healthcare, making them indispensable. Blocking them risks significant collateral damage, which inadvertently makes them reliable pathways for bypassing restrictions.
Internet censorship is a significant issue in many countries, where governments restrict access to information by blocking websites and services. For instance, China employs the "Great Firewall" to block platforms like Facebook and Twitter, while Iran restricts access to social media and messaging apps. In Russia, authorities have intensified efforts to control information flow by blocking virtual private networks (VPNs) and other tools that citizens use to bypass censorship.
AP NEWS In such environments, a tool that tunnels TCP traffic over HTTP(S) through a Content Delivery Network (CDN) like Cloudflare can be invaluable. By disguising restricted traffic as regular web traffic, this method can effectively circumvent censorship measures, granting users access to blocked content and preserving the free flow of information.
FIREWALL/CENSORSHIP
| | | |
v v v v
[Client]──────┐ ┌──────────────────┐ ┌─────────[Target Service]
│ │ │ │ (e.g., SSH Server)
│ │ CLOUDFLARE │ │tcp localhost:22
│tcp │ NETWORK │ │
[darkflare │ │ │ │ [darkflare
client]──────┼───HTTPS───────>│ (looks like │─-HTTPS-───────>│ server]
localhost:2222│ │ normal traffic) │ │ :8080
│ │ │ │
└────────────────┼──────────────────┼────────────────┘
│ │
└──────────────────┘
Flow:
1. TCP traffic ──> darkflare-client
2. Wrapped as HTTPS ──> Cloudflare CDN
3. Forwarded to ──> darkflare-server
4. Unwrapped back to TCP ──> Target Service
ssh, rdp, or anything tcp to bypass restrictive firewalls or state controled internet.
Tunneling ppp or other vpn services that leverage TCP.
darkflare-server can launch applications like sshd or pppd. Note that there are issues with host keys and certificate validation on sshd if you don't configure it properly.
Linux's popular pppd daemon will also not run as non-root in some cases, which would require a more complex configuration with sudo.
Breaking past blocked sites!
- Download the OpenVPN client
- Under Manual setup in your NordVPN account download the .ovpn file for TCP
- Also in Manual setup select username and password authentication.
- Edit the .ovpn file and change the IP and port to your darkflare server IP and Port.
- Configure darkflare-server to use the IP and port defined in the .ovpn file.
- Import the .ovpn file to OpenVPN and setup your username and password.
Note: OpenVPN does some weird thing with the default gateway/route. For testing purposes I added: pull-filter ignore "redirect-gateway" to the .ovpn file. That allows me to force the tunnel to not eat my network.
Latency over VPN and TCPoCDN was shockly low, around 100ms.
Requests are randomized to look like normal web traffic with jpg, php, etc... with random file names.
Client and server headers are set to look like normal web traffic.
If you have other ideas please send them my way.
Add your new proxy hostname into a free Cloudflare account.
Setup your origin rules to send that host to the origin server (darkflare-server) via the proxy port you choose.
I used 8080 with a Cloudflare proxy via HTTP for the firs test. Less overhead.
- Sneaky TCP Tunneling: Wraps your TCP connections in a fashionable HTTPS outfit
- Cloudflare Integration: Because who doesn't want their traffic to look like it's just visiting Cloudflare?
- Debug Mode: For when things go wrong and you need to know why (spoiler: it's always DNS)
- Session Management: Keeps your connections organized like a Type A personality
- TLS Security: Because we're sneaky, not reckless
- Download the latest release from the releases page or binary from the main branch.
- Extract the binaries to your preferred location
- Make the binaries executable:
chmod +x darkflare-client darkflare-server./darkflare-client -l 2222 -t https://host.domain.net:443 Add -debug flag for debug mode
Make the host.domain.net you use is configured in Cloudflare to point to the darkflare-server. If you want to debug and go directly to the psudo server you can use the -allow-direct flag on the server.
# HTTPS Server (recommended for production)
./darkflare-server -o https://0.0.0.0:443 -d localhost:22 -c /path/to/cert.pem -k /path/to/key.pem
# HTTP Server (for testing)
./darkflare-server -o http://0.0.0.0:8080 -d localhost:22- You must specify either
-d(network destination) or-a(application) mode, but not both - The
-allow-directflag allows direct connections without Cloudflare headers (not recommended for production) - Debug mode (
-debug) provides verbose logging of connections and data transfers - Under SSL/TLS configuration in Cloudflare you need to set ssl encryption mode to Full.
For HTTPS mode, you'll need to obtain origin certificates from Cloudflare:
- Log into your Cloudflare dashboard
- Go to SSL/TLS > Origin Server
- Create a new certificate (or use an existing one)
- Download both the certificate and private key
- When starting the server in HTTPS mode, provide both certificate files:
Note: Keep your private key secure and never share it. The certificate provided by Cloudflare is specifically for securing the connection between Cloudflare and your origin server.
ssh user@localhost -p 2222- Always use end-to-end encryption for sensitive traffic
- The tunnel itself provides obscurity, not security
- Monitor your Cloudflare logs for suspicious activity
- Regularly update both client and server components
This tool is for educational purposes only. Please don't use it to bypass your company's firewall - your IT department has enough headaches already.
Found a bug? Want to add a feature? PRs are welcome! Just remember:
- Keep it clean
- Keep it clever
- Intel (AMD64):
- Apple Silicon (ARM64):
# Download the checksums file
curl -O https://raw.githubusercontent.com/blyon/darkflare/main/bin/checksums.txt
# Verify downloads on Linux/macOS
shasum -a 256 -c checksums.txt
# Verify downloads on Windows PowerShell
Get-FileHash .\darkflare-client-windows-amd64.exe | Format-ListNote: All binaries are built automatically from the main branch. The checksums file is generated during the build process to ensure file integrity.
MIT License - Because sharing is caring, but attribution is nice.
Built with ❤️ and a healthy dose of mischief
