Tuesday 17 November 2026 · UTC
Global

Your region, kept on this device.

GitGuardian extends its Good Samaritan disclosure program to enterprise security teams

Compiled by RedTeamDaily · AI-assisted summaries · Human review not recorded for this version

Published

Read GBHackers report

What happened

Passwords and access keys are sometimes left publicly visible in online code repositories, where attackers can find and use them. has launched a program that finds serious leaks, traces them to the affected companies, and warns the security teams who can cut off access.

Like I’m new · Written by AI from 2 sources · Report an error

Sources
2

Sources and verification

Sources and editorial review

No named human review has been recorded for this story. See the source evidence below.

No vendor or government source is linked to this story yet. Read the source reports; attribution is not independent verification.

How severity and exploitation labels work · All source reports · Report an error

What to do

  1. Check whether your organisation's credentials are exposed on public GitHub, for example with GitGuardian's GitHub Security Audit.
  2. Revoke any exposed credentials that are found.
  3. Publish a security.txt file and a monitored security inbox so external researchers can report disclosures.

Written by AI from the sources, checked against them

Source timeline (UTC) · 2 updates

  1. Mon 16 NovemberLeaked Credentials Are an Enterprise Problem: GitGuardian Extends Its Good Samaritan Program to Security TeamsGBHackers
  2. Leaked Credentials Are an Enterprise Problem: GitGuardian Extends Its Good Samaritan Program to Security TeamsCyber Security News

Explore this report

Ask AI about this story

Optional follow-up answers generated from our coverage. Check the linked sources before acting.

Ask your own question

Who and what is in it

Report a problem