intelligence_src_c25d91fa3ad9ae9ac7
- Source-provided label
- Publisher RSS metadata
- Evidence class
- mentioned in report
- Confidence
- Not reported
- Observed
- Feb 28, 2022 11:22 UTC
- Retrieved
- Oct 16, 2026 04:13 UTC
Gitlab Reconnaissance Introduction
Although Gitlab is not as popular as Github, it’s common to run across it these days. Especially after Microsoft acquired Github it seemed more individuals and organizations flocked over to Gitlab. In this post I want to document a couple of recon commands that are useful post-exploitation, and for blue teamers to watch out for. Let’s assume one has access to a Gitlab Token as a precursor. Let’s walk through some interesting commands and script snippets to leverage to find out more.
Reference details
- Source category
- research-report
- First reported
- Feb 28, 2022 11:22 UTC
- Last reported
- Feb 28, 2022 11:22 UTC
- Catalog updated
- Oct 16, 2026 04:13 UTC
- Record ID
88b114b3783777f86ddd879f3dc9ed5ce7a9dc4e54f62332a5e7ab34d286d2f7
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, 0 unverified.
Review source update dates and status
- intelligence_src_c25d91fa3ad9ae9ac7Recent successful batchLast successful batch: Last attempt:
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.