support for HTTPS -> HTTP, HTTP -> HTTP, new phishlet property (http_mode)#1202
Open
jfmaes wants to merge 7 commits into
Open
support for HTTPS -> HTTP, HTTP -> HTTP, new phishlet property (http_mode)#1202jfmaes wants to merge 7 commits into
jfmaes wants to merge 7 commits into
Conversation
Features: - Phishlets can now specify orig_scheme: 'http' or 'https' for proxy_hosts - New http_mode setting per phishlet for HTTP-only phishing server (no TLS) - New http_port config option (default: 80) for HTTP listener - Commands: phishlets http_mode <name> on/off, config http_port <port> - Added example-http.yaml with HTTP support documentation Use cases: - http://phishing.example.com proxying to http://target.com (http_mode on) - https://phishing.example.com proxying to http://target.com (orig_scheme: http) https://claude.ai/code/session_01AyqENqDW9PrAhnC74EF1QJ
- Fixed lure get-url to use correct scheme based on http_mode setting - Improved example-http.yaml with clearer documentation and usage examples - Added step-by-step usage scenarios for internal awareness campaigns https://claude.ai/code/session_01AyqENqDW9PrAhnC74EF1QJ
Claude/add http support 7 e rxo
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
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.
Hey Mate
I had to use evilginx for a HTTP target. had to patch and figured I'd share.
Add HTTP Support for Security Awareness Campaigns
Summary
This PR adds comprehensive HTTP support to evilginx2, enabling security awareness campaigns and internal testing scenarios where TLS certificates are not required or available. This feature allows the phishing server to operate over plain HTTP and proxy to HTTP backend servers.
Changes
New Features
Phishing server can now listen on plain HTTP (no TLS required)
Configurable via phishlet YAML: http_mode: true
Configurable via CLI: phishlets http_mode on|off
HTTP port configurable: config http_port (default: 80)
Automatically applies when phishlet is enabled if set in YAML
HTTP Origin Targets (orig_scheme)
Proxy can connect to origin servers over HTTP instead of HTTPS
Set per proxy_host in phishlet YAML: orig_scheme: 'http'
Correctly routes requests to port 80 for HTTP origins
New Example Phishlet
Added phishlets/example-http.yaml demonstrating HTTP support
Includes comprehensive documentation and usage examples
Usage Examples
Scenario A: HTTP → HTTP (internal awareness campaign)
: phishlets hostname example-http phish.internal.lan
: phishlets enable example-http
: lures create example-http
: lures get-url 0
Result: http://phish.internal.lan/...
Scenario B: CLI-based HTTP mode
: phishlets hostname mysite attacker.com
: phishlets http_mode mysite on
: phishlets enable mysite
Phishlet YAML Configuration
🤖 Generated with Claude Code