High severityMulti-languageHardcoded SecretsHIGH confidence
GITLAB PAT
A GitLab personal access token (glpat-) appears to be hard-coded.
Standards mapping
- OWASP ASVS
- V6.4.1 (L2)
Vulnerable vs. safe
Flagged by this check
gitlab_token = glpat-00000000000000000000Passes - the safe pattern
gitlab_token = glpat-shortWhy it matters & how to fix it
A GitLab personal access token (glpat-) appears to be hard-coded. Revoke it in GitLab and inject tokens via CI/CD variables or a secrets manager.
References
Rule ID integsec.generic.secrets.gitlab-pat - engine: Opengrep - license: MIT - Copyright (c) IntegSec Inc.
TurboPentest runs this check automatically
Connect a GitHub repo and this check runs on every white-box pentest - AI-validated and reported with proof, from $99 per target.
Start a pentestRelated checks
- JavaScript / TypeScript - Hardcoded SecretsBasic Auth Credentials In URL
- JavaScript / TypeScript - Hardcoded SecretsDB Connection String With Credentials
- JavaScript / TypeScript - Hardcoded SecretsHardcoded Credential String
- JavaScript / TypeScript - Hardcoded SecretsHardcoded Crypto Key Or IV
- Python - Hardcoded SecretsBasic Auth Credentials In URL
- Python - Hardcoded SecretsDB Connection String Credentials