CONFERENCE On Demand: Cyber AI & Automation Summit - Watch Now
Connect with us

Hi, what are you looking for?


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]

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.

Advertisement. Scroll to continue reading.

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.

Click to comment

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 us as we delve into the transformative potential of AI, predictive ChatGPT-like tools and automation to detect and defend against cyberattacks.


As cybersecurity breaches and incidents escalate, the cyber insurance ecosystem is undergoing rapid and transformational change.


Expert Insights

Related Content

Application Security

Cycode, a startup that provides solutions for protecting software source code, emerged from stealth mode on Tuesday with $4.6 million in seed funding.

Identity & Access

Zero trust is not a replacement for identity and access management (IAM), but is the extension of IAM principles from people to everyone and...


The private equity firm merges the newly acquired ForgeRock with Ping Identity, combining two of the biggest names in enterprise IAM market.

CISO Strategy

Okta is blaming the recent hack of its support system on an employee who logged into a personal Google account on a company-managed laptop.


Government agencies in the United States have made progress in the implementation of the DMARC standard in response to a Department of Homeland Security...

Identity & Access

Hackers rarely hack in anymore. They log in using stolen, weak, default, or otherwise compromised credentials. That’s why it’s so critical to break the...

Email Security

Many Fortune 500, FTSE 100 and ASX 100 companies have failed to properly implement the DMARC standard, exposing their customers and partners to phishing...