{"id":39166,"date":"2021-01-12T19:35:06","date_gmt":"2021-01-12T19:35:06","guid":{"rendered":"https:\/\/www.threatshub.org\/blog\/solarwinds-malware-was-sneaked-out-of-the-firms-orion-build-environment-6-months-before-anyone-realised-it-was-there-report\/"},"modified":"2021-01-12T19:35:06","modified_gmt":"2021-01-12T19:35:06","slug":"solarwinds-malware-was-sneaked-out-of-the-firms-orion-build-environment-6-months-before-anyone-realised-it-was-there-report","status":"publish","type":"post","link":"https:\/\/www.threatshub.org\/blog\/solarwinds-malware-was-sneaked-out-of-the-firms-orion-build-environment-6-months-before-anyone-realised-it-was-there-report\/","title":{"rendered":"SolarWinds malware was sneaked out of the firm’s Orion build environment 6 months before anyone realised it was there \u2013 report"},"content":{"rendered":"

The malware that was utilised to hack SolarWinds checked to see whether software used to compile the firm’s Orion product was running before deploying its payload, according to Crowdstrike.<\/p>\n

In a blog post late last night, the infosec firm said the Orion-targeting malware<\/a>, which it codenamed Sunspot, had “several safeguards” to ensure its deployment of compromised code into new Orion builds didn’t trigger SolarWinds’ suspicions.<\/p>\n