Rapid River Skunk Works exists to turn practical security research into usable defense.
That means building labs, writing guides, testing hardware, documenting what actually happened, and producing artifacts that defenders, business owners, investigators, and operators can act on.
This profile is not meant to look polished while saying nothing.
It is a public workbench.
RRSW operating bias:
- build the lab
- verify the claim
- preserve function
- document the artifact
- ship the useful version
- do not fake outcomes
|
Endpoint controls, SIEM logic, detection rules, hardening notes, incident-ready checklists, and defender-first documentation. Current focus:
|
Research around the devices defenders usually do not see until they become a problem. Current focus:
|
|
Passive, legal, lab-scoped signal research for detection, presence sensing, field intelligence, and defensive monitoring. Current focus:
|
Narrative-driven security challenges, investigation artifacts, broken-system labs, and blue/purple-team training material. Current focus:
|
A defender-first guide for malicious USB cables, HID injection, rogue access points, LAN implants, cable implants, hardware keyloggers, RFID/NFC cloning, UART/SPI/JTAG exposure, and SDR/RF monitoring.
Built around usability:
- start-here decision layer
- role-based reading paths
- 30 / 60 / 90 roadmap
- risk register
- copy-paste detections
- hardening controls
- team-specific guidance
The companion reference used to understand the offensive hardware landscape from a lab and research perspective.
Things that keep showing up in RRSW work:
USB ports are physical trust decisions.
Badges are credentials.
Cables are supply chain.
Network closets are privileged zones.
RF is an attack surface.
Logs only help if the team knows what they are looking for.
A guide is not useful until a busy defender can act on it.