Thursday, February 27, 2025
HomeData Breach32TB of Windows 10 Internal builds & Source Code leaked online

32TB of Windows 10 Internal builds & Source Code leaked online

Published on

SIEM as a Service

Follow Us on Google News

Around 32TB of Windows 10 internal builds, including non-public installation images and software blueprints, upload online by an anonymous person on June 19.

Normally, internal builds were created by Microsoft engineers for bug-hunting and testing purposes. These private debugging symbols are normally stripped out in public releases.

The Leaked files are uploaded to the betaarchive website and very few people have access to that over FTP. Because downloading files from BetaArchive is not that much easy. According to experts who reviewed the source, it has the following reports, Register.

  • The source code of Windows 10 hardware drivers plus Redmond’s PnP code.
  • USB and Wi-Fi stacks.
  • Storage drivers.
  • ARM-specific OneCore kernel code.

Also read Windows Registry Analysis – Tracking Everything You Do on the System

The BetaArchive indicates that debugging symbols for the Windows 10 source code was also leaked. Any individual who has this data can use it for finding vulnerabilities, which could be utilized to hack Windows machines around the world.

Also, the leak consists of Multiple version of Microsoft’s Windows 10 Mobile Adaptation Kit, a private programming kit made by Microsoft meant to run Windows 10 working operating system on mobile devices.

But as indicated by experts, this is not as terrible as it sounds. The leaked source code is a part of the Microsoft’s Shared Source Kit program, and the majority of it was already accessible on the web.

Recent update from Betaarchive

At the time of writing this article, we saw a Statement published by BetaArchive indicates the contents have been removed already.

Betaarchive says "First of all let us clear up a few facts.The “Shared Source Kit”
 folder did exist on the FTP until this article came to light. We have removed it
from our FTP and listings pending further review just in case we missed something
in our initial release. We currently have no plans to restore it until a full
review of its contents is carried out and it is deemed acceptable under our rules."

As per update on 09:58 GMT 24/06/2017 Microsoft spokesperson contacted The Register and said: “Our review confirms that these files are actually a portion of the source code from the Shared Source Initiative and is used by OEMs and partners.”

Also read NSA Malware “EternalBlue” Successfully Exploit into Microsoft Windows 10

Gurubaran
Gurubaran
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Latest articles

GitLab Vulnerabilities Allow Attackers to Bypass Security and Run Arbitrary Scripts

GitLab has urgently released security updates to address multiple high-severity vulnerabilities in its platform...

LibreOffice Flaws Allow Attackers to Run Malicious Files on Windows

A high-severity security vulnerability (CVE-2025-0514) in LibreOffice, the widely used open-source office suite, has...

Cisco Nexus Switch Vulnerability Allows Attackers to Cause DoS

Cisco Systems has disclosed a high-severity vulnerability (CVE-2025-20111) in its Nexus 3000 and 9000...

Silver Fox APT Hackers Target Healthcare Services to Steal Sensitive Data

A sophisticated cyber campaign orchestrated by the Chinese Advanced Persistent Threat (APT) group, Silver...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Orange Communication Breached – Hackers Allegedly Claim 380,000 Email Records Exposed

Telecommunications provider Orange Communication faces a potential data breach after a threat actor using the pseudonym “Rey”...

US Employee Background Check Firm Hacked, 3 Million Records Exposed

DISA Global Solutions, a Houston-based provider of employee background checks and workplace safety services,...

Raymond IT Systems Hit by Cyber Attack, Authorities Investigating

Textile and apparel conglomerate Raymond Limited confirmed a cybersecurity breach affecting portions of its...