You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 14, 2024. It is now read-only.
Matt Creel edited this page Apr 2, 2020
·
2 revisions
Basic flow of what redlure-workers do:
Receive HTTP POST data from redlure-console containing phishing campaign data (HTML, routes, payloads, etc)
Write Flask app to campaigns/<id> and copy over static files from the UPLOAD_FOLDER
Start the phishing site (flask app) using gunicorn3
Send HTTP POST data to the redlure-console as opens/clicks/downloads/submissions are received
When the console communicates to stop the campaign, kill the process bound to the campaign's port and delete template data from disk
All redlure-worker API routes require the API key specified in config.py to be provided and all data returned to the console will be sent along with the API key.