The correct answer is DLL side-loading because the malware places a malicious DLL in a user-writable Temp folder and then invokes it via rundll32.exe with an explicit full path, forcing the legitimate Microsoft binary to load the attacker’s code from a non-standard location. This technique exploits the Windows DLL search order, but here the attacker bypasses that order entirely by specifying the exact path, ensuring the rogue DLL is executed instead of a system one. On the CHFI exam, this scenario tests your understanding of dynamic analysis in a sandbox environment, where you must distinguish DLL side-loading from similar techniques like DLL hijacking or search-order hijacking—a common trap is confusing the two, but remember: side-loading involves a trusted executable loading a malicious DLL from a user-controlled directory, while hijacking relies on placing a DLL earlier in the search order. Memory tip: “Side-loading = same directory as the trusted app, hijacking = one step ahead in the search path.”
CHFI Mobile and Malware Forensics Practice Question
This CHFI practice question tests your understanding of mobile and malware forensics. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
During malware dynamic analysis in a sandbox, a sample creates a file named 'C:\Users\Admin\AppData\Local\Temp\svchost.dll' and then executes 'rundll32.exe C:\Users\Admin\AppData\Local\Temp\svchost.dll,Start'. This behavior is indicative of which technique?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
DLL side-loading
D is correct because the sample places a malicious DLL named 'svchost.dll' in a user-writable directory (Temp) and then invokes it via rundll32.exe, which is a legitimate Microsoft binary. This exploits the Windows DLL search order: when rundll32.exe loads the DLL without specifying a full path, Windows first searches the application's directory, then system directories, but here the attacker explicitly provides the full path to the Temp folder, bypassing the search order and forcing the load of the attacker's DLL. This is classic DLL side-loading, where a trusted executable loads a malicious DLL from a non-standard location.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
DLL injection
Why it's wrong here
DLL injection involves forcing a running process to load a DLL via API calls like CreateRemoteThread.
✗
Process hollowing
Why it's wrong here
Process hollowing replaces the code of a legitimate process with malicious code.
✗
Reflective DLL loading
Why it's wrong here
Reflective DLL loading loads a DLL from memory without touching disk, but here the DLL is on disk.
✓
DLL side-loading
Why this is correct
The malware placed a malicious DLL in a location where rundll32.exe will load it, exploiting the search order.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse DLL side-loading with DLL injection because both involve a DLL being loaded by a legitimate process, but side-loading relies on the search order and file placement, while injection requires active code injection into a running process.
Detailed technical explanation
How to think about this question
DLL side-loading exploits the Windows DLL search order, which by default searches the application's directory, then system directories (e.g., C:\Windows\System32), then the current working directory, and finally directories in the PATH environment variable. In this scenario, the attacker places the malicious DLL in a user-writable Temp folder and explicitly specifies its full path in the rundll32 command, ensuring the malicious DLL is loaded instead of the legitimate one. A real-world example is the Stuxnet worm, which used DLL side-loading by placing a malicious DLL in the same directory as a legitimate signed executable (e.g., from Siemens) to evade detection.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this CHFI question in full detail.
Mobile and Malware Forensics — This question tests Mobile and Malware Forensics — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: DLL side-loading — D is correct because the sample places a malicious DLL named 'svchost.dll' in a user-writable directory (Temp) and then invokes it via rundll32.exe, which is a legitimate Microsoft binary. This exploits the Windows DLL search order: when rundll32.exe loads the DLL without specifying a full path, Windows first searches the application's directory, then system directories, but here the attacker explicitly provides the full path to the Temp folder, bypassing the search order and forcing the load of the attacker's DLL. This is classic DLL side-loading, where a trusted executable loads a malicious DLL from a non-standard location.
What should I do if I get this CHFI question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This CHFI practice question is part of Courseiva's free EC-Council certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CHFI exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.