You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Low — A (87/100)
Azure Tenant/Client ID (GUID) exposed, validity undetermined.
Published in the public commit stream, which harvesters also read.
Based on public commits only — the full git history may hold more.
Hi, I'm Cr0c0 : I run independant automated scans over public github repos looking for leaked credentials, and I found this.
I found Azure Tenant/Client ID (GUID) in the following commit : 0fb8e37. It looks likely active.
Im sorry for you but once a key is exposed in a public commit, it's compromised, even deleting it after won't help since it stays in git history. You need to rotate it now to be safe.
Note
Low — A (87/100)
Azure Tenant/Client ID (GUID) exposed, validity undetermined.
Based on public commits only — the full git history may hold more.
Hi, I'm Cr0c0 : I run independant automated scans over public github repos looking for leaked credentials, and I found this.
I found Azure Tenant/Client ID (GUID) in the following commit : 0fb8e37. It looks likely active.
Im sorry for you but once a key is exposed in a public commit, it's compromised, even deleting it after won't help since it stays in git history. You need to rotate it now to be safe.
I did a short report of this leak if you wants to know how to delete it : https://leakwatch.net/r/gsCY1DhPfIm9ixtg (you don't need to login to see it).
Stay safe.