Skip to content

Adversary Threats & Attack Vectors

This section catalogs how adversaries actually attack people — phishing campaigns, account takeovers, malware deliveries, network attacks, and the rest. Each page documents one vector or campaign with the same structure:

Attribution → How It Works → Phishing Lures or Payloads → Indicators of Compromise → Prevention (→ DFP) → If Compromised (→ IR Guide) → Detection / Purple Team → Sources

The goal is a working defender’s reference: when something feels off, you should be able to land on a page that names the technique, shows you what it looks like, and tells you what to do next.

The community (DFP Guide, IR Guide, Red Team) covers prevention, response, and offensive testing. This section fills the gap in the middle: what are the actual threats? Without that grounding, prevention reads as a generic checklist and response reads as a panic playbook.

CategoryWhat’s coveredExamples
Social EngineeringManipulation of people, not systemsPhishing, smishing, vishing, impersonation, verification-code theft
Account TakeoverAdversary gains control of an existing accountSIM swap, linked-device abuse, OAuth consent phishing, session-token theft
Credential TheftStealing passwords/tokens directlyInfostealer malware, credential dumps, password-reuse exploitation, AitM proxies
MalwareHostile code on a deviceSpyware (Pegasus, Predator), commodity infostealers, mobile RATs
Network MitMAdversary positions between you and a serviceRogue WiFi, IMSI catchers, ARP poisoning, evil twin APs
Physical ProximityAdversary needs to be physically near youJuice jacking, evil maid, BLE/UWB tracking, shoulder surfing
Supply ChainCompromise of something you trustHijacked software updates, malicious npm packages, hardware implants, compromised CMA forks

Recent threat activity affecting community-relevant populations:

  • Hit by something now? → Find the matching vector page, then jump to its “If Compromised” section, then to the IR Guide.
  • Hardening your setup? → Read the prevention sections of vectors relevant to your threat model, then apply the DFP Guide.
  • Training your team? → The phishing-lure samples on each page are real and attributed — use them for awareness training.
  • Running a red/purple team exercise? → Each page maps to MITRE ATT&CK where relevant; pair with Cyber Red Teaming.

Use the same structure as the Signal/RIS page. Required sections: At a Glance, How It Works, Indicators, Prevention, If Compromised, Sources. Optional but encouraged: MITRE ATT&CK mapping, Detection/Purple Team, phishing-lure samples. Cite primary sources (CISA, FBI, vendor advisories, original research) over secondary reporting.