High severityGoHardcoded SecretsMEDIUM confidence
Hardcoded API Key Token
An API key, access/refresh token, or signing secret appears to be hardcoded as a string literal (CWE-798/CWE-522).
Standards mapping
- OWASP ASVS
- V6.4.1 (L2)V2.10.4 (L2)
Vulnerable vs. safe
Flagged by this check
apiKey := "sk_live_0000000000000000000FAKE"Passes - the safe pattern
apiKey := os.Getenv("API_KEY")Why it matters & how to fix it
An API key, access/refresh token, or signing secret appears to be hardcoded as a string literal (CWE-798/CWE-522). Hardcoded secrets leak through source control, binaries, and backups and cannot be rotated without a code change. Load the value from an environment variable or a secrets manager (Vault, AWS/GCP Secret Manager) at runtime, and rotate any value that was committed.
References
Rule ID integsec-go-hardcoded-api-key-token - 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