Someone leaked 32TB of Windows 10 internal builds and source code
It looks like Microsoft is in trouble again. This time not for its critical vulnerabilities in Windows operating system but for a massive data leak in which 32TB of highly sensitive Windows 10 related data has been dumped online.
According to a report from TheRegister, it is believed that the data was stolen from Microsoft’s in-house systems in March. Those who have seen the data claim that the leaked files belong to Microsoft’s internal Windows operating system builds and in-depth details about its core source code.
Furthermore, TheRegister reported that the data was uploaded on a website called betaarchive.com, a collectors website for beta software, games, applications, and abandonware. But a discussion topic on the site denies uploading of any such data.
After a brief analysis, TheRegister has confirmed that the data is updated to last week, and includes “The source to the base Windows 10 hardware drivers plus Redmond’s PnP code, its USB and Wi-Fi stacks, its storage drivers, and ARM-specific OneCore kernel code.”
Furthermore, there are several never been released builds for Windows 10, which included testing, troubleshooting and debugging tools used by Microsoft internally. Also, there’s a Windows 10 Mobile Adaptation Kit, which looks like an unannounced toolset designed for Windows 10 to run on mobile devices.
This means that anyone who has downloaded the data and knew how to take advantage of it can exploit for security vulnerabilities and carry large-scale cyber attacks just like WannaCry ransomware attack which exploited Server Message Block (SMB) vulnerability in unpatched Windows 7 and Windows Server 2008 (or earlier OS) systems.
At this time, it is unclear if Microsoft has suffered a hack attack or someone from the inside has done the damage. However, it can be assumed that the data is highly sensitive for Windows and jackpot for hackers since the data is still available for anyone to download on the website.
Update:
Microsoft has now commented on the issue stating that: “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.”
Beta Archive’s administrator Andy has also posted an update stating that the Shared Source Kit was indeed leaked on their site which has now been removed. According to Andy’s post:
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.
//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (adsbygoogle=window.adsbygoogle||).push({});DDoS attacks are increasing, calculate the cost and probability of a DDoS attack on your business with this DDoS Downtime Cost Calculator.