A hybrid attack is a method that combines the dictionary attack with brute-force techniques. It starts with a list of known words (like in a dictionary attack) and then mutates them by:
Appending or prepending numbers (e.g., password1, 123hello)
Adding special characters (e.g., P@ssword!, admin#123)
Varying letter casing or leetspeak (e.g., h@x0r)
From CEH v13 Courseware:
Module 6: Malware Threats # Password Cracking Methods
Incorrect Options:
B: Linear is not a password cracking method.
C: Symmetric refers to encryption, not password cracking.
D: Brute-force tries every possible combination but does not start with a word list.
Reference:CEH v13 Study Guide - Module 6: Password Cracking Techniques # Hybrid Attacks
======

Keeping user inputs separate from SQL logic and binding them as fixed values before execution is the core principle of parameterized queries or prepared statements, which effectively prevent SQL injection.

This scenario precisely matches polymorphic malware, a type of advanced malware described in CEH v13 Malware Threats. Polymorphic malware dynamically alters its code, encryption, or signature each time it propagates, allowing it to evade traditional signature-based antivirus detection.
Additionally, the malware's ability to remain dormant until triggered indicates logic-based activation, which is common in advanced threats designed to avoid sandbox detection.
CEH v13 emphasizes that polymorphic malware cannot be reliably detected using static signatures. Instead, organizations must rely on behavior-based detection, heuristic analysis, and advanced threat protection systems capable of identifying suspicious runtime behavior.
Options A, C, and D do not match the described behavior. Adware focuses on advertising. Worms self- propagate aggressively. Rootkits focus on stealth and persistence, not code mutation.
Therefore, Option B is the correct answer.

Vulnerability scanning software is a tool that can help security analysts identify and prioritize known vulnerabilities in their systems and applications. However, it is not a perfect solution and has some limitations that need to be considered. One of the most critical limitations is that vulnerability scanning software is not immune to software engineering flaws that might lead to serious vulnerabilities being missed. This means that the software itself might have bugs, errors, or oversights that could affect its accuracy, reliability, or performance. For example, the software might:
* Fail to detect some vulnerabilities due to incomplete or outdated databases, incorrect signatures, or insufficient coverage of the target system or application.
* Produce false positives or false negatives due to misinterpretation of the scan results, incorrect configuration, or lack of context or validation.
* Cause unintended consequences or damage to the target system or application due to intrusive or aggressive scanning techniques, such as exploiting vulnerabilities, modifying data, or crashing services.
* Be vulnerable to attacks or compromise by malicious actors who could exploit its weaknesses, tamper with its functionality, or steal its data.
Therefore, the security analyst should be most cautious about this limitation of vulnerability scanning software, as it could lead to a false sense of security, missed opportunities for remediation, or increased exposure to threats. The security analyst should always verify the scan results, use multiple tools and methods, and update and patch the software regularly to mitigate this risk.
References:
* [CEHv12 Module 03: Vulnerability Analysis]
* 7 limitations of vulnerability scanners
* The pros and cons of vulnerability scanning tools