Git configuration files usually include sensitive information such as user email addresses, access tokens, authentication credentials, and remote repository URLs that embed usernames or tokens.

Threat actors are intensifying internet-wide scanning for Git configuration files that can reveal sensitive secrets and authentication tokens used to compromise cloud services and source code ...

Build artifacts generated by GitHub Actions often contain access tokens that can be abused by attackers to push malicious code into projects or compromise cloud infrastructure.