The scenario describes the classic signs of fuzz testing, or "fuzzing." This is a dynamic analysis technique that automatically injects malformed, random, or unexpected data into an application's inputs to discover errors, crashes, and security vulnerabilities. The "random characters" are characteristic of simple fuzzing, while the presence of "structured query language" indicates a more intelligent, protocol-aware fuzzer attempting to trigger vulnerabilities like SQL injection. The exponential growth of test data overnight is typical for an automated fuzzing tool running for an extended period.

A. Dynamic analysis: This is too general. Fuzzing is a specific type of dynamic analysis, and the details provided (random data, malformed SQL) point directly to fuzzing as the specific method.

C. Threat model: This is a design-phase process for identifying and analyzing potential threats. It does not involve executing code or generating test data.

D. Static analysis: This method analyzes source code or binaries without executing the application. It does not interact with the program's inputs or generate test data.

---

1. Manès, V. J. M., Han, H., Sung, C., Cha, S. K., & Egele, M. (2019). The Art, Science, and Engineering of Fuzzing: A Survey. IEEE Transactions on Software Engineering, 47(11), 2312-2331. Section II.A, Paragraph 1: "Fuzzing is a popular automated software testing technique that consists in finding security vulnerabilities by injecting malformed or semi-malformed data in an automated way." https://doi.org/10.1109/TSE.2019.2946543

2. OWASP Foundation. (n.d.). Fuzzing. OWASP. Retrieved from https://owasp.org/www-community/Fuzzing. Introduction, Paragraph 1: "Fuzzing or fuzz testing is an automated software testing technique that involves providing invalid, unexpected, or random data as inputs to a computer program."

3. National Institute of Standards and Technology (NIST). (2022). Secure Software Development Framework (SSDF) Version 1.1: Recommendations for Mitigating the Risk of Software Vulnerabilities (NIST Special Publication 800-218). Section 3.3, Practice PW.8, Task 2: "Have testers use a variety of testing methods, such as... dynamic analysis (e.g., web app scanning, fuzzing)... to find vulnerabilities."

4. Zalewski, M. (2011). The Tangled Web: A Guide to Securing Modern Web Applications. No Starch Press. Chapter 15, Section: "Fuzzing and fault injection," p. 267: Discusses how fuzzing tools can be used to submit "random garbage" or "systematically mutated, protocol-compliant data streams" to uncover vulnerabilities, which aligns with the random characters and structured query language mentioned in the scenario.