Skip to content

Case Studies

github-actions[bot] edited this page Nov 18, 2026 · 4 revisions

Historical incidents and security research, explained through evidence and diagrams

Part of the ULTIMATE CYBERSECURITY MASTER GUIDE

Maintained Books Docs OSINT Scripts License Last Commit


Visuals and navigation reviewed: November 17, 2026. These are historical accounts and conceptual diagrams, not laboratory reproductions or proof of current exploitability.

๐ŸŽฏ Purpose

Provide a dedicated starting point for studying documented cybersecurity incidents and hardware-security research, from enterprise intrusions to physical-device trust boundaries.

โš™๏ธ Function

Connect each case to its analysis, source material, explanatory visuals, and related defensive guides. Enterprise incident analyses live in the Enhanced Master Guide; the detailed hardware cases live in this section.

๐Ÿ† Goal

Help readers explain what failed, what the evidence actually establishes, and which engineering or operational lessons apply to a similar system.

๐Ÿ“‹ When To Use

  • Learning how an intrusion moves between systems, identities, or physical components.
  • Comparing a disclosed vulnerability with a documented incident.
  • Preparing a threat-model discussion, security lesson, or defensive review.
  • Checking the limits of a historical claim before applying it to a current deployment.

๐Ÿ“‹ Table Of Contents

Start Here

If You Want To Understandโ€ฆ Open
Worm propagation versus a ransomware payload WannaCry and EternalBlue
A trusted update becoming an intrusion path SolarWinds and NotPetya
Software changing a physical process Stuxnet
A technical foothold becoming financial fraud Carbanak
Historical surveillance collection pathways Snowden disclosures
Physical interfaces and credential trust Onity, Unsaflok, and DirecTV DSS
Secret recovery and authentication boundaries Tesla key fobs and EUCLEAK
Identifying information hidden in ordinary output Xerox printer dots

Attack Case Studies (Historical References)

Each incident title opens its analysis in the Enhanced Master Guide. The source links provide external background references; the detailed hardware research entries follow below.

Incident Type
Stuxnet Nation-state cyberweapon - Iranian nuclear facilities ยท Source
WannaCry Global ransomware outbreak ยท Source
EternalBlue / NSA Leak NSA exploit leaked by Shadow Brokers ยท Source
SolarWinds Software supply chain compromise ยท Source
Carbanak APT banking theft campaign ยท Source
NotPetya Destructive malware disguised as ransomware ยท Source
Edward Snowden / NSA Mass surveillance program revelations ยท Source

Hardware, RFID & Embedded Security

Case Study Published Primary Failure Related Guides
Unsaflok: Three Million Hotel-Lock Exposure March 2024 RFID keycard and lock authorization weaknesses RFID & NFC, Hardware Hacking
Onity Hotel-Lock Research 2012 Physical maintenance-port trust boundary Hardware Threat Modeling
Tesla Model S Key-Fob Cloning Research September 2018 Weak proprietary RF immobilizer authentication SDR Security
EUCLEAK: YubiKey/Infineon Side Channel September 2024 Non-constant-time ECDSA processing Side Channels, Security Keys
DirecTV DSS Cards & Black Sunday January 2001 event Altered smart-card authorization & operator countermeasures Threat Modeling
Xerox DocuColor MIC Decoding October 2005 Undisclosed identifying metadata in physical output OPSEC

The term โ€œ3M hackโ€ is used here to mean the approximately three million Saflok doors reported in Unsaflok research, not a confirmed incident involving 3M Company. If a different 3M incident was intended, that needs a separate verified case study.

Reading The Visuals

Each case includes an original conceptual diagram beside the relevant explanation. The Xerox case also includes owner-supplied images. Captions identify provenance, source material, scope, and limits.

Visual Element How To Read It
Boxes and arrows A simplified relationship or mechanism; not measured timing or a universal attack sequence.
Trust boundaries Where authority or information crosses between components; not a guarantee about a product.
Parallel routes Different mechanisms that may require different defensive controls.
Historical dates and versions Scope of the cited research; verify the actual deployment before making a present-day claim.
Illustrations and synthetic examples Teaching aids, not incident evidence or laboratory measurements.

The image asset index records where these figures are used. For deeper study, follow each case's source links and distinguish researcher findings, vendor advisories, court records, and later reporting.

Case Study Review Checklist

  1. Distinguish disclosed research from confirmed criminal exploitation; do not imply the latter unless evidence exists.
  2. Record which exact devices, deployments, firmware and date were covered by the original research; avoid universal claims.
  3. Separate lab reproduction from real-world incident statistics.
  4. Attribute dates and versions to the original source. An old patch-deployment percentage is not a current compliance rate.
  5. Link to related defensive and threat-modeling guides; never publish unauthorized entry techniques, live access credentials or card-cloning recipes.

Related Guides

Guide Use It For
Hardware Hacking Device trust boundaries, physical interfaces, and side channels.
Incident Response Containment, evidence handling, investigation, and recovery.
Reverse Engineering Understanding implementation behavior and analysis limits.
OPSEC Identity exposure and information handling.
RFID & NFC Credential systems and authorized access-control assessment context.

โฌ…๏ธ Back To Master Index | ๐ŸŽฏ Role Navigation | Legal Notice


๐Ÿ“‘ All Pages in Case Studies


๐Ÿ“‚ Folder: CaseStudies | โœ๏ธ Suggest an edit | ๐Ÿ—บ๏ธ Browse by Topic

Clone this wiki locally