Multiple Choice Questions: Coding Phishing Detectors in Scratch

💡 Quick Study Guide: Phishing Detectors in Scratch

• 🚨 Phishing Defined: Malicious attempts to trick users into revealing sensitive information (like usernames, passwords, credit card numbers) by impersonating a trustworthy entity.
• 🧱 Key Scratch Blocks: Essential tools include ask () and wait 💬 for user input, if () then () else () 🚦 for conditional logic, contains () 🔍 to check if a string includes another, length of () 📏 for input validation, join () () 🔗 for combining text, and set variable to () 💾 for storing data.
• 🚩 Common Phishing Indicators: Look for misspellings ✍️, suspicious or altered URLs 🌐, urgent or threatening language ⏰, requests for highly sensitive personal data 🔒, and unusual sender addresses 📧.
• ⚙️ Basic Detection Logic Flow: Typically involves asking for user input (e.g., a URL or email text)❓, analyzing this input for suspicious keywords or patterns using conditional blocks 🔎, and then providing an alert ⚠️ or confirmation message 🗣️ to the user.
• 🚧 Limitations of Scratch Detectors: While great for learning concepts, Scratch-based detectors are simplified. Real-world phishing detection uses complex algorithms, AI, and vast databases, making advanced scams difficult for basic Scratch projects to identify.

📝 Practice Quiz: Coding Phishing Detectors

1. What is the primary goal of a phishing attack?
   1. To improve website security.
   2. To gather sensitive user information.
   3. To optimize search engine rankings.
   4. To create fun online games.
2. Which Scratch block is most suitable for asking a user to input a suspicious email subject line for analysis?
   1. say () for () seconds
   2. ask () and wait
   3. broadcast ()
   4. set () to ()
3. To check if a user's input answer contains the word "verify" (a common phishing tactic), which Scratch block combination would you use?
   1. if (length of [answer] > 5) then...
   2. if (answer = [verify]) then...
   3. if ([answer] contains [verify]) then...
   4. if (not [answer]) then...
4. A Scratch phishing detector project uses a variable isPhishing to store true or false. When a suspicious keyword is detected, how should isPhishing be updated?
   1. set [isPhishing] to [false]
   2. change [isPhishing] by [1]
   3. set [isPhishing] to [true]
   4. show variable [isPhishing]
5. What is a common visual indicator of a phishing attempt that a basic Scratch detector could simulate checking (if the user inputs a URL)?
   1. The color scheme of the website.
   2. The exact domain name in a URL.
   3. The number of images on a page.
   4. The font used in the message.
6. If a phishing detector in Scratch needs to alert the user with a message like "Warning! This looks suspicious because it contains 'login' and 'urgent'", which block is best for combining these text parts?
   1. split () by ()
   2. letter () of ()
   3. join () ()
   4. report ()
7. Why might a simple Scratch phishing detector struggle to identify advanced phishing scams?
   1. Scratch projects cannot use variables.
   2. It lacks access to real-time threat databases and complex pattern recognition.
   3. Scratch is only for creating animations.
   4. It cannot ask for user input.