Vault 7: CIA Hacking Tools, the Source, and the Response

Vault 7 is the code name WikiLeaks gave to its 2017 publication of thousands of confidential CIA files that exposed the agency’s global arsenal of hacking tools, malware, and cyber-espionage techniques. The Vault 7 WikiLeaks disclosures began on March 7, 2017, ran in more than twenty batches through September of that year, and were eventually traced to Joshua Adam Schulte, a former CIA software developer who was sentenced in February 2024 to 40 years in federal prison.

What WikiLeaks Published

The first release, “Year Zero,” contained 8,761 documents and files taken from an isolated network inside the CIA’s Center for Cyber Intelligence in Langley, Virginia. WikiLeaks described it as the largest publication of confidential CIA documents in history and said the archive had already circulated among government hackers and contractors before reaching the organization. Before publishing, WikiLeaks said it applied more than 70,000 redactions to shield specific identities and targeted machines.¹

Year Zero was followed by more than twenty additional batches between March and September 2017, each focused on a different CIA project or tool. The final batch, “Protego,” appeared on September 7, 2017.² Two months later, in November 2017, WikiLeaks began a separate but related series called Vault 8, which published the actual source code for Hive, a covert communications platform the CIA used to control its malware implants. Hive relayed stolen data to hidden CIA servers through cover domains and fake digital certificates, including certificates impersonating Kaspersky Lab.³

The Hacking Arsenal the Files Exposed

The documents showed that the CIA’s Engineering Development Group had produced over a thousand hacking systems, trojans, viruses, and other weaponized software. By 2016 the Center for Cyber Intelligence had more than 5,000 registered users, and WikiLeaks characterized it as the agency’s own version of the NSA.¹

Phones and Computers

Specialized branches built attacks against iPhones and Android devices to pull geolocation data, text messages, and audio, and to silently activate microphones and cameras. On the desktop side the agency stockpiled zero-day exploits against Windows, macOS, and Linux. The Grasshopper framework built customized malware payloads for Windows machines, and the Marble Framework was an anti-forensics tool that could disguise CIA malware as if it had been written in Chinese, Russian, Korean, Arabic, or Farsi.⁴

Smart Televisions

“Weeping Angel,” developed jointly with Britain’s MI5, targeted Samsung F8000 smart TVs. It placed the sets in a “Fake-Off” mode where the screen appeared powered down while the television’s microphone kept recording and transmitting to CIA servers.¹

Routers and Networks

The Cherry Blossom project targeted hundreds of home router and wireless access point models from Belkin, D-Link, Linksys, and Cisco, loading custom firmware to enable man-in-the-middle attacks and traffic monitoring.⁵ Other tools exploited Cisco routers and switches to run administrative commands, redirect web traffic, poison DNS records, and exfiltrate data while hiding from detection.⁶

Isolated Systems

Brutal Kangaroo and HammerDrill were designed to jump “air gaps,” the physical isolation that protects the most sensitive government and corporate networks. Brutal Kangaroo used infected USB thumb drives to establish covert data-transfer networks inside isolated systems.²

Credential Theft and Covert Collection

BothanSpy and Gyrfalcon stole SSH credentials and intercepted session traffic on Windows and Linux. ExpressLane was designed to secretly copy biometric data that the CIA had provided partner intelligence agencies to gather, effectively spying on allies. CouchPotato remotely captured video streams, and Dumbo disabled webcams and microphones during physical operations so field agents could act without being recorded.²

Hiding the Fingerprints

A recurring theme was misdirection. The UMBRAGE group maintained a library of attack techniques and digital fingerprints stolen from other nations, including Russia, so that if an operation were discovered, forensic investigators might attribute it to a different country. Marble could insert foreign-language text into code to reinforce the misdirection.⁴ The Fine Dining system gave case officers a menu of decoy applications, including fake virus scanners, video players, and games, to disguise the installation of malware on a target’s computer.¹

How the CIA Lost the Files

An internal CIA report ordered by then-Director Mike Pompeo found that the Center for Cyber Intelligence had failed to implement basic security standards. The unit did not segregate access to its various hacking tools, allowed administrator-level passwords to be shared among employees, placed no restrictions on the use of USB drives, and did not monitor its own network.⁷ The team had focused on building offensive weapons and spent too little energy protecting them. The report acknowledged that the CIA had “moved too slowly to put in place the safeguards that we knew were necessary” and should have anticipated an insider threat after the Manning and Snowden disclosures.⁸

Because of those gaps, the agency could not detect the theft when it happened and remained unable to determine the precise scope of what was taken. It only learned of the breach when WikiLeaks began publishing the files in March 2017.

Joshua Schulte, the Source

Joshua Adam Schulte, a software developer at the Center for Cyber Intelligence from 2012 to 2016, was identified as the source. Prosecutors established that Schulte used his administrator privileges to steal the files in April 2016 and later transmitted them to WikiLeaks.⁹

Motive

According to reporting by The New Yorker and court records, Schulte’s motivation grew from escalating conflicts at work rather than ideology. He and a colleague identified in court as “Amol” had a prolonged feud that included verbal confrontations and a physical altercation involving Nerf guns. Schulte alleged that Amol threatened his life, filed a formal complaint with CIA security, and eventually sought a restraining order in Virginia state court, a step so unusual it alarmed agency officials.¹⁰

Schulte felt management sided against him. He was moved to what he considered a demeaning desk, a project built on his own code was reassigned to an outside contractor, and after he was blocked from working on Brutal Kangaroo, he reassigned himself access without authorization. Management revoked his administrator privileges and transferred him. He left the CIA in November 2016. Prosecutors argued the leak was retaliation against supervisors who had ignored his complaints.¹¹

Three Trials

Schulte was prosecuted in the Southern District of New York, case number 17-CR-548. His case ran through three separate trials.

March 2020: the jury deadlocked on eight counts tied to the theft and transmission of classified information, producing a mistrial on those charges. Schulte was convicted on two lesser counts, contempt of court and making false statements to the FBI.¹²
July 2022: at retrial, Schulte was convicted on all nine remaining counts, including four counts of espionage under 18 U.S.C. § 793 and four counts under the Computer Fraud and Abuse Act.¹³
September 2023: a separate trial resulted in conviction on three counts related to possession, receipt, and transportation of child sexual abuse material. The FBI had found roughly 10,000 images and videos on Schulte’s personal devices.¹⁴

Sentencing

On February 1, 2024, U.S. District Judge Jesse M. Furman sentenced Schulte to 40 years in federal prison followed by lifetime supervised release. Thirty-three years and four months were for the espionage and hacking convictions, and the remainder for the child exploitation material.¹⁵ Judge Furman said Schulte was motivated by “anger, spite and perceived grievance” and displayed a “complete lack of remorse.”¹⁴

Prosecutors secured a “terrorism enhancement,” arguing that Schulte’s actions were “clearly calculated to retaliate against the United States as a whole.” Defense attorneys characterized him instead as a “maladjusted and discontented employee.”¹⁶ Press freedom groups objected to the enhancement. Defending Rights and Dissent policy director Chip Gibbons warned that “using an isolated and unpopular defendant, the government has dramatically expanded its arsenal against media sources.”¹⁷ Schulte’s appeal to the U.S. Court of Appeals for the Second Circuit was pending as of early 2024.¹⁸

Leaking From Jail

Schulte’s activity did not stop after his arrest. While detained at the Metropolitan Detention Center in Brooklyn, he obtained smuggled cellphones and used them to set up anonymous encrypted email and social media accounts. Through those accounts he transmitted classified information and sealed court materials to WikiLeaks and to family members for further distribution.¹⁹ An FBI search of his cell turned up multiple contraband phones and roughly 13 email and social media accounts. Prosecutors filed additional charges, and Judge Furman cited the jailhouse conduct at sentencing.²⁰

The Government and Industry Response

On April 13, 2017, five weeks after Year Zero, CIA Director Mike Pompeo called WikiLeaks a “non-state hostile intelligence service often abetted by state actors like Russia” and labeled Julian Assange “a fraud” and “a coward.”²¹ The FBI and CIA opened a joint criminal investigation while the agency continued its policy of neither confirming nor denying the authenticity of the leaked documents.²²

Technology companies scrambled to review their products. Apple said “many of the issues leaked today were already patched in the latest iOS” and pledged to “rapidly address” any remaining vulnerabilities. Microsoft and Samsung said they were investigating. Google did not comment publicly at the time despite the documents detailing Android targeting.²³ Cisco reviewed its code in light of the disclosures and discovered a critical flaw in the Cluster Management Protocol of its IOS and IOS XE software that could allow an unauthenticated attacker to remotely execute code or crash a device. Cisco published a security advisory on March 17, 2017.⁶

Why the Leak Still Matters

U.S. officials described the breach as the most damaging disclosure of classified information in CIA history. At sentencing, prosecutors called it a “digital Pearl Harbor” that put agency personnel and intelligence assets at risk and cost the CIA hundreds of millions of dollars.⁹ Beyond the loss of individual tools, the files exposed tradecraft, cover entities, and server infrastructure that had taken years to build.

WikiLeaks itself highlighted the proliferation risk in cyber weapons: once such tools are loose, they can be copied and repurposed by rival states and criminals. Analysts contrasted Vault 7 with the Shadow Brokers leak of NSA tools, which released working exploit code and led directly to the WannaCry and NotPetya ransomware outbreaks. Vault 7 disclosed methods and tactics more than ready-to-use code, so the damage unfolded gradually, but the disclosed techniques narrowed the gap between sophisticated nation-state hackers and lower-level attackers. In one documented case, Vault 7 material tipped off attackers to a Cisco software flaw that put more than 300 of the company’s switches at risk of takeover.²⁴

The disclosures also reignited debate over the Vulnerabilities Equities Process, the framework under which the U.S. government decides whether to disclose software flaws to manufacturers or keep them secret for intelligence purposes. Tech companies were frustrated that the CIA had hoarded exploitable vulnerabilities rather than reporting them, and Mozilla publicly criticized the agency’s approach. The government maintained that the process was “biased toward responsible disclosure,” and NSA Director Admiral Mike Rogers had previously said “by orders of magnitude, the greatest number of vulnerabilities we find, we share.” Critics dismissed the process as a public relations exercise that would always favor intelligence collection over public safety.²⁵

Vault 7 also fed a broader legal debate about the government’s authority to hack. Senators Ron Wyden, Steve Daines, and Chris Coons had opposed a December 2016 amendment to Federal Rule of Criminal Procedure 41 that expanded law enforcement’s ability to obtain warrants for remote searches of computers in unknown locations, warning it granted “unlimited power for unlimited hacking.”²⁶ Federal courts remained divided on whether law enforcement hacking constitutes a search under the Fourth Amendment, and legal scholars noted the government’s “spotty compliance record” with existing warrant procedures.²⁷ Vault 7’s exposure of the CIA’s hacking capabilities lent urgency to calls for stricter oversight, reporting requirements, and minimization procedures for government cyber operations.

1
WikiLeaks. Vault 7: CIA Hacking Tools Revealed
2
WikiLeaks. Vault 7 Projects
3
WikiLeaks. Vault 8
4
Wired. CIA Files WikiLeaks Vault 7
5
InfoSec Institute. Vault 7 Data Leak: Analyzing CIA Files Released Since March
6
Cisco. The WikiLeaks Vault 7 Leak: What We Know So Far
7
Nextgov. Report: Lax Cybersecurity at CIA Unit Led to Vault 7 Leaks
8
New York Times. CIA Vault 7 Hacking Breach
9
U.S. Department of Justice. Former CIA Officer Joshua Adam Schulte Sentenced to 40 Years in Prison
10
The New Yorker. The Surreal Case of a CIA Hacker’s Revenge
11
Center for Development of Security Excellence. Case Study: Schulte
12
Courthouse News Service. Ex-CIA Coder Behind WikiLeaks Vault 7 Cache Found Guilty of Espionage
13
Reporters Committee for Freedom of the Press. Schulte Vault 7 Leak Sentence
14
NPR. Former CIA Engineer Sentenced to 40 Years
15
Press Freedom Tracker. Former CIA Agent Accused of Sending Classified Information to WikiLeaks
16
Courthouse News Service. Former CIA Coder Sentenced to 40 Years in Prison for WikiLeaks Vault 7 Breach
17
Freedom of the Press Foundation. Ex-CIA Employee Deserves a Long Prison Sentence, but Not for Leaking Documents
18
U.S. District Court, Southern District of New York. Sealing Order, United States v. Schulte
19
WHSV. Feds Accuse Ex-CIA Employee of Continuing Leaks From Prison
20
Politico. Ex-CIA Computer Engineer Sentenced for WikiLeaks Leak
21
NBC News. CIA Director Pompeo Calls WikiLeaks Hostile Intelligence Service
22
BBC. CIA Director Blasts WikiLeaks
23
The Guardian. WikiLeaks CIA Leak: Apple, Vault 7 Documents
24
Cybereason. Vault 7 Leaks: Long-Term Threats
25
Council on Foreign Relations. WikiLeaks and the CIA: What’s Vault 7
26
Just Security. Rule 41 Updated and Needed
27
The Yale Law Journal. Government Hacking