Analyzing Password-Protected Packed Malware
Short answer
B The investigator should run the packed executable in a controlled environment for dynamic analysis.
Question
Key Takeaways
Tests the distinction between static and dynamic malware analysis when source code or unpacked binaries are inaccessible due to obfuscation.
This question addresses how to analyze password-protected packed malware without the decryption key. The correct approach is dynamic analysis in a sandbox to observe runtime behavior.
Common mistake: Candidates often choose brute force cracking (C) because the prompt mentions a password, but this is impractical for time-sensitive investigations and may fail entirely.
Expert Analysis
Why the Answer Is Correct
Dynamic analysis (Option B) is the most suitable approach because it allows the investigator to observe the malware's behavior at runtime. By running the executable in a controlled environment (sandbox), the operating system handles the unpacking and execution, revealing the malicious payload's actions such as network connections or file modifications, regardless of the static encryption.
Why the Other Options Are Wrong
Static analysis (A) is impossible here because the content is encrypted/packed; the analyst cannot see the code structure. Brute-forcing the password (C) is inefficient and often futile against strong encryption, wasting valuable investigation time. Reverse engineering (D) is a valid long-term strategy but is too complex and resource-intensive for immediate access compared to simply observing the runtime output.
Community Comment Notes
The community was split on this, with some arguing that 'accessing contents' implies getting the raw binary data, which only cracking achieves. However, one user noted, 'Reveals runtime behavior without needing password,' highlighting the practical value of sandboxing. Another comment warned about tool availability: 'Assuming the investigator does not know the tool... will not be able to access it even with a cracked password,' reinforcing that dynamic analysis is more robust against unknown packers.
Exam Strategy
When analyzing malware, always consider if you can observe its effect without seeing its internal code. If static analysis is blocked by packing/encryption, dynamic analysis in a safe sandbox is usually the next best step to gather intelligence quickly.
Frequently Asked Questions
Why is static analysis not possible on packed files?
Is brute force ever acceptable for malware passwords?
Community Votes
50% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 3
-
044f354 👍 1 Answered BAnswer: B (A) ❌ Static analysis is limited without unpacking/decryption (B) ✅ Reveals runtime behavior without needing password (C) ❌ Brute-force is time-consuming and often impractical (D) ❌ Reverse engineering is complex and requires specialized skills Running the malware in a sandbox is most effective. ----- If you agree: UPVOTE. If you disagree: discuss with citations. Both actions help crowdsource correct answers. When you upvote someone with a yellow "SELECTED ANSWER: " banner, your vote is added to the community vote distribution.
-
Elb 👍 1B > Assuming the investigator does not know the tool that has been used to pack the file and doesn't have the tool to unpack it, the investigator will not be able to access it even with a cracked password.
-
jingu_bingo 👍 1 Answered CKeyword(s): "suitable for accessing the contents of the packed file", so a crack should be attempted, however unsuccessful.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.