Add Evilginx On-Premises Setup section #40
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add comprehensive guide for running Evilginx on client-owned infrastructure - Include Cloudflare → Caddy → Evilginx architecture with private networking - Provide practical configurations for Cloudflare firewall rules and Caddy setup - Cover OPSEC considerations for hybrid cloud/on-premises deployments - Update table of contents with new phishing setup option
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This PR adds a comprehensive guide for deploying Evilginx in on-premises environments while using cloud assets only for redirection.
Changes
Benefits
Testing
The configurations have been tested in real red team engagements and provide a robust foundation for on-premises Evilginx deployments.
More Info
https://dan1t0.com/2025/09/24/Working-with-Evilginx-on-Premises/