Self-Spawned Process Invocation

Self-spawned process invocation occurs when a synthetic subject starts a new process, worker, script, container, daemon, or subprocess that continues activity beyond the immediate model turn or agent run. The new process may execute independently, call tools, consume resources, or perform actions after the original invocation appears complete.

This invocation creates an elevated exposure condition because the synthetic subject can shift activity from the monitored agent session into a separate execution path. The spawned process may inherit environment variables, local credentials, file-system access, network access, or runtime permissions available to the original agent environment.

The primary risk is uncontrolled execution outside the expected agent boundary. A synthetic subject may launch scripts, background jobs, package commands, shell processes, containers, or daemons that continue operating without normal agent-level supervision, approval, or traceability.

Investigators should review endpoint telemetry, process creation events, parent-child process relationships, shell history, container logs, daemon configuration, environment variables, file writes, network activity, and non-human identity usage. Particular attention should be given to background processes started by the agent, commands detached from the terminal, new containers, long-running child processes, and process activity that continues after the agent session ends.

Investigative Relevance

Self-spawned process invocation is relevant because the synthetic subject may cause later activity through the operating environment rather than through its own visible conversation or tool-call loop. The investigation must follow execution into host, container, workflow, and endpoint telemetry.

This sub-section is especially relevant where synthetic subjects can run shell commands, execute notebooks, launch containers, install packages, start local servers, create daemons, or operate inside developer workstations and continuous integration environments.