Money Forward, a major Japanese provider of personal finance and accounting software, disclosed on May 1 that a third party had used leaked GitHub credentials to access its account and copy repositories. The company suspended its bank API integrations as a precaution, and many Japanese users lost account aggregation for several days.
What happened
The attacker copied repositories that hold source code for Money Forward group services. The company says the code may have been viewed, and that authentication keys and passwords embedded in it were exposed. One repository also held personal data that should not have been there. A file with the cardholder names (in Latin characters) and last four digits of 370 Money Forward Business Card cards, issued by subsidiary Money Forward Kessai, had been saved to GitHub outside normal procedures during an update. Money Forward calls this human error.
Full card numbers, expiry dates and security codes were not exposed. The company also found no leak of linked bank login data and no fraudulent card use. As of its May 11 update, it had found no leak or tampering in production databases.
Response
- Money Forward revoked the compromised credentials, blocked the account, and invalidated and reissued the keys and passwords found in the code. By early May this work was largely complete.
- It suspended financial-institution API integrations from May 1 and reconnected them in stages from mid-May.
- It reported the incident to the police, Japan’s Personal Information Protection Commission and other authorities, and contacted affected cardholders individually.
- On June 23 it announced that its detailed investigation was complete and published a further report on root cause and prevention.
Lessons for development teams
A single leaked developer credential exposed both intellectual property and production secrets, because secrets and personal data were stored in source control.
Recommendations
- Require SSO with phishing-resistant MFA on GitHub organisations, and prefer short-lived, fine-grained tokens over long-lived personal access tokens.
- Turn on secret scanning and push protection. Move embedded keys into a secrets manager and rotate anything that has ever been committed.
- Scan repositories for personal data and block files containing it with pre-commit or CI checks.
- Review GitHub audit logs for bulk clones and new token activity, and alert on clones from unfamiliar IPs.