inquire
Case files/BREACH
BREACH · SYNTHETIC CASESynthetic

From corporate domain to exposed dev credentials

Client asked 'are we in stealer logs?' Automated scanners said no. Manual Hudson + stealer correlation found a contractor Jenkins token in a combo list.

5 min readInquire desk

Investigation log

  1. Step 01 — Automated pass

    Aggregate breach APIs returned clean for @company.tld mailboxes.

  2. Step 02 — Stealer pivot

    Domain-scoped infostealer index hit contractor laptop dump — not employee SSO.

  3. Step 03 — Validate

    Token format matched internal CI; last commit timestamp aligned with dump date.

This case is synthetic and declassified for training purposes. Methodology reflects how Inquire analysts work; identifiers and locations are fictional.