Why does compiled code pose more of a security risk than interpreted code?

The correct answer is A. Because malicious code can be embedded in compiled code and be difficult to detect.. Compiled code is translated entirely into machine-level binary before execution, making it opaque and very difficult to inspect or audit for malicious logic without specialized reverse-engineering tools. An attacker can embed hidden malicious routines in compiled binaries that ar

Submitted by satoshi_tk· Apr 18, 2026Systems and Application Security

Question

Options

ABecause malicious code can be embedded in compiled code and be difficult to detect.
BIf the executed compiled code fails, there is a chance it will fail insecurely.
CBecause compilers are not reliable.
DThere is no risk difference between interpreted code and compiled code.

How the community answered

(26 responses)

A
88% (23)
B
4% (1)
C
8% (2)

Explanation

Compiled code is translated entirely into machine-level binary before execution, making it opaque and very difficult to inspect or audit for malicious logic without specialized reverse-engineering tools. An attacker can embed hidden malicious routines in compiled binaries that are not visible without disassembly. Interpreted code, by contrast, is executed line-by-line from a human-readable (or at least more reviewable) source, making auditing more straightforward. Compilers themselves (C) are generally reliable tools. Option B describes a runtime failure concern, not an inspection/detection disadvantage. Option D is incorrect because a meaningful security distinction does exist.

Topics

#Code Security#Compiled Code#Interpreted Code#Malware

Community Discussion

No community discussion yet for this question.

Full SSCP Practice