6 Famous Hackers That Got Caught: Cases and Outcomes
September 4, 20217 min read1,444 words
Hacker history becomes useful when I separate the legend from the record. These six cases show why technical ability, permission, evidence, and legal outcomes are different questions.

The takeaways
- 01
The six cases involved different investigations and legal outcomes.
What to do nextCheck whether a source describes an allegation, charge, guilty plea, or sentence.
- 02
Bevan’s dropped prosecution must not be described as a conviction.
What to do nextInclude the final legal outcome when summarizing an investigation.
- 03
Repeated hacker legends are not a substitute for evidence.
What to do nextTrace a dramatic historical claim to a reliable source before sharing it.
- 04
Technical skill does not establish permission to access a system.
What to do nextUse an authorized lab and obtain written scope before testing someone else’s environment.
Six famous hackers and what happened to them
Adrian Lamo, Mathew Bevan, Richard Pryce, Kevin Poulsen, Kevin Mitnick, and Albert Gonzalez became well-known through investigations into unauthorized access and computer crime. Their cases had different outcomes. Being charged is not the same as being convicted, and “got caught” can conceal important details.
The common thread is not a genius who stayed invisible until one mistake. These public records describe different conduct, investigations, and legal outcomes. Some popular retellings flatten those differences into a legend.
I read these cases through the responsibilities of cybersecurity work: get permission before testing, distinguish an allegation from a finding, and explain the harm without glamorizing the person who caused it. My experience building Alpine Security and leading Blue Goat Cyber makes those boundaries more useful to me than a ranking of the “best” hackers.
Here is a quick comparison before the individual accounts. Dates identify the stated legal event, not necessarily the intrusion itself.
| Person | Case or investigation | Key legal event |
|---|---|---|
| Adrian Lamo | The New York Times network intrusion | Surrendered and charged in September 2003; pleaded guilty in January 2004 |
| Mathew Bevan | Investigation into military-network intrusions | Charged in June 1996; case later dropped |
| Richard Pryce | Related military-network investigation | Admitted offenses and was fined |
| Kevin Poulsen | Computer and telephone-related fraud | Arrested April 11, 1991; sentenced in April 1995 |
| Kevin Mitnick | Fugitive and computer-fraud case | Arrested February 15, 1995; sentenced in 1999 |
| Albert Gonzalez | Retail and payment-network breaches | Guilty pleas in 2009; major federal sentences in March 2010 |
1. Adrian Lamo: The New York Times intrusion
Lamo accessed The New York Times network on February 26, 2002. According to the Justice Department's account of the charge, he accessed contributor information and added his own record to a database of expert sources.
He surrendered to federal authorities on September 9, 2003. The intrusion date and surrender date are different events. The Justice Department reported his guilty plea on January 8, 2004.
The useful lesson is not that a visible weakness is an invitation. Finding an accessible system does not establish permission to explore it, alter records, or use its services. I would distinguish an authorized assessment with an agreed scope from a person entering a network on their own initiative.
2. Mathew Bevan: military-network investigation
Bevan, known as Kuji, was investigated in connection with intrusions into military computer systems. Contemporary Reuters reporting published by The New York Times recorded his charge in June 1996.
Accounts of this investigation describe South Korean research data being copied onto a U.S. Air Force system. That raised concern about the nature of the access. It does not establish that the intrusions almost started World War III.
The prosecution ultimately dropped Bevan's case, as described in the BBC's later account. I include that outcome because an arrest or accusation must not be presented as a conviction. The distinction is part of getting the history right.
3. Richard Pryce: a related case, a different outcome
Pryce, known as Datastream Cowboy, was the other British hacker associated with the investigation. He and Bevan are often placed in one paragraph, but they were two people with separate legal outcomes.
Reporting on the outcome of the military-network cases describes Pryce admitting offenses and receiving a fine. That is different from Bevan's dropped prosecution.
For me, this is also a reminder about how I read incident accounts. A dramatic collective label can hide what each person actually did and what the evidence established. When discussing security history, I want the distinction between an allegation, an admission, and a court outcome to remain visible.
4. Kevin Poulsen: telephone and computer fraud
Poulsen, known as Dark Dante, became associated with telephone-system intrusions and radio-contest fraud. He was arrested on April 11, 1991, after being a fugitive, according to the Los Angeles Times arrest report.
His story is often reduced to winning a Porsche in a manipulated radio contest. The broader case involved computer and telephone-related offenses, rather than just a lucky caller. The Los Angeles Times sentencing report records a 51-month sentence in April 1995.
A manipulated contest also illustrates a boundary that matters outside cybersecurity: technical control over a process is not a legitimate entitlement to its reward. The 1991 arrest and 1995 sentence belong to different stages of the case, not one immediate consequence.
5. Kevin Mitnick: arrest in North Carolina
Mitnick was arrested on February 15, 1995, in North Carolina. The Justice Department's announcement described him as a fugitive wanted for violating probation. His subsequent federal case ended with a guilty plea and sentencing in 1999; contemporary sentencing coverage reported a 46-month sentence with time already served.
One correction matters here: the repeated story that Mitnick hacked NORAD and inspired WarGames is not established history. An analysis of the NORAD myth explains how unsupported claims became part of his public reputation.
That is why I do not judge a security story by how often it is repeated. If the central claim is unsupported, repetition does not make it evidence.
6. Albert Gonzalez: retail and payment-network breaches
Gonzalez was involved in large-scale theft of payment-card data from retail and banking networks. The federal cases covered multiple victims and separate schemes; they should not be compressed into one alleged breach or one arrest date.
He pleaded guilty in the TJX-related retail case on September 11, 2009, as described in the Justice Department's plea announcement. He entered another guilty plea on December 29, 2009, in a separate retail and banking-network case.
His major federal sentences followed in March 2010. A Justice Department sentencing record documents the retail and banking-network case.
The practical distinction is scale of harm versus fame. Payment-card theft concerns the organizations and people whose information was stolen, not just the reputation of the attacker. I do not need an unsupported “first” or “biggest” label to explain why that harm matters.
How were these hackers caught?
There is no single supported answer across all six cases. The sources above establish arrests, charges, pleas, and other legal outcomes. They do not provide a complete technical reconstruction of every identification or investigation.
That limit matters. An arrest notice is evidence that an arrest happened; it is not automatically a description of the logging, interviews, or forensic steps that led to it. I would rather name the gap than invent a dramatic tracing scene. Use the linked source for the specific case instead of assuming one technique explains all six.
What these cases teach about ethical hacking
The lesson I take into professional security work is responsibility, not invulnerability. Technical ability tells me what someone may be able to do. Authorization tells me what they are allowed to do. Evidence helps establish what actually happened.
Before testing a real environment, clarify these boundaries with its owner:
- Permission: who can authorize the work, and what approval has been given?
- Scope: which systems, dates, and activities are included, and which are excluded?
- Handling: how will findings, sensitive information, and unexpected effects be reported?
- Stopping conditions: when should testing pause so the owner can make a decision?
This is a practical starting point, not legal advice or a substitute for a complete engagement agreement. Discovering an exposed system is not permission to investigate further. For learning, use a lab or another environment explicitly intended for authorized practice.
A second lesson is how we explain incidents. Bevan’s dropped prosecution, Pryce’s admission, and Gonzalez’s guilty pleas are not interchangeable. Neither are an attacker’s nickname and the evidence of their conduct. Keeping those distinctions visible helps readers understand the case without turning suspicion into certainty.
What to read next: from hacker history to responsible practice
- Start with permission and professional testing. Read Penetration Testing History to explore how authorized assessment differs from entering someone else’s system on your own initiative.
- Understand the culture without confusing it with competence. Read Leetspeak: Meaning, 1337 Examples, and History for slang, number substitutions, and why playful spelling is not security.
- Make the lesson understandable to other people. Continue with The Meaning of Communication Is the Response You Get. A security explanation needs to help the listener understand and act, not simply recognize the speaker’s expertise.
For the broader leadership framework, explore The Smartest Person in the Room, or browse the cybersecurity collection.
Frequently asked
Keep reading
Penetration Testing History
Begin with the history of authorized assessment and why scope matters.
Read essay →Leetspeak: Meaning, 1337 Examples, and History
Understand hacker culture without mistaking slang for competence.
Read essay →The Meaning of Communication Is the Response You Get
Explain the evidence, uncertainty, and next action clearly.
Read essay →