Configure Evilginx on Ubuntu VM
Budget: ₹400 – ₹750 INR
I’m running an Ubuntu-based lab VM and want to get Evilginx fully operational, but port 80 refuses to come up. I have full root access over SSH, so you’ll be able to adjust firewall rules, tweak Nginx configs, or install any missing dependencies without hurdles.
Your task is to install and configure the latest stable Evilginx release so it listens correctly on both port 80 and 443, survives reboots, and is ready for me to start adding phishlets right away. If the issue lies with ufw, iptables, cloud security groups, or a conflicting service already bound to the port, please diagnose and resolve it as part of the job.
Deliverables
• Working Evilginx service reachable on my VM’s public IP over HTTP and HTTPS
• Clean, commented configuration files stored in /etc/evilginx and /etc/nginx (or equivalent)
• A brief log of the commands or scripts you used, so I can reproduce the setup in future
Acceptance criteria
• curl http://<server-ip> and https://<server-ip> both return the default Evilginx response
• systemctl reports both nginx and evilginx as active (running) after a reboot
• No unintended open ports or disabled services left behind
I’ll provide SSH credentials as soon as we agree to start. Let me know if you need any additional information about the VM or network.
Your task is to install and configure the latest stable Evilginx release so it listens correctly on both port 80 and 443, survives reboots, and is ready for me to start adding phishlets right away. If the issue lies with ufw, iptables, cloud security groups, or a conflicting service already bound to the port, please diagnose and resolve it as part of the job.
Deliverables
• Working Evilginx service reachable on my VM’s public IP over HTTP and HTTPS
• Clean, commented configuration files stored in /etc/evilginx and /etc/nginx (or equivalent)
• A brief log of the commands or scripts you used, so I can reproduce the setup in future
Acceptance criteria
• curl http://<server-ip> and https://<server-ip> both return the default Evilginx response
• systemctl reports both nginx and evilginx as active (running) after a reboot
• No unintended open ports or disabled services left behind
I’ll provide SSH credentials as soon as we agree to start. Let me know if you need any additional information about the VM or network.
Related categories:
System Admin
Linux
Apache
Ubuntu
Scripting
Cloud Security
Network Security
System Administration