An internal reporting service accepts this token and trusts it completely.
Its signing key was generated by a developer in a hurry from a short list of "good enough" strings. Those were the twenty candidates:
Work out which one actually signs this token. Recompute
Submit the secret, not the token.
code
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJzdmMtcmVwb3J0aW5nIiwicm9sZSI6InVzZXIiLCJpc3MiOiJudWxsaGF2ZW4taW50ZXJuYWwiLCJpYXQiOjE3NjMyMDAwMDB9.TA8xs8tQGDgRV34VwLydFkAOXU8I78HJI0WWHZoIg6EIts signing key was generated by a developer in a hurry from a short list of "good enough" strings. Those were the twenty candidates:
markdown
- auth-key
- changeme
- dev-key-2026
- hunter2
- internal-api
- jwt-secret
- k3y-2026
- letmein
- m3tadata-s3rvice-k3y
- metadata-service-key
- my-secret-key
- nullhaven
- production
- qwerty123
- reporting
- s3cr3t
- s3rvice-k3y
- service-account
- supersecret
- svc-reportingWork out which one actually signs this token. Recompute
HMAC-SHA256(key, header + "." + payload), base64url-encode it, and compare with the third part.Submit the secret, not the token.