Attributed metadata history
Up to 100 retained publisher events per page for 88b114b3783777f86ddd879f3dc9ed5ce7a9dc4e54f62332a5e7ab34d286d2f7. Withdrawals and unavailable references remain attributed to their publishers.
intelligence_src_c25d91fa3ad9ae9ac7
observed · 2026-10-12 14:53:03 UTC
available
Fingerprint: 0a2f1bebc7ea800736eafab237a0ddecfb8797a02d23951e8aa80935e2f3446f
intelligence_src_c25d91fa3ad9ae9ac7
observed · 2026-10-12 14:53:03 UTC
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.
Fingerprint: c89195baf57fb6f39e235801195d3be0fc4a112674579e7bd1c4558a5005f009