Medium severityMulti-languageHardcoded SecretsMEDIUM confidence
Hardcoded JWT
A hard-coded JSON Web Token (eyJ...) appears in source.
Standards mapping
- OWASP ASVS
- V6.4.1 (L2)
Vulnerable vs. safe
Flagged by this check
jwt = eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiIwMDAwMDAwMCJ9.0000000SIGNATUREEXAMPLE00000Passes - the safe pattern
jwt = not.a.jwtWhy it matters & how to fix it
A hard-coded JSON Web Token (eyJ...) appears in source. If it is a live token it grants access until expiry; revoke/rotate it and obtain tokens at runtime rather than embedding them.
References
Rule ID integsec.generic.secrets.hardcoded-jwt - 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