It seems a huge amount of Windows software has been leaked, from an internal source. 32 terabytes of data, including, but not limited to beta copies of Windows 10, developer software, and potentially the most important of them all-- source code. UK news site, The Register, were the ones to initially break the story, claiming that these confidential testing builds and other data came from a source inside Microsoft, back in March 2017. The files were then uploaded on June 19, to Beta Archive, though they were removed shortly after. With the "shared source code kit" being available to the public, this means that users may be able to better customize Windows to their liking, but it also comes with the fact that this leaves users' security vulnerable and compromised, if one manages to use the source code to create a dangerous virus or exploit. The source below contains more intricate details on the matter.

The leaked code is Microsoft's Shared Source Kit: according to people who have seen its contents, it 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.

Anyone who has this information can scour it for security vulnerabilities, which could be exploited to hack Windows systems worldwide. The code runs at the heart of the operating system, at some of its most trusted levels.

This software includes, for example, prerelease Windows 10 "Redstone" builds and unreleased 64-bit ARM flavors of Windows. There are, we think, too many versions now dumped online for Microsoft to revoke via its Secure Boot mechanism, meaning the tech giant can't use its firmware security mechanisms to prevent people booting the prerelease operating systems.

EDIT: response from a Beta Archive admin

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.

The folder itself was 1.2GB in size, contained 12 releases each being 100MB. This is far from the claimed “32TB” as stated in The Register’s article, and cannot possibly cover “core source code” as it would be simply too small, not to mention it is against our rules to store such data.

At this time all we can deduct is that The Register refers to the large Windows 10 release we had on March 24th which included a lot of Windows releases provided to us, sourced from various forum members, Windows Insider members, and Microsoft Connect members. All of these we deemed safe for release to BetaArchive as they are all beta releases and defunct builds superseded by newer ones, and they were covered under our rules.

If any of this should change we will remove these builds from the FTP and we will happily comply with any instructions to do so by Microsoft.

Source

 

[Seriel]

I do know where my dad keeps his old Microsoft keycards

Leak the rest of the source for us :^)

 

[Thunder Hawk]

View attachment 91228​

It seems a huge amount of Windows software has been leaked, from an internal source. 32 terabytes of data, including, but not limited to beta copies of Windows 10, developer software, and potentially the most important of them all-- source code. UK news site, The Register, were the ones to initially break the story, claiming that these confidential testing builds and other data came from a source inside Microsoft, back in March 2017. The files were then uploaded on June 19, to Beta Archive, though they were removed shortly after. With the "shared source code kit" being available to the public, this means that users may be able to better customize Windows to their liking, but it also comes with the fact that this leaves users' security vulnerable and compromised, if one manages to use the source code to create a dangerous virus or exploit. The source below contains more intricate details on the matter.



Source

32TB

Yeah, try uploading that via FTP.
Also, other sources say it was a 1.2GB folder.
https://www.neowin.net/news/interna...-for-windows-10-revealed-in-massive-32tb-leak

An administrator at BetaArchive has now commented on the story, acknowledging that a folder entitled Shared Source Kit did exist but has been removed for further review, though they did also question the accuracy of many of the claims contained within the story. His full statement is as follows:

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.

The folder itself was 1.2GB in size, contained 12 releases each being 100MB. This is far from the claimed “32TB” as stated in The Register’s article, and cannot possibly cover “core source code” as it would be simply too small, not to mention it is against our rules to store such data.

At this time all we can deduct is that The Register refers to the large Windows 10 release we had on March 24th which included a lot of Windows releases provided to us, sourced from various forum members, Windows Insider members, and Microsoft Connect members. All of these we deemed safe for release to BetaArchive as they are all beta releases and defunct builds superseded by newer ones, and they were covered under our rules.

If any of this should change we will remove these builds from the FTP and we will happily comply with any instructions to do so by Microsoft.

With regards to the BBC article http://www.bbc.co.uk/news/technology-40366823 about two Britons that have been arrested following an alleged Microsoft hack, we don’t believe there is any connection with this alleged “Windows 10 core source code leak”.

 

[ThisIsDaAccount]

Bruh, I live in the middle of Microsoft territory. Their HQ is like a 15 min drive away, every other person here is a Microsoft employee. So if this was an inside-Microsoft source, there's a very real chance it could be a neighbor or someone xD

In the Seattle-Bellevue area? Most people I know around there would never even consider leaking this, and that's the probably where Microsoft would look first

 

[Viri]

The Windows 10 source code leaks, but this happens feels bad man!
https://www.reddit.com/r/pcmasterra...bished_and_old_xbox_development_kit_and_made/

 

[HaloEliteLegend]

In the Seattle-Bellevue area? Most people I know around there would never even consider leaking this, and that's the probably where Microsoft would look first

Mhm, I live near Redmond. I was merely joking, my neighbors are great people x3

 

[Chary]

32TB

Yeah, try uploading that via FTP.
Also, other sources say it was a 1.2GB folder.
https://www.neowin.net/news/interna...-for-windows-10-revealed-in-massive-32tb-leak

I'm reading reports that say a great many number of things. I will include the response in the OP though. Thank you.

 

[ThisIsDaAccount]

Mhm, I live near Redmond. I was merely joking, my neighbors are great people x3

Yeah agreed, I dont live there but most people from there are great people.

I imagine that Microsoft is probably searching everywhere for the leaker right now. The leakers are definitely not gonna have a good time

 

[HaloEliteLegend]

Yeah agreed, I dont live there but most people from there are great people.

I imagine that Microsoft is probably searching everywhere for the leaker right now. They're definitely not gonna have a good time

Not even Phoenix Wright could save 'em from Microsoft lawyers.
RIP leaker.

 

[Thunder Hawk]

Not even Phoenix Wright could save 'em from Microsoft lawyers.
RIP leaker.

If only this could have been done with Nintendo and all of their private keys.

 

[Jayro]

Again all the beautiful things Linux can get working with Windows now... This will be HUGE for WINE development.

 

[ForeverEternal]

Ransomware incoming

 

[HaloEliteLegend]

If only this could have been done with Nintendo and all of their private keys.

You know, Nintendo of America HQ is just a block down the road from Microsoft... And if I use that keycard @ Microsoft, then hop the fence...

 

[Tizm]

/First of all, who can exploit windows with all the source code, what I mean is, 32TB OF STORAGE WHO IS THAT fUCKING RICH???

 

[Thunder Hawk]

You know, Nintendo of America HQ is just a block down the road from Microsoft... And if I use that keycard @ Microsoft, then hop the fence...

Don't forget about Nintendo's Ninjas.

 

[hobbledehoy899]

Not even Windows' source code is secure!

 

[gman666]

Could this mean potential cracked Windows 10? A friend wants to know...

 

[Joe88]

Seems this is more looking like the register creating a click bait article because they didnt know what they were looking at.

 

[Thunder Hawk]

Could this mean potential cracked Windows 10? A friend wants to know...

Someone would have to actually look into this possible source code.

 

[the_randomizer]

Good thing I don't have Windows 10. Probably good I never upgraded (even though I can through some...certain methods).

 

[ihaveahax]

Again all the beautiful things Linux can get working with Windows now... This will be HUGE for WINE development.

no it won't. the Wine project does not use code from leaked Windows source because that would cause major legal issues. much like the win2k leak they will probably investigate every code contribution made, and who's making it, else something from the leaked source makes it in and the project is sued.

https://www.reddit.com/r/linux/comments/1j5q71/did_the_windows_2000_source_leak_contribute_in/