Back to All Scenarios
PASSEDsecurity / leaked_credentials
Database Credentials Committed to Public Git Repo
GitHub Secret Scanning detected production database credentials committed to a public repository. Credentials are for the production PostgreSQL instance.
Pattern
UNKNOWN
Expected: CREDENTIAL_LEAK
Severity
MEDIUM
Confidence
68%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | CREDENTIAL_LEAK | UNKNOWN | |
| Severity Assessment | CRITICAL | MEDIUM | |
| Incident Correlation | N/A | None | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Auto-Heal — Corax resolves autonomously |
Scenario Conditions
GitHub public repository. .env file committed with DATABASE_URL containing production credentials. Secret scanning alert fired. Credentials have read-write access to production DB.
Injected Error Messages (1)
LEAKED CREDENTIALS — GitHub Secret Scanning alert: production PostgreSQL credentials found in public repo commit abc1234, DATABASE_URL with password exposed, credential has read-write access to production database
Neural Engine Root Cause Analysis
Unrecognized error pattern — this may be a new type of failure not yet cataloged.
Remediation Plan
Trigger autonomous healing to diagnose and fix. Manual investigation may be needed if healing cannot resolve.
Improvements Applied
- Pattern unrecognized — consider adding keywords for CREDENTIAL_LEAK
- Severity: MEDIUM (expected CRITICAL)
Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnoo5z0016lig7iayk5ysh