The Key to Every Member Card Was Public

Contributors

Shantanoo Govilkar
Shantanoo Govilkar
SVP Strategic Solutions Risk & Cybersecurity Solutions

A credit union built card freeze and spending alerts on its processor's API. During an external test, testers searched public code sites and found a contractor's old project. Inside sat a live production key with control over every member card.

AT A GLANCE

  • Industry: Credit union with its own debit card program
  • Test type: External test with a public footprint sweep
  • Severity: Critical, CVSS 9.1
  • Outcome: Key rotated within hours, secrets moved to a vault

Launching a debit card program meant new integrations, new contractors, and new code. The security team wanted to see everything an outsider could find, including what lived beyond the credit union's own systems.

What's Inside the Case Study

  • Where testers found the key, and why internal scans would never see it
  • How one safe, read-only call confirmed the key worked in production
  • What the key could change on every member card
  • What card fraud costs once recovery and operations count
  • How the credit union rotated the key within hours and locked down every repository
exposed-card-api-key-case-study
Back
to Top