Files
nick-doc/Issues/ISSUE-079-frontend-telegram-bot-token-committed-in-gitleaks-toml-allowli.md
Siavash Sameni dceaf82934 audit: 2026-05-30 full-codebase audit — report, issues, docs, runbooks
Full-codebase-audit 2026-05-30 outputs:
- Audit report: 09 - Audits/Full Codebase Audit - 2026-05-30.md
- 81 issue files ISSUE-055..135 (decisions + 1 skipped no-brainer).
- Scanner docs from scratch (was zero): architecture, data model, API ref, payment
  flow, operations runbook + repo README.
- Doc-sync updates across API reference, data models, flows, design system.
- Secret Rotation Runbook (08 - Operations) for the exposed credentials.
- Reusable workflow guide (07 - Development) + .claude/workflows/full-codebase-audit.js.

Issues remain status:open intentionally — the code fixes are uncommitted-then-committed
working-tree changes per repo and aren't "resolved" until merged/deployed.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-05-30 18:48:04 +04:00

1.4 KiB

issue, title, severity, domain, labels, status, created, source
issue title severity domain labels status created source
079 Frontend: Telegram bot token committed in .gitleaks.toml allowlist — must rotate high Security
security
frontend
secrets
rotation-required
open 2026-05-30 Full Codebase Audit 2026-05-30

Frontend: Telegram bot token committed in .gitleaks.toml allowlist — must rotate

Severity: high Domain: Security Labels: security, frontend, secrets, rotation-required

Description

frontend/.gitleaks.toml:15 contains a value-based allowlist entry with the plaintext Telegram bot token. Value-based allowlist entries in gitleaks effectively publish the secret in the allowlist itself. The same token appears in the backend .env.development (see ISSUE-074).

Options

  1. Replace the value-based allowlist with a path/commit-hash allowlist and rotate the token.
  2. Remove the allowlist entry entirely after scrubbing the secret from source.
  3. Use the handle-gitleaks workflow to triage and remediate.

Recommendation

Rotate the token, switch to a non-value-based allowlist (path/fingerprint), and scrub history. Coordinate with backend ISSUE-074 since the same token appears there.

Affected Files

  • frontend/.gitleaks.toml:15

References