High severityMulti-languageHardcoded SecretsHIGH confidence
Google OAuth Token
A Google OAuth 2.0 access token (ya29.) appears to be hard-coded.
Standards mapping
- OWASP ASVS
- V6.4.1 (L2)
Vulnerable vs. safe
Flagged by this check
google_token = ya29.a0000000000000000000000000000000Passes - the safe pattern
google_token = ya29.shortWhy it matters & how to fix it
A Google OAuth 2.0 access token (ya29.) appears to be hard-coded. These are short-lived but should never be committed; rotate/revoke it and obtain tokens dynamically at runtime.
References
Rule ID integsec.generic.secrets.google-oauth-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