Scam › Module 2 › Lesson 5
Lab — Scam Simulator
Walk through realistic scam scenarios and decide the safe response for each one
Opening
Four fictional files. Your job is refuse + flags — not a live sting.
Scams compress time. This lab decompresses it. You will read four fictional scenarios that reuse Module 2: a WhatsApp "hire," a romance-to-invest dashboard, a parking QR overlay, and an AI-sounding family/boss call. For each, you write the flags you can name and the safe action you would take — into $HOME/cyberlium-lab/scam-sim.txt, then chmod 600. You will not message the fictional senders (they are not real). You will not deposit, scan random public stickers, buy gift cards, or clone a voice "to complete the sim." The code block contains the scenario text so you can copy it into your notes. Work slow. The point is the pause you will need when the next one is not labeled LAB.
1. How to score a scenario — flags first, then the refuse
A flag is a fact you can point at, not a vibe. Job: too-good pay, WhatsApp-only, buy-gear-reimburse, ID over chat, Gmail instead of a careers page you type. Crypto: TRUST THEN MONEY, guaranteed returns, dashboard-only profit, withdrawal tax, recovery-for-a-fee. QR: physical overlay, preview host mismatch, SSO or password ask on a parking/Wi-Fi story. AI: unexpected money, stay-on-the-line, skip process, voice-as-proof. The safe action is almost always: stop the send (money, ID, OTP, crypto), leave the channel, verify on a page or number you already have. Write "what I would NOT do" as well. That line catches the lab-shaped mistakes: playing along, test deposits, scanning the wild sticker, calling the number the scammer recited, or building a copy of the kit. This file can mention that you recognized a pattern from lessons 1–4. It must not contain real ID images, real wallet seeds, or anyone else's phone number you do not already have a right to store.
Scope is the four stories in the code block. If a real message in YOUR inbox looks similar, you may add a fifth section about that message only — still refuse, still no engagement. Do not hunt forums for live pig-butchering chats to "practice on." Do not report fictional domains as if they were incidents. The lab is judgment on paper.
2. Wrong vs right: engaging the kit vs writing the refuse
Worked failure — turning a simulator into operations. Evidence is your flags and safe actions in scam-sim.txt.
Wrong
You try to WhatsApp "Maya," deposit dust on LuminaTrade, scan garage stickers near you, or clone a voice to match Scenario 4. You paste a real passport into the notes "for realism." You publish scam-sim.txt. That is how labs become incidents or how-to leakage.
Right
You copy the four fictional scenarios from the block. For each, you write flags + safe action + what you would not do. You chmod 600 $HOME/cyberlium-lab/scam-sim.txt. You send nothing, scan only a known-good QR if you still want that drill from lesson 3 (optional, not required here), and you never run the other side of any scam.
3. Hands-on: four fictional scenarios, one notes file
Create the directory, write the template, fill every SCENARIO section. The scenario text is fictional — company names, URLs, and people are not real contacts. If a command fails on Windows, use WSL, Git Bash, or create the same file in Notepad under your user profile at cyberlium-lab\scam-sim.txt and restrict permissions as you can (icacls / inheritance removed, or keep it offline on paper).
Command guide
Scam simulator — four fictional scenarios → scam-sim.txt chmod 600
Command — copy this
mkdir -p "$HOME/cyberlium-lab"
============================================================ FICTIONAL SCENARIOS — do not contact, visit, pay, or clone.
Optional command
Copy into your notes. Fill flags + safe_action + would_not.
============================================================ SCENARIO 1 — Dream remote job (fake recruiter) Channel: WhatsApp "Maya HR" — no company email, no video interview. Pitch: $4,500/week remote "payment agent," hired after one chat. Asks: passport selfie tonight; buy a laptop from their link (reimburse Friday); then USDT gift cards for "client refunds." Mail: [email protected] claiming Northbridge Analytics. SCENARIO 2 — Romance + trading tip (pig-butchering pattern) Channel: dating-app match "Ava," weeks of chat, then investing. Platform: LuminaTrade — not a URL you typed from a real exchange you know. Pitch: "1% daily, no risk, my firm's desk." Dashboard shows $8,400. Withdrawal: "pay 15% tax in USDT to unlock." Follow-up: "Agent Chen" DM — recovery fee to unfreeze. SCENARIO 3 — Parking QR (preview mismatch) Physical: garage QR looks freshly stuck on top of another code. Camera preview (do NOT open): pay-garage-secure-login.xyz Page story: Microsoft 365 login to "complete parking payment." You have the city's official parking app on your phone already. SCENARIO 4 — "Family / CEO" voice (AI-sounding urgency) Call: voice sounds like your mom (or, at work, like your boss). Ask: bail / vendor wire in gift cards or a same-day transfer. Pressure: "stay on the line, don't tell anyone, skip the usual process." You have Mom (or the switchboard) already saved in contacts. ============================================================
Command — copy this
{
echo "date: $(date -Iseconds 2>/dev/null || date)"
echo "ethics: fictional only; no sends; no overlay; no voice clone; no fake job desk"
echo ""
echo "=== SCENARIO 1 job ==="
echo "flags:"
echo "safe_action:"
echo "would_not:"
echo ""
echo "=== SCENARIO 2 crypto ==="
echo "flags:"
echo "safe_action:"
echo "would_not:"
echo ""
echo "=== SCENARIO 3 qr ==="
echo "flags:"
echo "safe_action:"
echo "would_not:"
echo ""
echo "=== SCENARIO 4 voice ==="
echo "flags:"
echo "safe_action:"
echo "would_not:"
} > "$HOME/cyberlium-lab/scam-sim.txt"
chmod 600 "$HOME/cyberlium-lab/scam-sim.txt"Fill the blanks in an editor you own, then re-chmod 600. Suggested direction (write YOUR words, not a copy-paste of this comment): 1) Stop. No ID, no laptop buy, no USDT. Type careers page — role won't exist. Report in-app. 2) TRUST THEN MONEY. No deposit, no tax, no recovery pay. Break contact. Dashboard ≠ wallet. 3) Do not open. Official parking app or URL you type. Do not scan random stickers as a lab. 4) Hang up. Call known number. Phrase test. No money on the first call.
NEVER: message Maya/Ava/Chen or visit LuminaTrade / the .xyz host NEVER: send ID, crypto, gift cards, or a "test" wire NEVER: overlay QR stickers or scan random public codes for this lab NEVER: clone voices or deepfake family/boss NEVER: process payments or reship for a "job" that failed this sim
Mission: four refuses in scam-sim.txt
For each of the four fictional scenarios, write the flags you saw and the safe action (plus what you would not do) into $HOME/cyberlium-lab/scam-sim.txt. chmod 600. Do not send money, ID, OTPs, or crypto. Do not scan random public QRs. Do not clone voices or impersonate HR. Optional fifth section only for a real message already in YOUR inbox — still refuse, still no engagement.
Stuck? Ask Cyberlium AI Mentor
If two scenarios feel like they "might still be real," ask for a hint — not contact scripts. Try: "Hint only: for the WhatsApp payment-agent hire and the LuminaTrade withdrawal tax, which flags belong in scam-sim.txt and what is the safe action — without telling me how to operate either scam?" You still write the file in your own words.
You practiced the pause on job, crypto, QR, and voice using only fictional text and a notes file you locked at mode 600. Next — Quiz — Scam Protection — ten APPLY items on the same four families, then Module 3 starts with What to Do If You Clicked.
Knowledge Check
APPLY: In Scenario 1, buying USDT gift cards for "client refunds" after a WhatsApp-only hire is:
Multiple choice
Knowledge Check
APPLY: Scenario 3's preview is pay-garage-secure-login.xyz. A classmate says scanning real garage stickers will make the lab "more valid." What is in scope?
Multiple choice
Knowledge Check
APPLY: True or False: chmod 600 on $HOME/cyberlium-lab/scam-sim.txt is appropriate because the file holds your refuse decisions and any optional inbox notes you should not share casually.
True or False