GitHub: Hackers steal information from dozens of organizations' private leavers

GitHub announced that hackers could gain access tokens through a cloud service and a CI service, allowing access to the private locks of dozens of companies and organizations, including NPM. Fear: Information will be the basis for more attacks

Source: Unsplash

There are often stories of malicious code debugging, which was found on GitHub servers and from there onto the computers of innocent users. A new case reveals new loopholes related to the open source home Acquired by Microsoft in 2018 – The allegations at the moment are that companies that generally offer third-party services have not done a good job of retaining customers.

Fear: Hackers will use the information for further attacks

Last Tuesday, GitHub updated over the weekend about a new security breach identified by its security teams. According to the report, hackers were able to gain access to the privacy of dozens of companies, including NPM. The problem was not with GitHub’s security capabilities, but instead with the use of two third – party services: Heroku and Travis CI.

Both services, which offer cloud (Rocco) and Continuity Integration (CI) services, allow hackers to access the OAuth Open Security Protocol tokens. The hackers who gained access to these tokens were able to gain access to the private debugging of many GitHub users, according to a post on the GitHub blog about infringement.

In the post Mike Hanley, GitHub’s director of security, wrote that the company had deactivated the “burned” tokens as soon as the attack was discovered. According to Annie, security analysts at the company’s security apparatus believe that the attackers have exploited loopholes and access keys in an attempt to steal as much information as possible from the private recruits who gave them access and turn it into an attack. Locator about additional infrastructure.

He added that hackers’ access to NPMs allowed them to download information from private recovery on GitHub, while at the same time allowing hackers to gain access to packages stored on AWS. To S3, Amazon’s storage service.

GitHub itself, as it appears from Hanley’s post, was not immediately available for comment – and hackers had no access to download information from Github.com’s private recovery. In addition, Hanley says the attackers were only seen removing information from the bounty they had access to and making no changes to it. He goes on to say that the details of the users – including their login details to the site – were not disclosed in the attack.

Demi Ben-Ari, CTO and one of the founders of Startup Panorace, said the damage caused by the breach could be very serious. At the same time, it could harm the functionality of their products – as GitHub thought – because hackers could use the information to turn them into new attack locators. “Many times companies have their own personal involvement on GitHub so there shouldn’t be a lot of access information to their other services and much more – the harm is very significant,” Ben-Ari added.