Connect with us

Hi, what are you looking for?

SecurityWeekSecurityWeek

Application Security

GitHub Starts Scanning for Exposed Package Registry Credentials

GitHub this week announced that it has started scanning code hosted on its platform for package registry credentials, including RubyGems and PyPI secrets.

GitHub this week announced that it has started scanning code hosted on its platform for package registry credentials, including RubyGems and PyPI secrets.

The scanning is performed via GitHub secret scanning, a service meant to identify exposed secrets in pushes to repositories. Active since 2015, the service can look for more than 70 different secret types in both public and private repositories.

The focus of the service is to keep not only open-source code secure, but also the software that relies on that code. Secrets left exposed in the code could allow malicious actors to access developer accounts and make unwanted changes to code.

Malicious modifications to open-source packages could impact millions of products, including other open source packages. Threat actors often target this supply chain to compromise an application or organization of interest.

“Scanning for supply chain secrets is important because unlike with other secrets, where exposing the secret impacts only one account, an exposed supply chain secret can potentially impact millions of downstream software applications and their users,” GitHub says.

[Also read: Library Dependencies and the Open Source Supply Chain Nightmare]

Advertisement. Scroll to continue reading.

The scanning service now looks for package registry credentials that developers use to sign into package management services.

GitHub secret scanning has started looking for RubyGems and PyPI secrets, but it also supports scanning for npm, NuGet, and Clojars secrets. In total, it can scan for potentially leaked tokens in roughly 2.3 million packages hosted by these services.

GitHub secret scanning automatically scans new commits to repositories and, if it identifies an exposed secret, it notifies the registry of the leak, for that secret to be revoked. The registry then notifies the developer of the compromised secret.

Related: New Google Tool Helps Developers Visualize Dependencies of Open Source Projects

Related: Adobe Releases Open Source Anomaly Detection Tool “OSAS”

Related: Google Launches Database for Open Source Vulnerabilities

Written By

Ionut Arghire is an international correspondent for SecurityWeek.

Daily Briefing Newsletter

Subscribe to the SecurityWeek Email Briefing for the latest cybersecurity threats, trends, and expert insights.

Click to comment

Trending

Daily Briefing Newsletter

Subscribe to the SecurityWeek Email Briefing to stay informed on the latest threats, trends, and technology, along with insightful columns from industry experts.

Join as speakers examine the various components of ASM strategy, the push to mandate continuous asset visibility and inventory tools, and the use of red-teaming, bug bounties and pen-tests in modern security programs.

Register

In this live webinar, learn how to define your minimum viable business, identify the systems it depends on, measure actual recovery time against business requirements, and present the gaps to the board as measurable risk.

Register

People on the Move

Tom Bonos has been named Chief Revenue Officer at Sumo Logic.

Axonius has appointed Chris Jones as CTSO and Dan Schoenbaum as SVP of Business Development.

Optiv has appointed Sean Forkan as Chief Revenue Officer (CRO).

More People On The Move

Expert Insights

Daily Briefing Newsletter

Subscribe to the SecurityWeek Email Briefing to stay informed on the latest cybersecurity news, threats, and expert insights. Unsubscribe at any time.