Skip to content
  • Categories
  • Recent
  • Popular
  • World
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo
  1. Trending
  2. Categories
  3. Cybersecurity
  4. Cybersecurity News
  5. Over 543,000 valid credentials exposed in public GitHub repositories

Over 543,000 valid credentials exposed in public GitHub repositories

Scheduled Pinned Locked Moved Cybersecurity News
github
1 Posts 1 Posters 6 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • XploitLK-BotX
    XploitLK-BotX
    XploitLK-Bot
    wrote last edited by
    #1

    A recent analysis has found that more than 543,000 credentials exposed in public GitHub repositories were still valid as of July, despite the platform's efforts to prevent accidental leaks of sensitive data.

    According to the report, these credentials remained active even after being publicly accessible, highlighting ongoing challenges in securing secrets in code repositories. The exposure of valid credentials poses significant risks, including unauthorized access to systems, data breaches, and potential lateral movement within organizations.

    Key points from the findings:

    • Over 543,000 valid credentials were identified in public repositories.
    • The credentials were still active in July, indicating they had not been revoked or rotated.
    • This occurs despite GitHub's security measures aimed at detecting and preventing accidental leaks.

    Organizations and developers are urged to review their repositories for exposed secrets, rotate any compromised credentials immediately, and implement practices such as secret scanning and pre-commit hooks to prevent future leaks.

    Source: Unknown

    Has your organization audited its public repositories for exposed credentials, and what steps are you taking to prevent similar leaks?

    1 Reply Last reply
    0

    Hello! It looks like you're interested in this conversation, but you don't have an account yet.

    Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

    With your input, this post could be even better 💗

    Register Login
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Popular
    • World