Friday, March 29, 2024

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

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

Website

Latest articles

GoPlus’s Latest Report Highlights How Blockchain Communities Are Leveraging Critical API Security Data To Mitigate Web3 Threats

GoPlus Labs, the leading Web3 security infrastructure provider, has unveiled a groundbreaking report highlighting...

Wireshark 4.2.4 Released: What’s New!

Wireshark stands as the undisputed leader, offering unparalleled tools for troubleshooting, analysis, development, and...

Zoom Unveils AI-Powered All-In-One AI Work Workplace

Zoom has taken a monumental leap forward by introducing Zoom Workplace, an all-encompassing AI-powered...

iPhone Users Beware! Darcula Phishing Service Attacking Via iMessage

Phishing allows hackers to exploit human vulnerabilities and trick users into revealing sensitive information...

2 Chrome Zero-Days Exploited at Pwn2Own 2024: Patch Now

Google has announced a crucial update to its Chrome browser, addressing several vulnerabilities, including...

The Moon Malware Hacked 6,000 ASUS Routers in 72hours to Use for Proxy

Black Lotus Labs discovered a multi-year campaign by TheMoon malware targeting vulnerable routers and...
Guru baran
Guru baranhttps://gbhackers.com
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.

Mitigating Vulnerability Types & 0-day Threats

Mitigating Vulnerability & 0-day Threats

Alert Fatigue that helps no one as security teams need to triage 100s of vulnerabilities.

  • The problem of vulnerability fatigue today
  • Difference between CVSS-specific vulnerability vs risk-based vulnerability
  • Evaluating vulnerabilities based on the business impact/risk
  • Automation to reduce alert fatigue and enhance security posture significantly

Related Articles