Skip to content

Responsible use

This site documents OS command injection so that security teams can find it, developers can fix it, and defenders can detect it. Every technique is published for authorized testing and secure development only. This responsible-use policy explains the boundaries that come with that.

Authorized testing only

Only test systems you own or have explicit, written permission to assess. Authorization should name the in-scope targets, the permitted techniques, the testing window and a point of contact. Running command injection payloads against systems without authorization is illegal in most jurisdictions and can cause real harm, regardless of intent.

Lead with the defensive value

The reason every entry on this site pairs an attack with detection and a concrete fix is that the fix is the point. If you are a developer, you can go straight to the prevention guide and never read a payload in anger. If you are a defender, each technique page lists the signals and log sources that reveal the attack.

Stay within scope and minimize impact

  • Use harmless proof-of-execution markers (for example a timing delay or a callback to infrastructure you control) rather than destructive commands.
  • Do not exfiltrate real data, pivot beyond the agreed scope, or leave persistent changes on the target.
  • Prefer the least-invasive confirmation that proves the finding, and stop once it is proven.
  • Record what you did so the finding can be reproduced and verified after it is fixed.

Report and remediate

Disclose findings privately to the system owner with enough detail to reproduce and fix them, and give reasonable time to remediate before any public discussion. A good report includes the vulnerable sink, the proof of execution, the impact, and the remediation — the same structure every technique page follows.

No content from third parties is reproduced

The payloads and explanations here are written for this site. Reference sources are credited on each page for further reading; their text is not reproduced.

Legal

Nothing on this site is a license or authorization to attack any system. The content is provided for lawful, authorized security testing and defensive engineering. You are responsible for complying with all applicable laws and the terms of any authorization you hold. See also the terms and privacy pages.

Questions or corrections: hello@commandinjectionpayloads.com.