Cyberlium

Cybersecurity › Module 6 › Lesson 4

BeginnerModule 6Lesson 4/6

AI-Powered Scam Awareness

Voice clones, vishing playbooks, and synthetic IDs

15 min+17 XP3 quiz
Module progress4 of 6

Opening

A familiar voice is no longer proof of identity

Module 1 introduced deepfakes as a 2026 threat. This lesson goes narrower and more operational: AI voice cloning used in live phone fraud (vishing), synthetic identity documents, and the verification protocols that actually stop money and secret movement. Seeing or hearing is evidence of media — not of who controls the call. Your defense is process: code words, deliberate delay, and call-backs on numbers you already saved.

1. AI voice cloning + the vishing playbook

Vishing is voice phishing: social engineering over a phone call. Generative AI made it scalable. Attackers scrape short public clips — school videos, conference talks, social stories — and build a voice model. Spoofed caller ID makes the number look local, school, bank, or vendor. The script adds urgency and secrecy so you stay on the line.

Common playbook beats: (1) establish a familiar voice, (2) invent a time-critical payment or "verify your wallet," (3) demand you stay on the call so you cannot verify independently, (4) push irreversible channels — wire, crypto transfer, gift rails, or reading a seed phrase aloud. The emotion is the exploit; the clone is the costume.

2. Synthetic ID documents

AI image tools also forge or remix identity documents: IDs, utility bills, enrollment letters, vendor invoices with nearly perfect logos. A PDF that "looks official" is not authentication. Treat unexpected documents that unlock money movement as claims — verify through a known portal or phone number you already trust, not through links or numbers printed on the attachment.

Where this collides with voice scams: the caller may text a polished invoice or school-fee notice while the cloned voice pressures you live. Dual-channel pressure still fails against a single out-of-band check on a pre-saved contact.

3. Verification protocols that survive clones

Build rituals before the call arrives. Code words (family or workplace): a private phrase agreed offline that strangers and scraped audio will not know. Delay: any request involving money, codes, or wallet seeds waits until you hang up — even if the voice sobs. Call-back on a known number: dial the school office, vendor AP contact, or relative from your address book / official website, never from a number the caller "helpfully" dictates.

  • Code word

    Pre-shared secret asked after hang-up / on the real call-back. No word → no money.

  • Delay

    Urgent + irreversible = automatic pause. Scammers hate time; defenders use it.

  • Call-back on known numbers

    Saved contacts or official published numbers only — not caller-ID and not "new" numbers.

4. Wrong vs right: school-fees voice + fake invoice

Worked failure — cloned parent/guardian voice, different from Module 1 gift-card stories:

  • Wrong

    A call sounds exactly like your sibling. Caller ID shows a local number. They say the school needs overnight fees wired to a "new bursar account," then text a perfect PDF invoice. They beg you not to hang up. You transfer while still on the line — or worse, they pivot to "help me move crypto; read your wallet seed so I can unlock the payment."

  • Right

    You hang up. You wait (delay). You call the school office or your sibling on a number already saved — not the number from the call or PDF. You ask the family code word. No independent confirm → no wire, no seed phrase, no vendor "new account" payment. Seeds are never read aloud.

5. Practical: second-channel verification card

Command guide

AI voice / vishing / synthetic-doc protocol

If money / codes / wallet seeds / secrecy are requested by voice:

Command — copy this

1. STOP — do not stay on the emotional call
2. HANG UP / end the meeting (delay starts now)
3. Call or message using a SAVED contact / official published number
4. Ask the family/work CODE WORD or known private detail
5. Only then consider the request — via the real institution's portal

Synthetic invoice / ID / "bursar" PDF

Command — copy this

- Do not trust logos or letterhead alone
- Open the official site/app yourself; check the balance or invoice there
- Never pay a "new account" from a cold call attachment

Crypto / seed twist (never)

Command — copy this

Never read a recovery seed / private key on a call
Never type a seed into a site a caller sends

Family / household drill (5 minutes)

Command — copy this

Agree one code word offline
Practice: "I will call you back on your saved number"
Agree: school fees / vendor payments wait for portal confirm

Command guide

Terminal practice (Linux / Kali / macOS — YOUR machine only)

Callback rule sheet — YOUR machine, no deepfakes Linux / Kali / macOS

Command — copy this

whoami
mkdir -p "$HOME/cyberlium-lab/notes"
cd "$HOME/cyberlium-lab/notes"
date
cat > ai-scam-callback.txt << 'EOF'
if_voice_asks_money_or_codes: hang_up
verify_via: saved_contact_or_family_code
never: stay_on_call_to_catch_scammer
EOF

Command — copy this

chmod 600 ai-scam-callback.txt
ls -l ai-scam-callback.txt

Windows PowerShell

Command — copy this

New-Item -ItemType Directory -Force -Path "$env:USERPROFILE\cyberlium-lab
otes" | Out-Null
Set-Location "$env:USERPROFILE\cyberlium-lab
otes"
Get-Date

NEVER: deepfake classmates, clone voices, or SE people "for training"

Mission: install a verification ritual

1) Choose a family or close-friend code word (or work verification phrase if appropriate). 2) Store it offline — not in a chat titled "scam code." 3) Practice saying: hang up → delay → call saved number → ask code word. 4) Tell one person you will never pay "school/vendor emergency" wires or read a wallet seed on a live call.

Stuck? Ask Cyberlium AI Mentor

Ask: "Hint only: how do I verify a voice that sounds exactly like my relative during a fee emergency?" Or: "Hint only: why is a PDF invoice from a caller not enough?" Do not ask Mentor for voice-cloning or fake-ID building steps — defense only.

Verification beats vibes: code words, delay, and known-number call-backs survive clones and synthetic docs. Next — Incident Response — the full personal loop when something still goes wrong.

Knowledge Check

1

APPLY: A cloned voice + matching caller ID demands an urgent school-fee wire to a "new bursar account" and begs you not to hang up. Best first move?

Multiple choice

Knowledge Check

2

APPLY: Why must you never read a crypto wallet seed phrase to someone on a voice call — even if they sound like family?

Multiple choice

Knowledge Check

3

APPLY: A caller sends a flawless synthetic vendor invoice PDF. What makes verification actually work?

Multiple choice

← Previous

Answer all 3 knowledge checks to continue. (0/3 answered)