Phishing, Smishing, Vishing and Scams
A practical method for reading emails, SMS, calls and chats as connected signals before acting.
Objectives and practical frame
At the end of this module, you will be able to:
- 01
recognize phishing, smishing and vishing
- 02
analyze links and attachments
- 03
treat otp requests as high-risk
- 04
verify through official channels
8.1 Introduction
This section focuses on introduction in practical terms: what is being requested, what data or access is involved and what could go wrong if the action is rushed.
The useful habit is to connect details instead of checking them in isolation. Context, channel, timing, destination and consequences provide a clearer picture of risk.
Fake emails, text messages, calls and chats are designed to look familiar and push quick action. This module helps read sender, tone, links, attachments, OTP requests and context as connected signals rather than isolated details.
8.2 What phishing is
This section focuses on what phishing is as a form of deception built around context, pressure and a requested action.
The safest response is to read the request as a whole: sender, channel, timing, link, attachment, payment instruction, code request and independent verification path.
A suspicious message should be evaluated as a whole
A suspicious message should be evaluated as a whole. Logos and wording matter less than context, destination and the action being requested.
8.3 Why phishing works
This section focuses on why phishing works as a form of deception built around context, pressure and a requested action.
The safest response is to read the request as a whole: sender, channel, timing, link, attachment, payment instruction, code request and independent verification path.
8.3.1 Email phishing
This detail focuses on email phishing as a form of deception built around context, pressure and a requested action.
The safest response is to read the request as a whole: sender, channel, timing, link, attachment, payment instruction, code request and independent verification path.
8.3.2 Smishing: phishing by SMS
This detail focuses on smishing: phishing by sms as a form of deception built around context, pressure and a requested action.
The safest response is to read the request as a whole: sender, channel, timing, link, attachment, payment instruction, code request and independent verification path.
8.3.3 Vishing: phone scams
This detail focuses on vishing: phone scams as a form of deception built around context, pressure and a requested action.
The safest response is to read the request as a whole: sender, channel, timing, link, attachment, payment instruction, code request and independent verification path.
8.3.5 QR phishing
This detail focuses on qr phishing as a form of deception built around context, pressure and a requested action.
The safest response is to read the request as a whole: sender, channel, timing, link, attachment, payment instruction, code request and independent verification path.
8.3.6 Spear phishing
This detail focuses on spear phishing as a form of deception built around context, pressure and a requested action.
The safest response is to read the request as a whole: sender, channel, timing, link, attachment, payment instruction, code request and independent verification path.
8.3.7 Business Email Compromise
This detail focuses on business email compromise as a form of deception built around context, pressure and a requested action.
The safest response is to read the request as a whole: sender, channel, timing, link, attachment, payment instruction, code request and independent verification path.
8.3.8 Scams with fake payments
This detail focuses on scams with fake payments as a form of deception built around context, pressure and a requested action.
The safest response is to read the request as a whole: sender, channel, timing, link, attachment, payment instruction, code request and independent verification path.
8.3.9 Scams with fake refunds
This detail focuses on scams with fake refunds as a form of deception built around context, pressure and a requested action.
The safest response is to read the request as a whole: sender, channel, timing, link, attachment, payment instruction, code request and independent verification path.
8.3.10 Scams with fake parcels and couriers
This detail focuses on scams with fake parcels and couriers as a form of deception built around context, pressure and a requested action.
The safest response is to read the request as a whole: sender, channel, timing, link, attachment, payment instruction, code request and independent verification path.
8.3.11 Banking scams
This detail focuses on banking scams as a form of deception built around context, pressure and a requested action.
The safest response is to read the request as a whole: sender, channel, timing, link, attachment, payment instruction, code request and independent verification path.
8.3.12 Romance scams
This detail focuses on romance scams as a form of deception built around context, pressure and a requested action.
The safest response is to read the request as a whole: sender, channel, timing, link, attachment, payment instruction, code request and independent verification path.
8.3.13 Fake investment scams
This detail focuses on fake investment scams as a form of deception built around context, pressure and a requested action.
The safest response is to read the request as a whole: sender, channel, timing, link, attachment, payment instruction, code request and independent verification path.
8.4 Common warning signs
This section focuses on common warning signs in practical terms: what is being requested, what data or access is involved and what could go wrong if the action is rushed.
The useful habit is to connect details instead of checking them in isolation. Context, channel, timing, destination and consequences provide a clearer picture of risk.
8.5 Practical procedure: I receive a suspicious message, what do I do?
This section focuses on practical procedure: i receive a suspicious message, what do i do? in practical terms: what is being requested, what data or access is involved and what could go wrong if the action is rushed.
The useful habit is to connect details instead of checking them in isolation. Context, channel, timing, destination and consequences provide a clearer picture of risk.
8.6 What to do and what not to do
This section focuses on what to do and what not to do in practical terms: what is being requested, what data or access is involved and what could go wrong if the action is rushed.
The useful habit is to connect details instead of checking them in isolation. Context, channel, timing, destination and consequences provide a clearer picture of risk.
A correct logo does not prove that a message is legitimate.
Checking only the visual design and not the link, context or request.
Open the official app or site manually instead of using the received link.
Message comparison
Compare a legitimate message with a suspicious one. List differences in sender, link, request, tone and verification path.
A suspicious message should be evaluated as a whole. Logos and wording matter less than context, destination and the action being requested.