Thursday, December 19, 2024
HomeCyber AttackSolarWinds CEO Blames Intern for 'solarwinds123' Password Leak that Led to Biggest...

SolarWinds CEO Blames Intern for ‘solarwinds123’ Password Leak that Led to Biggest Cyber Attack in 2020

Published on

SIEM as a Service

“solarwinds123”, the password that is believed to be the root cause of the biggest cyber hack of 2020. Top executives of Texas-based software company SolarWinds have laid the blame at the feet of an intern for a critical password lapse that was noticed by anyone for several years.

This is the latest piece of information to come out in the SolarWinds supply chain attack that is believed to have affected more than 18,000 customers of SolarWinds.

The password “solarwinds123” is believed to have been publicly accessible via a GitHub repository since June 17, 2018, before it was addressed on November 22, 2019.

- Advertisement - SIEM as a Service

CEO Sudhakar Ramakrishna appeared in a hearing before the House Committees on Oversight and Reform and Homeland Security on SolarWinds on Friday, and he had testified that the password has been in use as early as 2017.

SolarWinds’ Orion platform is believed to have been compromised as early as October 2019. This malware was used to introduce the Sunburst backdoor.

Till now, at least 9 government agencies and several private agencies are believed to have fallen victim to this. This attack was deemed so severe that The Cybersecurity and Infrastructure Security Agency (CISA) had advised all government agencies to update the software with immediate effect or to cease using it.

Excerpts from the hearing

“I’ve got a stronger password than ‘solarwinds123’ to stop my kids from watching too much YouTube on their iPad,” Representative Katie Porter of California said. “You and your company were supposed to be preventing the Russians from reading Defense Department emails.”

“I believe that was a password that an intern used on one of his servers back in 2017 which was reported to our security team and it was immediately removed,” Ramakrishna said in response to Porter. Former CEO Kevin Thompson echoed Ramakrishna’s statement during the testimony. “That related to a mistake that an intern made, and they violated our password policies and they posted that password on their own private GitHub account,” Thompson said. “As soon as it was identified and brought to the attention of my security team, they took that down.”

You can follow us on LinkedinTwitterFacebook for daily Cybersecurity, and hacking news updates.

Also Read

SolarWinds Hack – Multiple Similarities Found Between Sunburst Backdoor and Turla’s Backdoor

DOJ Says SolarWinds Hackers Accessed 3% of it’s Office 365 Mailboxes

New Malware Discovered in SolarWinds Attack that Used 7-Zip Code to Hide

Gurubaran
Gurubaran
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.

Latest articles

Beware Of Malicious SharePoint Notifications That Delivers Xloader Malware

Through the use of XLoader and impersonating SharePoint notifications, researchers were able to identify...

Malicious Supply Chain Attacking Moving From npm Community To VSCode Marketplace

Researchers have identified a rise in malicious activity on the VSCode Marketplace, highlighting the...

Hackers Weaponizing LNK Files To Create Scheduled Task And Deliver Malware Payload

TA397, also known as Bitter, targeted a Turkish defense organization with a spearphishing email...

BADBOX Botnet Hacked 74,000 Android Devices With Customizable Remote Codes

BADBOX is a cybercriminal operation infecting Android devices like TV boxes and smartphones with...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

Beware Of Malicious SharePoint Notifications That Delivers Xloader Malware

Through the use of XLoader and impersonating SharePoint notifications, researchers were able to identify...

Malicious Supply Chain Attacking Moving From npm Community To VSCode Marketplace

Researchers have identified a rise in malicious activity on the VSCode Marketplace, highlighting the...

Hackers Weaponizing LNK Files To Create Scheduled Task And Deliver Malware Payload

TA397, also known as Bitter, targeted a Turkish defense organization with a spearphishing email...