{"id":39640,"date":"2021-02-18T17:44:00","date_gmt":"2021-02-18T17:44:00","guid":{"rendered":"http:\/\/f9d37452-436f-4f6b-9474-872418b21ca4"},"modified":"2021-02-18T17:44:00","modified_gmt":"2021-02-18T17:44:00","slug":"microsoft-says-solarwinds-hackers-downloaded-some-azure-exchange-and-intune-source-code","status":"publish","type":"post","link":"https:\/\/www.threatshub.org\/blog\/microsoft-says-solarwinds-hackers-downloaded-some-azure-exchange-and-intune-source-code\/","title":{"rendered":"Microsoft says SolarWinds hackers downloaded some Azure, Exchange, and Intune source code"},"content":{"rendered":"
\"Microsoft\"<\/span>
<\/span> Image: Microsoft <\/span><\/figcaption><\/figure>\n

Microsoft’s security team said today it has formally completed its investigation into its SolarWinds-related breach and found no evidence that hackers abused its internal systems or official products to pivot and attack end-users and business customers.<\/p>\n

\n

ZDNet Recommends<\/span> <\/h3>\n<\/p><\/div>\n

The OS maker began investigating the breach in mid-December after it was discovered that Russian-linked hackers breached software vendor SolarWinds<\/a> and inserted malware inside the Orion IT monitoring platform, a product that Microsoft had also deployed internally.<\/p>\n

In a blog post published on December 31, Microsoft said it discovered that hackers used the access they gained through the SolarWinds Orion app to pivot to Microsoft’s internal network, where they accessed the source code<\/a> of several internal projects.<\/p>\n

“Our analysis shows the first viewing of a file in a source repository was in late November and ended when we secured the affected accounts,” the company said today, in its final report<\/a> into the SolarWinds-related breach.<\/p>\n

Microsoft said that after cutting off the intruder’s access, the hackers continued to try to access Microsoft accounts throughout December and even up until early January 2021, weeks after the SolarWinds breach was disclosed, and even after Microsoft made it clear they were investigating the incident.<\/p>\n

“There was no case where all repositories related to any single product or service was accessed,” the company’s security team said today. “There was no access to the vast majority of source code.”<\/p>\n

Instead, the OS maker said intruders viewed “only a few individual files […] as a result of a repository search.”<\/p>\n

<\/section>\n

Microsoft said that based on the search queries attacker performed inside their code repositories, the intruders appeared to have been focused on locating secrets (aka access token) that they could be used to expand their access to other Microsoft systems.<\/p>\n

The Redmond company said these searches failed because of internal coding practices that prohibited developers from storing secrets inside source code.<\/p>\n

Some source code was also downloaded<\/h3>\n

But beyond viewing files, the hackers also managed to download some code. However, Microsoft said the data was not extensive and that the intruders only downloaded the source code of a few components related to some of its cloud-based products.<\/p>\n

Per Microsoft, these repositories contained code for:<\/p>\n