- A grey hat hacker accesses systems without explicit permission but without malicious intent. They occupy the legally ambiguous space between ethical white hat hackers and criminal black hat hackers.
- Grey hats typically discover security vulnerabilities, notify the affected organisation, and sometimes request payment for the disclosure.
- Unlike white hat hackers, grey hats do not obtain authorisation before accessing systems. Unlike black hat hackers, they do not exploit what they find for personal gain.
- Grey hat hacking is illegal in most jurisdictions under laws like the CFAA, regardless of intent. Good intentions do not provide legal protection.
- The legitimate equivalent is bug bounty hunting: authorised vulnerability research that pays for responsible disclosure without legal risk.
In 2013, security researcher Marcus Hutchins identified a kill switch in the WannaCry ransomware that stopped the attack from spreading further. He became globally recognised as someone who saved hundreds of thousands of systems. He also later pleaded guilty to unrelated charges of creating banking malware. His story illustrates the complexity of the grey hat space better than any definition can.
Grey hat hackers operate without the explicit permission that defines ethical hacking, but without the malicious intent that defines criminal hacking. They exist in a legally murky space, and understanding that space is important for anyone studying cybersecurity or considering vulnerability research.
What is a grey hat hacker?
A grey hat hacker is a cybersecurity practitioner who accesses systems or networks without explicit authorisation in order to identify security vulnerabilities, but without the intention of exploiting those vulnerabilities for personal gain or causing harm. After gaining access, a grey hat typically notifies the affected organisation of what they found and sometimes requests compensation for the disclosure.
The name comes from the moral ambiguity of the position. White hat hackers (ethical hackers) always obtain written permission before testing. Black hat hackers (malicious hackers) exploit what they find. Grey hats fall between both: they enter without permission, but their goal is to improve security rather than to cause harm.
White hat vs. grey hat vs. black hat: the key differences
| White hat | Grey hat | Black hat | |
|---|---|---|---|
| Authorisation | Always obtained before testing | Not obtained or obtained after access | Absent, stolen, abused, or exceeded |
| Intent | Improve security, protect systems | Improve security, personal challenge, exposure | Steal, destroy, exploit for gain |
| Disclosure | Full disclosure to the affected party | Disclosed to target, sometimes publicly | Exploited or sold to third parties |
| Legal status | Legal when conducted within written authorisation and agreed scope | Usually illegal despite good intent | Criminal |
| Compensation | Contracted fee or bug bounty | May request payment after the fact | Ransom, data sale, dark web markets |
How grey hat hackers operate
Grey hat hacking typically follows a recognisable pattern:
1 Unsolicited scanning or probing
A grey hat scans websites, web applications, or network infrastructure looking for exploitable vulnerabilities. This is done without the knowledge or permission of the target organisation.
2 Exploitation for access verification
The grey hat exploits a discovered vulnerability to confirm that it is genuinely exploitable and to assess its potential impact. This is where the legal line is crossed.
3 Disclosure to the target
After gaining access, the grey hat contacts the affected organisation and discloses the vulnerability. This disclosure may include a request for payment, a bug bounty reward, or simply an expectation of acknowledgement.
4 Public disclosure as pressure
If the organisation does not respond or refuses to pay, some grey hats publish the vulnerability publicly. This pressures the target to patch the issue but also potentially exposes users to exploitation before the patch is released.
Responsible disclosure frameworks, used by white hat researchers, give organisations a defined window (typically 90 days) to patch a vulnerability before it is published. Grey hat public disclosure often lacks this structure and can create real harm for users even when that was not the grey hat's intent.
Real-world grey hat hacking examples
The Facebook zero-day report (2013)
Security researcher Khalil Shreateh discovered a vulnerability in Facebook that allowed him to post on any user's wall without their permission. He reported the bug through Facebook's official bug bounty programme. Facebook's security team told him the behaviour was intentional and closed the report. Shreateh then exploited the vulnerability to post directly on Mark Zuckerberg's wall to demonstrate the flaw. Facebook patched the vulnerability, but because Shreateh had used it against a real user's account, the company declined to pay the bug bounty. Shreateh argued he acted in the public interest. The CFAA disagreed with the legality of his method.
The Syrian Electronic Army router compromise (2014)
A grey hat hacker disclosed vulnerabilities in routers used by the Syrian Electronic Army, a group known for pro-government cyberattacks. The researcher accessed the routers, documented the vulnerabilities, and notified authorities. The intent was to disrupt a malicious actor, but the access was unauthorised. The researcher's method was grey hat; the target was black hat.
Marcus Hutchins and WannaCry (2017)
Marcus Hutchins, a British security researcher, registered a domain name embedded in the WannaCry ransomware that functioned as a kill switch. His action stopped the ransomware from spreading to new systems globally. The discovery required analysing malware samples, which is standard security research. It did not require unauthorised access and is considered white hat work. Hutchins' later legal troubles involved separate activities predating WannaCry and are often cited to illustrate how grey hat adjacent activity can carry long-term legal consequences.
Why people engage in grey hat hacking
Understanding the motivations behind grey hat hacking is important for evaluating both the ethical and policy dimensions of the practice.
- Security improvement: Many grey hats genuinely believe they are contributing to a safer internet. They identify vulnerabilities that might otherwise be exploited by malicious actors and help organisations fix them.
- Recognition and professional credibility: Discovering a critical vulnerability in a major platform generates significant professional recognition in the security community, even when the legal risk is present.
- Financial motivation: Some grey hats request payment for disclosure. When legitimate bug bounty programmes exist, this financial motivation can be channelled legally. When they do not, grey hat disclosure becomes the primary mechanism.
- Challenge and curiosity: The technical challenge of finding and exploiting vulnerabilities is itself a motivation for many researchers, independent of the consequences.
The legal risk: what grey hat hackers face
Under the Computer Fraud and Abuse Act (CFAA) in the U.S., accessing a computer system without authorisation is a federal crime. The statute does not contain an exception for good intentions. Penalties include significant fines and up to 10 years imprisonment for first offences, with enhanced penalties for repeat offences.
The Electronic Frontier Foundation (EFF) has argued for years that CFAA's broad language criminalises legitimate security research. Grey hat hackers are particularly vulnerable because their activities are often genuinely beneficial but technically illegal. A grey hat who discovers and discloses a critical vulnerability in critical infrastructure is in legal jeopardy regardless of the outcome.
International equivalents include the Computer Misuse Act in the UK, the Cybercrime Act in Australia, and Directive 2013/40/EU in the European Union. All impose criminal liability for unauthorised access regardless of intent.
The legitimate alternative: bug bounty hunting
The cybersecurity industry has created a legal alternative that captures most of what grey hats want to do: bug bounty programmes. Companies like HackerOne and Bugcrowd host programmes for hundreds of organisations including Google, Microsoft, Apple, and the U.S. Department of Defense. Researchers who find and responsibly disclose vulnerabilities within programme scope are recognised, and legally protected.They are usually protected only if they stay within scope and follow the programme policy. Not every valid report is paid. Not every programme gives “complete” protection.
Bug bounties have paid out over $300 million to security researchers through HackerOne alone. The top earners make more than $500,000 per year. The incentive to work within legal boundaries is substantial, and the protection is complete. A grey hat who operates outside a programme accepts all the legal risk while often receiving less recognition and no guaranteed payment.
If you want to find and report vulnerabilities legitimately, bug bounty hunting is the path. It provides authorisation, legal protection, and payment for the same work that grey hat hacking does illegally. The skills are identical. The legal status is entirely different.
Build offensive security skills the right way
Explore the Metana Cybersecurity Bootcamp and see how to build the skills that get you into ethical hacking, penetration testing, and bug bounty hunting legally.
Explore at metana.io/cybersecurity-bootcamp →FAQ
What is a grey hat hacker?
A grey hat hacker accesses computer systems or networks without explicit authorisation but without malicious intent. They typically identify security vulnerabilities and disclose them to the affected organisation, sometimes requesting payment. Grey hat hacking occupies the legally ambiguous space between authorised ethical hacking and criminal black hat hacking.
Is grey hat hacking illegal?
Yes, in most jurisdictions. The Computer Fraud and Abuse Act (CFAA) in the U.S. criminalises unauthorised access to computer systems regardless of intent. Equivalent laws in the UK, Australia, and the EU carry similar provisions. Good intentions do not provide legal immunity. A grey hat who discloses a vulnerability responsibly has still committed a criminal act under most computer crime statutes.
What is the difference between grey hat and white hat hackers?
White hat hackers always obtain explicit written authorisation before accessing any system. They operate legally and disclose findings under agreed terms. Grey hat hackers access systems without authorisation, even if their intent is benign. The key distinction is not motivation but whether permission was obtained before the activity began.
What is a real-world example of grey hat hacking?
In 2013, researcher Khalil Shreateh discovered a Facebook vulnerability allowing posts to any user's wall without permission. After Facebook dismissed his report, he demonstrated the flaw by posting on Mark Zuckerberg's wall. Facebook patched the bug but refused the bounty payment because Shreateh had exploited the vulnerability against a real user's account without authorisation.
What is the legal alternative to grey hat hacking?
Bug bounty programmes provide a legal, paid alternative. Platforms like HackerOne and Bugcrowd host programmes for hundreds of organisations where researchers can find and disclose vulnerabilities within a defined scope, receive payment, and have full legal protection. The skills required are identical to grey hat hacking. The legal status is entirely different.
Written by
Raqeeb Ameen
Raqeeb Ameen is an AI and cybersecurity researcher examining the security implications of autonomous AI agents and automated decision-making systems. He writes on emergent attack vectors, prompt injection defenses, and the evolving threat landscape in AI security, helping organizations safely deploy agentic systems in production.
