How to fix: Hard-coded secret values in source
API keys, tokens, or secret strings are embedded directly in the source code.
Why it matters
Secrets embedded in source code are committed to version history, included in build artifacts, and potentially exposed in client-side bundles, giving anyone with the code or the deployed JS file access to your third-party services, databases, and APIs.
Secrets in source are nearly impossible to fully remove once committed: use environment variables and rotate immediately.
How to fix it
- 1Remove the secret from source code and git history (BFG Repo Cleaner)
- 2Move to environment variables or a secrets manager
- 3Rotate the exposed secret immediately
Code examples
Remove secrets from source and use environment variables
# Scan for secrets before committing
npx gitleaks detect --source . --no-git
# Or use git-secrets:
git secrets --scan
# Move secrets to environment:
# .env.local (git-ignored)
API_KEY="your-actual-key-here"
# Rotate any keys already committed to history:
# git filter-branch or BFG Repo Cleaner to remove from historyReferences
Detected automatically by VulnRadar. The check id is hardcoded-secrets, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is Hard-coded secret values in source?
- VulnRadar rates this critical severity in the code category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id hardcoded-secrets, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Hard-coded secret values in source map to?
- It maps to CWE-798. In the OWASP Top 10 it falls under A07:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.