- Date
- Apr 25 – May 11, 2001
- Location
- United States
- Industry
- Energy
- Access vector
- Exploit Public-facing Application
- OT targeting
- None
- Primary peril
- None
- Impact duration
- 17 days
California ISO grid-operator intrusion, 2001

The incident path, stage by stage
Each stage of the attack, from intent to financial loss, with this incident’s path highlighted. Solid cells are confirmed, dashed cells are reported by a source but not confirmed, dotted cells are implied by the facts, and Unknown marks what is not publicly known. Click a stage title or a highlighted cell to read that part of the analysis.
Scroll sideways to see every stage.
On this page
Highlights
What happened. From as early as April 25 to May 11, 2001, intruders were inside development servers of the California Independent System Operator (Cal-ISO), which runs the bulk of California’s transmission grid, at the height of the state’s energy crisis[1][2]. Cal-ISO said markets and grid reliability were not affected[2].
Why it matters. It is an early documented intrusion at a grid operator, and it leaves a question the public record never closed: Cal-ISO said the intruders never got close to the systems that run the grid, while an unnamed source called it “very close to being a catastrophic breach”[3][2].
About this analysis. This analysis sets out what is known, stage by stage. It rests on press accounts from June 2001 of a confidential internal report that was never published. This account reflects the best available information as of October 22, 2026; new information could confirm, change or discredit parts of it.
Highlights
- The intrusion lasted at least 17 days before it was detected on May 11, 2001, according to the Los Angeles Times, which drew on a confidential Cal-ISO report[1][2].
- The intruder used a Solaris flaw to take control of two web servers on a development network that, according to sources close to the investigation, were connected directly to the internet[4].
- Rolling blackouts on May 7 and 8 fell inside the intrusion window. Cal-ISO officials said they were not connected to the hacking, and no source claims they were[2][5].
- The main attack appeared to come from Guangdong province, China, but officials could not confirm the origin, and no one was identified or arrested[2].
Attack flow
- Updated: 2026-10-22
- Intent: Malicious [confirmed]
- Threat actors: Not attributed [unknown | Origin not confirmed]
- Access vector: Exploit Public-facing Application [reported | T1190, Solaris flaw]
- IT impact: Not disclosed [unknown | No IT impact described]
- OT targeting: None [confirmed | Grid systems not reached]
- OT sophistication: Not applicable [not in path | No OT reached]
- OT impact: Not in path [not in path | No OT system reached]
- Perils: No Perils [confirmed | No physical event]
- Financial losses: Cyber Incident Response [implied]
What happened
The Los Angeles Times reported on June 9, 2001, drawing on a confidential Cal-ISO report, that hackers attacked the agency’s computer system “for at least 17 days at the height of the energy crisis”[1]. Reuters, summarizing the Times, said the attack began as early as April 25 and was not detected until May 11, when investigators saw hackers trying to get through security firewalls[2].
The attackers focused on parts of the system that were under development, and “the system being developed was not behind a firewall,” the Times said[1]. CNET added that the intruder used a security flaw in Cal-ISO’s Solaris servers to take control of two web servers on a development network. They were meant to sit behind a firewall but, according to sources close to the investigation, were connected directly to the internet. The servers kept their logs on the same machines, so investigators could not easily tell which files had changed[4].
The internal report, as the Times described it through Reuters, said the main attack appeared to come from Guangdong province, routed through China Telecom, and entered through internet servers in Tulsa, Oklahoma, and Santa Clara, California[2]. The FBI investigated[5][3]. Rolling blackouts on May 7 and 8, which hit more than 400,000 utility customers, fell inside the intrusion window; Cal-ISO officials said they were not connected to the hacking[2][5].
The story became public through the press about four weeks after detection, not through Cal-ISO or a regulator. CNET reported that state legislators were not told for more than a month, and that State Senator Tom McClintock requested the break-in documents under California’s open-records law[4].
Intent: malicious
An intrusion that ran for at least 17 days, found when investigators saw the intruders trying to get through security firewalls, was deliberate[1][2]. Cal-ISO’s computer security specialist, James Sample, called it “a compromise, not really an attack”[2], which is a statement about its effect rather than its intent. What the intruders wanted is not stated in any source.
Threat actors: not attributed
The internal report traced the main attack to Guangdong province through China Telecom, but officials could not confirm the true origin[2]. Sample said at the time: “An ambitious U.S. hacker could have posed as a Chinese hacker”[2]. A routing path is not an attribution. The FBI investigated, and no one was identified or arrested[5][3]. No threat actor is highlighted on the map.
Access vector: an exposed development server
Cal-ISO never described the route. CNET, citing sources close to the investigation, reported that the intruder used a security flaw in Cal-ISO’s Solaris servers and took control of two web servers on a development network that were connected directly to the internet, although they were meant to sit behind a firewall[4]. The Times said the system under development “was not behind a firewall”[1]. No source names the flaw. Exploiting a public-facing application is the matching technique, shown as reported. Reading the servers in Tulsa and Santa Clara as relays is DeNexus’s reading of the reporting, not a statement by any source[2].
IT impact: not disclosed
No source describes what the intruders did on the two servers, and no data is reported stolen, altered or destroyed. Cal-ISO spokesman Greg Fishman called it “minimal penetration into a system that we use to demonstrate software”[4]. Because the logs sat on the compromised machines, investigators could not easily tell which files had changed[4]. This stage is marked Not disclosed.
OT targeting: none
No source places the intruders inside the energy management system, the market systems or any grid control function. Fishman said they “never really got close at all to our operational systems that run the grid”[3], and spokeswoman Stephanie McCorkle said “It did not affect markets or reliability”[2]. A real intrusion produced no OT effect, so targeting is shown as None. That is Cal-ISO’s account; no independent source tested it.
OT sophistication: not applicable
No source describes ICS-specific tooling, protocol knowledge or process awareness. What is described is a server flaw on a development network[4]. With no OT reached, there is nothing to grade, and this stage is marked Not applicable.
OT impact: none, and an open question about the margin
No effect on markets, reliability or any physical process is reported[2]. The open question is the margin, not the outcome. An unnamed source familiar with the attack and Cal-ISO’s investigation said “This was very close to being a catastrophic breach”[2]; Cal-ISO said the intruders never got close[3]. Both can be true: one is a claim about what happened, the other about how close it came. No public source says what stood between the development servers and the grid systems.
Perils: none
No equipment, breaker or process was affected, and no physical consequence of any kind is described[2]. The rolling blackouts of May 7 and 8 were not linked to the intrusion by Cal-ISO or by any source[2][5]. The map shows No Perils.
A record where nothing happened is not, by itself, evidence that a control held.
Financial losses: what it cost
No cost figure exists in any source. The realized loss is investigation and remediation effort that no one itemized: a confidential internal report and an FBI investigation[1][5]. Cal-ISO officials said the problem was fixed, without describing a program, its scope or its cost[2].
Loss evidence
- Implied: Network event response and recovery (internal report, FBI investigation); Voluntary improvements (fixes to the development system)
- Not supported: Direct business interruption; Third-party physical and societal impact (no link to the May blackouts); Cyber-physical event response
What this incident shows
Dwell time is the clearest finding. The intrusion ran for at least 17 days at the operator of a state transmission grid before anyone noticed, and logs kept on the compromised machines made it hard to reconstruct afterwards[1][4]. DeNexus’s records hold similar dwell findings at grid targets two decades later.
The second finding is about what a non-event proves. Nothing happened, but the one architecture fact in the record cuts against crediting the separation of IT from grid systems: the development system was not behind a firewall[1]. Whether that separation held or was simply never tested, the public record cannot say.
References
- Morain, Dan. “Hackers Victimize Cal-ISO.” Los Angeles Times, 9 June 2001, excerpt as carried by the Politech list, 11 June 2001. seclists.org/politech/2001/Jun/40
- “Hackers hit California power grid computers.” Reuters, 10 June 2001, as carried by Deseret News. deseret.com/2001/6/10/19590720/hackers-hit-california-power-grid-computers/
- Verton, Dan. “California hack points to possible IT surveillance threat.” Computerworld, 12 June 2001, as carried by InfoSec News. seclists.org/isn/2001/Jun/57
- Lemos, Robert. “Hack raises fears of unsafe energy networks.” CNET News.com, 13 June 2001, as carried by InfoSec News. seclists.org/isn/2001/Jun/64
- Associated Press. “Hackers threatened California power supply.” CNET News.com, 9 June 2001, as carried by InfoSec News. seclists.org/isn/2001/Jun/46


