Attack Interview 01 — The recruiter and the borrowed Git history
A LinkedIn take-home led to two poker repositories. Their source files matched an open-source game, while hundreds of Git snapshots matched an unrelated TCP utility.
One thread in the notebook
security.
3 entries on this subject. Browse everything →
Attack Interview 02 — What could run before the login screen
The execution trace from a VS Code folder-open task and an npm lifecycle hook to a five-second HTTP beacon and a separate environment POST.
Attack Interview 03 — Indicators and what to look for
Defanged endpoints from the saved Git history, the evidence linking each to a code path, and what to look for in endpoint and network logs.
