DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Ex-CIA employee ID’d but not charged in Vault 7 leak of hacking tools

Posted on May 16, 2018 by Dissent

It’s the leak/spy story of the year, I think. But no one has been charged as yet, even though they have a suspect. Dan Goodin reports:

Federal authorities have identified a suspect behind last year’s Vault 7 leak of Central Intelligence Agency hacking tools. The trove published to WikiLeaks included exploits and documents for infecting iPhones, Wi-Fi routers, and Cisco Switches, and it represented the biggest-known loss of classified information in CIA history.

According to articles posted by The Washington Post and The New York Times, the suspect is 29-year-old Joshua A. Schulte. FBI agents reportedly searched his Manhattan home a week after the WikiLeaks published its first Vault 7 dispatch in March 2017. A transcript of a court hearing this past January indicates that agents seized phones, computers, and unspecified “top secret government information.” According to the transcript, the evidence immediately made Schulte a target in the leak investigation.

Read more on Ars Technica.


Related:

  • US company with access to biggest telecom firms uncovers breach by nation-state hackers
  • Canada says hacktivists breached water and energy facilities
  • Another plastic surgery practice fell prey to a cyberattack that acquired patient photos and info
  • How a hacking gang held Italy’s political elites to ransom
  • UN Cybercrime Convention to be signed in Hanoi to tackle global offences
  • Two U.K. teenagers appear in court over Transport of London cyber attack
Category: HackOf Note

Post navigation

← Shadowy Hackers Accidentally Reveal Two Zero-Days to Security Researchers
More than 200,000 patients’ records were exposed on MedEvolve’s public FTP server – researcher →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs
  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • Lawmakers Warn Governors About Sharing Drivers’ Data with Federal Government
  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[at]databreaches.net
Mastodon: Infosec.Exchange/@PogoWasRight
Signal: +1 516-776-7756
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.