Skip to content
This repository has been archived by the owner on Feb 14, 2024. It is now read-only.

Process Flow

Matt Creel edited this page Apr 2, 2020 · 2 revisions

Basic flow of what redlure-workers do:

  1. Receive HTTP POST data from redlure-console containing phishing campaign data (HTML, routes, payloads, etc)
  2. Write Flask app to campaigns/<id> and copy over static files from the UPLOAD_FOLDER
  3. Start the phishing site (flask app) using gunicorn3
  4. Send HTTP POST data to the redlure-console as opens/clicks/downloads/submissions are received
  5. 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.

Clone this wiki locally