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.
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.”