Poisoned Pipeline

Poisoned Pipeline / Techniques / T0166

T0166 · Execution · TA04 · observed in 18 incident(s)

Trigger pipeline execution

CI/CD Posture SCM Posture

The Trigger pipeline execution (Poisoned pipeline execution) attack abuses permissions against an SCM repository, in a way that causes a CI pipeline to execute malicious commands.
Users that have permissions to manipulate the CI configuration files, or other files which the CI pipeline job relies on, can modify them to contain malicious commands, ultimately poisoning the CI pipeline executing these commands.
Pipelines executing unreviewed code, for example those which are triggered directly off of pull requests or commits to arbitrary repository branches, are more susceptible to Trigger pipeline execution.
The reason is that these scenarios, by design, contain code which has not undergone any reviews or approvals.
Once able to execute malicious code within the CI pipeline, the attacker can conduct a wide array of malicious operations, all within the context of the pipelines identity.

Where this idea came from

Security research

Identified in published CI/CD or supply-chain security research cited below.

Mitigations

Detections

Observed in incidents (18)

References