usb-and-peripheral-forensics — Claude Code skill: install & guide
usb-and-peripheral-forensics is a Claude Code skill that analyses USB connection records and peripheral activity. Investigates Windows storage artefacts during forensic reviews.
no license ★ 73 updated 2026-11-15
npx skills add W4L33Dx/Cyber-Monster --skill usb-and-peripheral-forensics -a claude-codeWhat usb-and-peripheral-forensics does
The skill inspects removable storage artefacts across Windows system stores. It reads SYSTEM\CurrentControlSet\Enum\USB for Plug and Play classes, moving to Enum\USBSTOR and Enum\SCSI for external drives. Under properties subkeys 0064 to 0067, it extracts UTC FILETIMEs covering initial installation, arrival, and extraction.
Presence in USBSTOR verifies attachment rather than file transfers. To verify whether sensitive data moved, the skill demands supplementary evidence from shellbags, jump lists, LNK shortcuts, or USN journal entries. Because setupapi.dev.log writes local timestamps, the skill converts them through the SYSTEM hive timezone before comparing against registry records.
Device identifiers holding an ampersand as their second character represent Windows-generated strings rather than authentic hardware serials, making cross-host matching invalid. If critical logs or registry hives were omitted during collection, the procedure halts with an inconclusive telemetry gap finding.
What it helps with
- extract first-install and last-removal timestamps for external media
- attribute mounted volume GUIDs to specific NTUSER.DAT user hives
- distinguish Windows-generated instance IDs from vendor serial numbers
- correlate setupapi.dev.log local time with registry UTC values
Example prompts for the agent
- Check USBSTOR and MountedDevices to map recently attached flash drives
- Correlate setupapi.dev.log entries against SYSTEM registry FILETIME keys
- Verify whether user MountPoints2 links the target serial number to a profile
How to install usb-and-peripheral-forensics
1Skills CLI (Vercel)
npx skills add W4L33Dx/Cyber-Monster --skill usb-and-peripheral-forensics -a claude-code2Manually: put the files in place
~/.claude/skills/usb-and-peripheral-forensics/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/usb-and-peripheral-forensics/
1Skills CLI (Vercel)
npx skills add W4L33Dx/Cyber-Monster --skill usb-and-peripheral-forensics -a codex2Manually: put the files in place
.agents/skills/usb-and-peripheral-forensics/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add W4L33Dx/Cyber-Monster --skill usb-and-peripheral-forensics -a cursor2Manually: put the files in place
.cursor/skills/usb-and-peripheral-forensics/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install W4L33Dx/Cyber-Monster blue-team/digital-forensics/usb-and-peripheral-forensics2Manually: put the files in place
.github/skills/usb-and-peripheral-forensics/SKILL.md1Skills CLI (Vercel)
npx skills add W4L33Dx/Cyber-Monster --skill usb-and-peripheral-forensics -a gemini-cli2Platform CLI
gemini skills install https://github.com/W4L33Dx/Cyber-Monster --path blue-team/digital-forensics/usb-and-peripheral-forensicsManually: put the files in place
.devin/skills/usb-and-peripheral-forensics/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about usb-and-peripheral-forensics
How to install usb-and-peripheral-forensics in Claude Code?
Run npx skills add W4L33Dx/Cyber-Monster --skill usb-and-peripheral-forensics -a claude-code. The rule loads into ~/.claude/skills/usb-and-peripheral-forensics/SKILL.md.
What does usb-and-peripheral-forensics do?
It guides digital forensics investigators through Windows peripheral artefacts, parsing Plug and Play keys, mount points, and driver logs to trace connected hardware.
Can usb-and-peripheral-forensics confirm file exfiltration on its own?
No, registry keys like USBSTOR prove device attachment exclusively. Proving data transfer requires secondary artefacts such as LNK files, Sysmon event 29, or the USN journal.