A child process is a separate operating system process created by an application to run a command or task. It can become a security risk when the parent application spawns it with attacker-controlled input, because the child may continue executing commands unless it is tightly constrained or explicitly terminated.
What a child process is
A child process is a separate operating system process created by an application to run a command or task. It inherits part of the parent’s execution context, then runs independently. That separation is useful for modular execution, but it also means a compromised or overly permissive parent can delegate dangerous work into another process boundary.
Why child processes matter for security
Child processes become security-relevant when the parent feeds them untrusted input, environment variables, command-line arguments, or file paths. If the spawned process interprets those values as commands, the result can be command injection, unexpected tool execution, or privilege abuse through a trusted parent workflow.
Attackers often look for places where applications launch helper programs, shell commands, scripts, or interpreters because those transitions can turn a single input flaw into code execution. The risk is not the process boundary itself, but the trust the parent places in what it launches.
Common ways child processes are abused
One common pattern is command injection, where attacker-controlled data changes what the child process actually executes. Another is abuse of living-off-the-land tools, where a legitimate interpreter or admin utility is started with malicious parameters. Child process abuse can also support persistence, staging, or lateral movement when the spawned process inherits network access, file permissions, or elevated privileges.
Defenders often watch for suspicious parent-child combinations, unusual command lines, and process trees that do not match the application’s normal behaviour. Those relationships are frequently more useful than looking only at the spawned binary name.
In phishing and document-delivery chains, child process creation is especially important because user-triggered content may launch script hosts or shell utilities. NHIMG’s OneNote Malware Delivery Guide is a useful example of how malicious content can rely on spawned processes to carry the attack forward, while the ATT&CK Execution Tactic Guide explains how process creation fits into the broader execution phase.
How organisations control and monitor child process behaviour
Controlling child process risk usually means reducing what the parent is allowed to launch, constraining inherited permissions, and logging the command line and process lineage. On endpoint and server platforms, that can include application control, script restrictions, process creation auditing, and hardening of administrative tools that are commonly spawned by other software.
Where the application design depends on launching helpers, the safest approach is to make the allowed child process set explicit and narrowly scoped. The Node.js Permission Model Guide is relevant here because runtime permission boundaries can limit whether code is allowed to spawn child processes at all.
Defensive review should also include the parent application’s own privilege level. NHIMG’s Endpoint Privilege Management Buyer's Guide is useful for understanding how reduced privilege changes what a spawned child process can actually do if it is abused.
What to investigate after suspicious process creation
When a child process looks abnormal, the first question is whether the parent was expected to create it and whether the arguments, working directory, user context, and network activity match normal use. A single suspicious process can be a symptom of a broader compromise, especially if the child is a shell, script host, or downloader.
Investigators should review the full process tree, associated file writes, child-to-parent timing, and any evidence of follow-on execution. The process boundary often becomes the pivot point where a harmless-looking application turns into a vehicle for attacker-controlled code.
For server-side abuse patterns, NHIMG’s T1505 Server Software Component Defensive Guide is useful when child processes emerge from web-facing components or other persistent server software, because those environments are commonly abused for post-exploitation execution.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack and risk surface, while CIS Controls v8 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| MITRE ATT&CK | T1059 — Command and Scripting Interpreter | Child processes often execute attacker-supplied commands through shells or script interpreters. |
| T1204 — User Execution | Many child-process abuse chains begin when a user opens content that spawns further execution. | |
| Recommendation — Map suspicious command execution to T1059 and inspect parent-child process trees for injected arguments. Correlate user-triggered launches with downstream child processes and block suspicious execution chains. | ||
| CIS Controls v8 | CIS-4 — Secure Configuration of Enterprise Assets and Software | Restricting which programs can be launched and how they run is a core secure-configuration issue. |
| Recommendation — Harden application launch paths and disable unnecessary script and helper execution. | ||
| NIST SP 800-53 Rev 5 | SI-3 — Malicious Code Protection | Child processes can carry malicious code execution and need preventive control and monitoring. |
| AU-12 — Audit Generation | Process creation logging is essential for tracing parent-child relationships and execution chains. | |
| Recommendation — Apply SI-3 to detect and block suspicious child-process execution paths. Enable detailed process-creation auditing so investigations can reconstruct process lineage. | ||
Related resources from NHI Mgmt Group
- What breaks when browser-child-process detections are suppressed to reduce endpoint noise?
- How should security teams hunt for anomalous parent-child process relationships without drowning in noise?
- What happens when a child protection reporting process is not designed around anonymity and safeguarding?
- Why is a VS Code extension child process chain like code.exe to cscript.exe risky?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org