Endpoint / Malware

Keylogger Detection & Incident Response

A lab-based investigation focused on suspicious process behavior, file validation, persistence, credential exposure risk and endpoint containment.

ALERT→PROCESS TREE→COMMAND LINE→FILE/HASH→NETWORK→PERSISTENCE→SCOPE→CONTAIN
▶

Video walkthrough pending

Upload your walkthrough to YouTube as Unlisted, then replace YOUR_YOUTUBE_ID in this page to embed it here.

Investigation Timeline

How I would work the incident.

Defender XDRProcess TreesThreat IntelligenceMITRE ATT&CKEndpoint Telemetry
ALERT

Validate the detection, affected host, user, timestamp, severity and initial behavioral evidence.

PROCESS TREE

Review parent/child relationships, execution path, command line, signer and related processes.

FILE / HASH

Check file path, hash reputation, prevalence, creation time and whether the artifact is expected.

NETWORK

Look for outbound connections, DNS activity, unusual destinations and timing tied to process execution.

PERSISTENCE

Inspect startup locations, scheduled tasks, services, registry run keys and other persistence mechanisms.

SCOPE

Search the IOC, hash, filename, path, user and related TTPs across other endpoints and telemetry.

CONTAIN

Isolate the affected endpoint and restrict compromised credentials if evidence supports credential capture risk.

VALIDATE

Re-scan, verify persistence removal, confirm suspicious connections stop, and review for reinfection.

Key Findings

Evidence that drives the decision

  • Suspicious behavior should be linked to a clear parent/child process chain.
  • File reputation alone is not enough; execution context and telemetry determine confidence.
  • Persistence evidence materially changes incident severity and eradication steps.
  • Credential exposure should trigger identity scoping, session review and password/MFA remediation where appropriate.
Response

Contain → Eradicate → Validate

  • Contain the affected user, host, account, connection, or IOC based on confirmed evidence.
  • Remove malicious artifacts, persistence, unauthorized sessions, or access paths.
  • Re-scan and re-check telemetry to confirm suspicious activity has stopped.
  • Document the timeline, evidence, business impact and response actions.
  • Use lessons learned to tune or create detections for similar behavior.
Lab disclosure: This case study is presented as a simulated/home-lab investigation for portfolio demonstration.