- A
API hooking
Why wrong: API hooking intercepts calls but does not necessarily involve injecting code.
- B
Process hollowing
Why wrong: Process hollowing replaces a legitimate process's memory with malicious code, not injection into a running process.
- C
Code injection
Code injection is the technique of inserting code into a running process.
- D
DLL injection
Why wrong: DLL injection is a form of code injection but more specific; the stem does not specify DLL.
Quick Answer
Code injection is the correct choice because the scenario describes a malicious process writing arbitrary code into the address space of a legitimate system process like explorer.exe, typically using Windows API calls such as WriteProcessMemory and CreateRemoteThread to execute that code. This technique is the broad, generic category for any method where an attacker forces a target process to run unauthorized instructions, making it the direct match for the description of “injecting code” into a trusted process. On the Computer Hacking Forensic Investigator CHFI exam, this question tests your ability to distinguish the overarching technique from its specific subtypes—like DLL injection, process hollowing, or APC injection—which are common distractors. A frequent trap is confusing the general term with a specialized variant; remember that when the exam simply says “injecting code,” the answer is always the umbrella term code injection. Memory tip: think “inject” equals the generic category—if it doesn’t specify how, stick with code injection.
CHFI Malware Forensics Practice Question
This CHFI practice question tests your understanding of 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 analysis, an investigator finds that a suspicious process is injecting code into a legitimate system process (e.g., explorer.exe). Which technique is being used?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Code injection
Code injection is the correct answer because the scenario describes a process injecting arbitrary code into a legitimate system process like explorer.exe. This is the generic term for techniques where malicious code is written into the address space of another process and executed, often via Windows API calls such as WriteProcessMemory and CreateRemoteThread. The question explicitly states 'injecting code,' which directly maps to the broad category of code injection, not a specific subtype.
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.
- ✗
API hooking
Why it's wrong here
API hooking intercepts calls but does not necessarily involve injecting code.
- ✗
Process hollowing
Why it's wrong here
Process hollowing replaces a legitimate process's memory with malicious code, not injection into a running process.
- ✓
Code injection
Why this is correct
Code injection is the technique of inserting code into a running process.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
DLL injection
Why it's wrong here
DLL injection is a form of code injection but more specific; the stem does not specify DLL.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the distinction between generic code injection and its specific subtypes (like DLL injection or process hollowing), trapping candidates who choose a narrower term when the question uses the broad phrase 'injecting code' without specifying the delivery mechanism.
Detailed technical explanation
How to think about this question
Under the hood, code injection typically uses the Windows API sequence: OpenProcess to get a handle, VirtualAllocEx to allocate memory in the target process, WriteProcessMemory to write the malicious code, and CreateRemoteThread to execute it. A real-world scenario is the use of process injection by banking trojans like Zeus, which injects into explorer.exe to steal credentials while evading detection by blending into a trusted process. Subtle behavior includes the fact that injected code runs in the context of the target process, inheriting its security token and privileges, which can bypass user account control (UAC) if the target is a high-integrity process.
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 practitioner preparing for the CHFI exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Malware Forensics — study guide chapter
Learn the concepts, then practise the questions
- →
Malware Forensics practice questions
Targeted practice on this topic area only
- →
All CHFI questions
1,000 questions across all exam domains
- →
Computer Hacking Forensic Investigator CHFI study guide
Full concept coverage aligned to exam objectives
- →
CHFI practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related CHFI practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Computer Forensics Investigation Process practice questions
Practise CHFI questions linked to Computer Forensics Investigation Process.
Computer Forensics Fundamentals and Process practice questions
Practise CHFI questions linked to Computer Forensics Fundamentals and Process.
Storage Forensics and File System Analysis practice questions
Practise CHFI questions linked to Storage Forensics and File System Analysis.
Incident Response and First Responder Skills practice questions
Practise CHFI questions linked to Incident Response and First Responder Skills.
Computer Forensics Lab practice questions
Practise CHFI questions linked to Computer Forensics Lab.
Evidence Acquisition and Duplication practice questions
Practise CHFI questions linked to Evidence Acquisition and Duplication.
OS and Network Forensics practice questions
Practise CHFI questions linked to OS and Network Forensics.
OS and File System Forensics practice questions
Practise CHFI questions linked to OS and File System Forensics.
Application, Email and Cloud Forensics practice questions
Practise CHFI questions linked to Application, Email and Cloud Forensics.
Mobile and Malware Forensics practice questions
Practise CHFI questions linked to Mobile and Malware Forensics.
Network and Cloud Forensics practice questions
Practise CHFI questions linked to Network and Cloud Forensics.
Database and Application Forensics practice questions
Practise CHFI questions linked to Database and Application Forensics.
Practice this exam
Start a free CHFI practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this CHFI question test?
Malware Forensics — This question tests Malware Forensics — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Code injection — Code injection is the correct answer because the scenario describes a process injecting arbitrary code into a legitimate system process like explorer.exe. This is the generic term for techniques where malicious code is written into the address space of another process and executed, often via Windows API calls such as WriteProcessMemory and CreateRemoteThread. The question explicitly states 'injecting code,' which directly maps to the broad category of code injection, not a specific subtype.
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 →
Last reviewed: Jun 11, 2026
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.