GPR-003 · critical risk
Block known-malicious package installs
Block supported install actions for packages already classified as malicious.
Decision
block
Matcher
package = malicious-package
Reviewed
2026-08-09
Safe test cases
matching synthetic case
package = malicious-package → block
different benign synthetic case
package = benign-malicious-package → unmatched
Limitations
- This recipe requires a reviewed package identity and does not classify unknown packages by itself.
Review before applying
This recipe is a starting point, not a universal security policy. Open it in Policy Studio, replace example identifiers where necessary, review scope and blast radius, simulate where supported, and use the normal approval flow before enforcement.
Recipe SHA-256: 733a6355b8bbfe5cc54447875063fcdcc524347013ef7a4bfcb03299c6fb79ae
When a policy is saved and delivered through Guard Cloud, it uses the existing Guard policy-bundle compiler. If the policy-bundle signing key is configured, that compiler produces an RSA-PSS-SHA256 signed bundle that local Guard verifies before applying.