SolarWinds hackers accessed Microsoft source code
The firm doesn't consider this as an elevation of risk due to its open source development best practices
The cyber criminals that compromised SolarWinds in a sophisticated supply chain cyber attack broke into Microsoft and accessed the company’s source code as the list of confirmed victims expands beyond 250.
Microsoft confirmed that the attackers, linked by US authorities to the Russian state, accessed source code repositories as part of the attack, but didn’t alter the codebase at the heart of the firm’s core products and services. They did so through an internal account that had permissions to view, but not edit, these repositories.
The company has suggested, however, that viewing access to source code isn’t tied to an elevation of risk due to the firm’s use of open source development best practices, which allows source code to be viewable by employees.
It was previously reported by Reuters that the hackers had compromised Microsoft as part of its efforts to load SolarWinds’ Orion security platform with malware, although the company denied that its own software was, in turn, used to attack others.
This is despite a Securities and Exchange Commission (SEC) filing revealing that Microsoft Office 365 accounts of SolarWinds employees were broken into. SolarWinds suggested, according to this document, that it was aware of an attack vector used to compromise the company’s emails, with this intrusion also granting attackers access to other data contained in its Microsoft-developed productivity suite.
The news comes as the list of confirmed victims of the gigantic hack continues to expand, with more than 250 US government agencies and businesses having been compromised, according to the New York Times.
Although hackers effectively gained access to the networks of 18,000 SolarWinds public sector and business customers when they compromised the Orion security platform, probes were thought to have been sent to only a few dozen. This figure of 250, which the publication ascertained through multiple interviews, represents a much broader pool of potential victims.
The monster hack first emerged last month after FireEye disclosed that it had been compromised by foreign hackers, who made off with advanced penetration tools. Only afterwards did the US Cybersecurity and Infrastructure Security Agency (CISA), as well as Microsoft, warn of a supply chain attack involving SolarWinds.
In the immediate aftermath of the revelations, Microsoft went so far as to block its customers from accessing malicious SolarWinds binaries for the compromised Orion platform. The company had previously released detections alerting users to the presence of these binaries, with a recommendation to isolate and investigate flagged devices.
Managing security risk and compliance in a challenging landscape
How key technology partners grow with your organisationDownload now
Evaluate your order-to-cash process
15 recommended metrics to benchmark your O2C operationsDownload now
AI 360: Hold, fold, or double down?
How AI can benefit your businessDownload now
Getting started with Azure Red Hat OpenShift
A developer’s guide to improving application building and deployment capabilitiesDownload now