DO NOT report security vulnerabilities through public GitHub issues.
Instead, please report them via email to: [your-security-email@example.com]
Include as much information as possible:
- Type of issue (credential leak, vulnerability, etc.)
- Affected files or components
- Steps to reproduce
- Potential impact
GitHub Secret Scanning has detected exposed credentials in the repository history. These credentials have been:
- Revoked/Rotated (action required by repository owner)
- Removed from current files (completed)
- Added to .gitignore (completed)
-
MongoDB Atlas Credentials:
- Go to MongoDB Atlas
- Navigate to Database Access → Your User
- Click "Edit" → "Edit Password"
- Generate new secure password
- Update local
.envfiles with new credentials
-
Google API Keys (Firebase):
- Go to Google Cloud Console
- Navigate to APIs & Services → Credentials
- Find the exposed API keys and click "Delete"
- Create new API keys with proper restrictions:
- Application restrictions: HTTP referrers (websites)
- API restrictions: Limit to required APIs only
- Download new
google-services.jsonandGoogleService-Info.plist - Add to local project (never commit!)
-
Git History Cleanup (Optional but Recommended):
# Use BFG Repo-Cleaner to remove secrets from git history # https://rtyley.github.io/bfg-repo-cleaner/ # Or use git-filter-repo (recommended by GitHub) # https://github.com/newren/git-filter-repo
- ❌ API keys
- ❌ Database passwords
- ❌ OAuth tokens
- ❌ Private keys
- ❌ Firebase config files
- ❌
.envfiles with real credentials
- ✅ Environment variables (
.env.exampleas template) - ✅ GitHub Secrets for CI/CD
- ✅ Secret management services (AWS Secrets Manager, HashiCorp Vault)
- ✅
.gitignorefor sensitive files - ✅ Git hooks to prevent accidental commits
- Copy
.env.exampleto.env - Fill in your local credentials in
.env - Never commit
.envfile - Use different credentials for dev/staging/production
// firebase_options.dart should be generated locally
// Run: flutterfire configure
// Add to .gitignore: **/firebase_options.dart- All exposed credentials have been rotated
-
.gitignoreupdated to prevent future leaks - GitHub Secret Scanning alerts reviewed and closed
- Team members notified about security best practices
- CI/CD updated to use GitHub Secrets
- Documentation updated with security guidelines