Quarantined patches¶
What the Quarantined badge means¶
When an error shows Quarantined (prompt injection), Patcherly detected that the error log may have been crafted to manipulate the AI. The suggested fix is not auto-applied, and connectors refuse to apply that patch until the quarantine is cleared.
Status is typically Manual review required.
Important: quarantine affects this error only. Your target keeps running, the connector stays active, and other errors on the same site are unaffected. This is different from Protection mode, which pauses the whole target.
Why a patch gets quarantined¶
Attackers can trigger errors whose messages contain fake instructions ("ignore previous rules", role markers, or unsafe code suggestions). Patcherly treats error text as untrusted data and blocks automated apply paths when the analysis is flagged suspicious.
Who can review or clear a quarantine?¶
| Role | What you can do |
|---|---|
| Anyone on your workspace | Open the error, read the log and detector signals, filter with Suspicious only on the Errors page |
| Workspace owner / admin / team with approve permission | Same as above — you cannot Mark as benign or Confirm suspicious in the dashboard; those actions are reserved for Patcherly Staff |
| Patcherly Staff | Confirm suspicious (keep quarantined) or Mark as benign (clear quarantine and return the error to normal review). Confirm notes are optional when AI/regex already recorded a reason (those details stay in the audit trail). Mark as benign still requires short notes. Patcherly Staff are notified when an error is quarantined. |
If you believe a quarantine is a false positive, open Support from the bottom of the dashboard sidebar and include the error ID. Patcherly Staff are notified automatically and can mark it benign after review.
You do not need to wait for clearance to fix a real bug on your server — see Manual fixes.
Reviewing a quarantined error (your workspace)¶
- Open Errors and use Suspicious only or look for the quarantine badge.
- Open the error detail — a banner explains that prompt-injection markers were detected.
- Review the original log, detector signals, and (when available) a plain-English summary of what the input said.
What happens when Patcherly Staff marks it benign¶
The suspicious flag is removed and the error returns to a normal workflow (typically Ready to Patch if a fix exists). You can then approve and apply through Patcherly if appropriate. The original quarantine context is preserved in audit logs.
What happens when Patcherly Staff confirms suspicious¶
The error stays quarantined. Auto-apply and connector apply paths remain blocked for that error. Apply any legitimate fix manually on your server if you determine the underlying issue is real.
Where to find all quarantined errors¶
On the Errors page, enable the Suspicious only filter (or add suspicious=true when using the API).
Related¶
- Security overview
- Prompt injection protection
- Protection mode — whole-target pause (separate from quarantine)
- Approving fixes
- Manual fixes