Hashcat is one of the fastest password-recovery tools around, and it runs well on Parrot Linux once your GPU drivers and OpenCL stack are in order. This guide walks you through a clean hashcat Parrot Linux setup: installing the tool, getting your GPU recognised, running a benchmark, and cracking your first hash. Everything here is meant for authorized testing only — your own password hashes, lab machines, or practice files you created yourself. Never run hashcat against credentials you do not own.
What hashcat does and why the GPU matters
Hashcat takes a hash (a one-way fingerprint of a password) and tries to find the plaintext that produces it, either by guessing from a wordlist or by brute force. The actual guessing is a huge number of tiny, repetitive calculations — exactly the kind of work a GPU handles far better than a CPU. A modern graphics card can test millions to billions of candidates per second depending on the hash type, while a CPU limps along by comparison. That is why the first real task on Parrot Linux is not installing hashcat (it is already packaged) but making sure the GPU is visible to it.
Hashcat can also run in CPU-only mode. If you are on a laptop without a discrete GPU, or inside a virtual machine, CPU mode still works for learning — it is simply slower. For CTF practice and weak test hashes, CPU mode is often enough.
Install hashcat on Parrot Linux
Parrot Linux ships hashcat in its repositories, so installation is a single command. Update your package lists first:
sudo apt update
sudo apt install hashcatConfirm the version and that the binary runs:
hashcat --versionIf you want the newest release instead of the packaged one, you can download the binaries from the official hashcat site and run them from a folder in your home directory. For most users the repository build is fine and gets security updates through the normal parrot-upgrade process.
Set up GPU drivers and OpenCL
Hashcat talks to your GPU through a compute runtime — OpenCL, and on NVIDIA cards also CUDA. Which packages you need depends on your hardware.
NVIDIA GPUs
Install the proprietary NVIDIA driver and the OpenCL runtime. On Parrot Linux the cleanest path is the packaged driver plus the ICD (installable client driver):
sudo apt install nvidia-driver nvidia-opencl-icd
sudo rebootAfter rebooting, check the driver loaded:
nvidia-smiIf this prints a table with your card, driver version and memory, the driver is active. For card-specific details and Secure Boot notes, follow the project’s own driver documentation rather than guessing package names.
AMD and Intel GPUs
AMD and Intel rely on the Mesa OpenCL stack or the vendor ICD. A reasonable starting point:
sudo apt install mesa-opencl-icd clinfo
sudo apt install intel-opencl-icd # Intel integrated graphicsThe clinfo tool reports every OpenCL device your system can see — run it to confirm your GPU shows up before you expect hashcat to use it.
Verify hashcat sees your hardware
Ask hashcat to list its compute devices:
hashcat -IYou want to see your GPU listed as an active device, not just the CPU. If only the CPU appears, the OpenCL runtime for your card is missing or the driver did not load — go back to the driver step and re-check clinfo. A common cause on fresh installs is skipping the reboot after installing the NVIDIA driver.
Run your first benchmark
The benchmark mode measures raw speed per hash algorithm without needing any target. It is the quickest way to confirm the whole stack works end to end:
hashcat -b -m 0Here -b means benchmark and -m 0 selects MD5 (mode 0). You will get a hashes-per-second figure for your device. To benchmark every supported algorithm at once, drop the -m flag and just run hashcat -b, though that takes much longer.
The exact numbers depend entirely on your card, so there is no “correct” figure to compare against — treat your own first run as the baseline and watch how it changes if you later tune settings or update drivers.
Crack your first hash (lab only)
Create a hash you own so there is no question of authorization. Generate an MD5 of a word you choose:
echo -n "parrot123" | md5sumSave the resulting hash (the long hex string, without the trailing filename) into a file called test.hash. Then run a dictionary attack against it. Parrot Linux includes the classic rockyou wordlist; on many installs it is compressed, so expand it once:
sudo gunzip /usr/share/wordlists/rockyou.txt.gz # if still gzipped
hashcat -m 0 -a 0 test.hash /usr/share/wordlists/rockyou.txtThe flags break down as: -m 0 MD5, -a 0 straight (dictionary) attack mode, then your hash file and the wordlist. When hashcat finds the plaintext it prints it next to the hash and marks the job cracked. Re-running the same job later shows the result instantly because hashcat stores cracked hashes in its potfile; add --show to just display what is already cracked.
Common attack modes and when to use them
| Flag | Attack mode | Use it when |
|---|---|---|
-a 0 | Straight / dictionary | You have a wordlist of likely passwords |
-a 1 | Combinator | Joining two wordlists into longer candidates |
-a 3 | Brute force / mask | You know the length or character pattern |
-a 6 / -a 7 | Hybrid | Wordlist plus a brute-forced suffix or prefix |
A mask attack is worth learning early. To try every 6-character lowercase-plus-digit password you would use a mask like ?l?l?l?l?l?d, where ?l is a lowercase letter and ?d a digit. Masks let you brute force intelligently instead of blindly, which matters because brute force time grows explosively with length.
Identify the hash type first
Every algorithm has its own -m mode number, and picking the wrong one means hashcat will never find a match. If you are unsure what you are looking at, two things help. First, hashcat’s own reference list: run hashcat --help and search the hash-type table for the format you have. Second, the shape of the hash is a strong clue — a 32-character hex string is usually MD5 (mode 0), a 40-character one is usually SHA-1 (mode 100), and strings that start with markers like $2y$ are bcrypt (mode 3200). When in doubt, test against a hash you generated yourself so you already know the answer, then apply the same mode to the real job.
Getting the mode right also sets realistic expectations for speed. Fast hashes like MD5 and SHA-1 fall quickly to a good wordlist, while deliberately slow hashes such as bcrypt and Argon2 are designed to resist exactly this kind of attack and may be impractical to crack at all. That is the point of a strong hashing scheme, and seeing the difference first-hand is one of the most useful lessons a beginner takes away from hashcat.
Keep your GPU healthy
Long cracking jobs push a GPU hard. Watch temperatures with nvidia-smi (NVIDIA) or sensors from the lm-sensors package, and stop a job if the card runs hot in a poorly ventilated case. Hashcat has a built-in thermal guard that aborts above a threshold, but good airflow is the real fix. If your machine locks up during heavy jobs, it is almost always a driver or power issue, not hashcat itself.
Where to go next
Once hashcat runs cleanly, the natural next step is practising in a safe environment. Spin up a target in your home pentesting lab and capture hashes you are allowed to crack, or feed hashcat material from a CTF box. If your GPU is not detected at all, the problem is usually the driver layer — review the steps in our guide to fixing hardware and driver issues on Parrot Linux for the same diagnostic mindset, and confirm the basics with a safe system update before blaming the tool. For the official OpenCL packaging notes, the OpenCL install documentation covers edge cases per vendor.
FAQ
Does hashcat need a GPU to run on Parrot Linux?
No. Hashcat runs in CPU-only mode if no GPU is available, which is fine for learning and weak test hashes. A GPU simply makes it dramatically faster.
Why does hashcat -I only show my CPU?
The OpenCL runtime for your graphics card is not installed or the driver did not load. Install the correct ICD for your vendor, reboot, and confirm the device appears in clinfo.
Is it legal to use hashcat?
The tool itself is legal and widely used by security professionals. Cracking hashes you do not own or have written permission to test is not. Stick to your own hashes, lab machines, and CTF targets.