Loading
0x10Lesson 2 of 15

How attacks evolved and how to threat-model

Recognize malware and attacker tools, then use data flows and STRIDE to find threats.

38 min 9-question quiz
By the end of this lesson you can
  • Distinguish viruses, worms, Trojans and ransomware by what they do
  • Recognize the kinds of programs used in malicious campaigns and the clues they leave
  • Use the four threat-modeling questions
  • Find trust boundaries in a data-flow diagram
  • Apply STRIDE to each part of a system

Selected moments in hacking history

Hacking did not begin as a synonym for crime. The word once described clever technical problem solving; as connected systems grew, the same curiosity and skills could also be used for unauthorized access. These examples show how the methods changed:

  • 1970s — phone phreaking. People explored telephone signaling. A “blue box” could manipulate the phone network to place calls without paying. This was an early example of exploiting a system’s rules rather than breaking its hardware. Computer History Museum.
  • 1988 — the Morris worm. A program spread across connected Unix computers without attaching to a host file. It slowed or halted many systems and helped spur organized incident response. FBI history.
  • 1999 — Melissa. A malicious Word document used a macro and Outlook address books to email copies of itself. It combined a virus with social engineering and overloaded mail systems. FBI history.
  • 2000 — ILOVEYOU. A deceptive email attachment ran a script that spread through recipients’ address books. The name “Love Bug virus” stuck, though the FBI also described it as a worm. FBI testimony.
  • 2017 — WannaCry. Ransomware used Windows SMB vulnerabilities to spread like a worm, then encrypted files. One outbreak can therefore have more than one label. Microsoft research.

Today, attackers may also steal credentials, abuse legitimate administration software, and move data to cloud services. The core question remains: what behavior is occurring, and what access made it possible?

Malware types and attack techniques

The labels below describe different things. Virus and worm describe how malicious code spreads; Trojan describes how it is disguised; ransomware and spyware describe what it does after it runs. One program can fit several labels.

TermWhat to recognize
VirusInfects another file or program and spreads when that host runs or is shared.
WormReplicates and spreads on its own, often across a network. It need not attach to another program.
TrojanPretends to be a useful or harmless file or app to persuade someone to run it. It need not replicate.
RansomwareLocks or encrypts access to data and demands payment; some groups also steal data first.
Spyware / infostealerQuietly collects information such as credentials, browser data, or files.
BotnetMany compromised devices controlled as a group, for example to send traffic or spam.

Phishing is a deceptive message or site that persuades someone to reveal information or run something. Credential stuffing tries stolen username/password pairs on other services. DDoS overwhelms a service with traffic. These are attack techniques, not malware families. CISA’s malware guide describes the malware terms.

Try it

Up to 15 XP

Name the behavior

Sort each description by the behavior it illustrates. A real incident can involve several categories at once.

0 of 5 sortedScore 0/0
  • “A macro infects documents and spreads when people open and share those files”

  • “Code copies itself to reachable vulnerable computers without attaching to a document”

  • “A fake PDF converter secretly installs unwanted software when opened”

  • “Malware encrypts business files and demands payment for a key”

  • “A message impersonates payroll and sends employees to a lookalike sign-in page”

Programs found in malicious campaigns

Attackers rarely use one magical “hacking program.” They combine tools for access, control, movement, and theft. Many named tools below also have legitimate uses, so finding one is a lead to investigate, not proof that its user is malicious. MITRE ATT&CK documents these examples:

JobDocumented exampleWhat a defender might investigate
Capture a sign-inevilginx2 can relay a lookalike login flow and capture credentials or session tokens.Unexpected login domains, new sessions, and token use from unusual places.
Collect credentialsMimikatz can extract Windows credential material.Sensitive process access and unusual account use afterward.
Move inside a networkImpacket includes network-protocol tools used for remote execution and lateral movement.Remote service activity and authentication across multiple hosts.
Control a compromised hostCobalt Strike is an adversary-simulation product also used in intrusions.Repeated outbound connections and unexpected child processes.
Copy data outRclone is a normal cloud-sync utility that has also appeared in ransomware campaigns.Large or unusual uploads to cloud storage.

Attackers may also use software already installed on a computer, such as PowerShell. That is called living off the land: the tool’s presence is ordinary, while its context and behavior may be suspicious. None of these examples requires assuming that every scan, script, or cloud upload is an attack.

With those patterns in mind, threat modeling asks what could happen to your system before you build it - when fixing a design flaw costs a whiteboard eraser, not an incident. The Threat Modeling Manifesto boils it down to four questions:

  1. What are we working on? - draw the system.
  2. What can go wrong? - list threats.
  3. What are we going to do about it? - choose mitigations.
  4. Did we do a good enough job? - review and repeat.

For step 1, teams draw a data-flow diagram: external entities (users, other services), processes (your code), data stores (databases, files) and the data flows between them. Then they mark trust boundaries - lines where data passes between areas with different levels of trust, like the internet and your server. Most attacks happen where data crosses a boundary, so that’s where you validate input, authenticate and authorize.

STRIDE (created at Microsoft) is a checklist for step 2. Each letter is a threat and the property it violates:

ThreatViolatesExample
SpoofingAuthenticationlogging in with a stolen password
TamperingIntegritychanging the price in a request
RepudiationNon-repudiation“I never made that transfer” - and no logs to prove otherwise
Information disclosureConfidentialityan error page showing database details
Denial of serviceAvailabilityflooding the login endpoint
Elevation of privilegeAuthorizationa normal user reaching the admin panel

Try it

Up to 15 XP

Name that STRIDE threat

You’re reviewing a food-delivery app. Sort each threat into its STRIDE category.

0 of 6 sortedScore 0/0
  • “A customer edits the request to set the order total to $0.01”

  • “An attacker signs in as a courier using a password from another site’s breach”

  • “A restaurant denies changing a menu price because nothing records who changed it”

  • “The order API returns other customers’ home addresses”

  • “Bots place thousands of fake orders, so real customers can’t check out”

  • “A courier account calls the admin refund endpoint successfully”

A handy shortcut, STRIDE-per-element, says which threats usually apply to each kind of element: external entities can be spoofed or deny their actions (S, R); processes face all six; data stores and data flows mainly face tampering, information disclosure and denial of service (T, I, D).

Practice: find the trust boundaries

Try it

Up to 15 XP

Where does data change hands?

Threats cluster where data crosses from one zone of trust to another. Click every flow that crosses a boundary, then check your answer.

InternetBrowser
Web tierWeb app
Internal networkAPIDatabaseJob queue
Third partyPayment provider

Key takeaways

  • A virus needs a host, a worm spreads on its own, a Trojan is disguised, and ransomware describes its effect.

  • Malicious campaigns combine programs for access, credential theft, remote control, movement, and data theft; investigate behavior in context.

  • Ask: what are we working on, what can go wrong, what will we do, did we do a good job?

  • Draw data flows and mark trust boundaries; attacks cluster where data crosses them.

  • STRIDE: Spoofing, Tampering, Repudiation, Information disclosure, Denial of service, Elevation of privilege.

Lesson quiz

9 questions · pass with 7 correct · up to 50 XP

Passing this quiz completes the lesson and keeps your streak going. Questions you miss come back in review sessions later.

Questions about this lesson

Stuck? Ask. Figured something out? Share it. Explaining is one of the best ways to learn.

Loading posts…