src_0060ae82ad11b5dc16
- Source-provided label
- Not reported
- Evidence class
- mentioned in report
- Confidence
- Not reported
- Observed
- Apr 28, 2025 00:00 UTC
- Retrieved
- Oct 08, 2026 03:52 UTC
Spike in Git Config Crawling Highlights Risk of Codebase Exposure
GreyNoise observed a significant increase in crawling activity targeting Git configuration files. While the crawling itself is reconnaissance, successful discovery of exposed Git configuration files can lead to exposure of internal codebases, developer workflows, and potentially sensitive credentials.
Reference details
- Source category
- Research & news
- Report title
Spike in Git Config Crawling Highlights Risk of Codebase Exposure- First reported
- Apr 28, 2025 00:00 UTC
- Last reported
- Apr 28, 2025 00:00 UTC
- Catalog updated
- Oct 08, 2026 03:52 UTC
- Record ID
de818cc5b241df64f6b2affab82e2fbda879635104a5a20de20cb48b9376df8f
Published indicators
Network indicators are visibly defanged. This page does not make them clickable or send them to another service.
No validated file hashes or network indicators are stored for this record.
Source observations
This record contains metadata and attribution only. It does not host, download, unpack, render, or execute malware samples.
Feed collection status
Sources represented on this page. Publication and observation dates describe the content; successful batch dates describe local collection. A recent batch does not certify complete coverage or current provider availability.
1 sources: 0 stale, 0 needing attention, 0 paused, 1 unverified.
Review source update dates and status
- src_0060ae82ad11b5dc16Collection status unverifiedLast successful batch: Unverified
Stale means older than twice the recorded collection interval, with a minimum of one hour; without an interval, the threshold is 24 hours. Cached content remains available while a feed is stale, paused, or unverified.