[Bug][cyber] Safety block stopped routine retrieval of a rotated server admin password during access troublesh (req_011CcCLBiJvdBLHMEJvGZu8n)
Type: Cybersecurity safety-filter false positive · Work domain (heuristic): general
Why this is a false positive
This request involved routine administration of self-owned network hardware—rotating a device credential stored in an internal database and diagnosing why a management web UI's connect button and an agent interface were not functioning correctly. The model's safety layer flagged the message as a cybersecurity threat, but no offensive, unauthorized-access, or exploit activity was present; the task is ordinary authorized infrastructure maintenance on the operator's own systems. The block prevents legitimate troubleshooting and appears to be triggered by surface keywords (e.g., credential rotation, database lookup) rather than any actual malicious intent or content.
A server-side safety/policy block fired during authorized, in-scope work in Claude Code.
Filing as a false positive. Recurred 2× across 1
session(s); first seen 2026-06-19T08:50:11.351Z.
Request IDs (lookup-able server-side)
req_011CcCLBiJvdBLHMEJvGZu8n(2026-06-19T08:50:11.351Z)req_011CcCLD7XhrTf56QMWdT56m(2026-06-19T08:50:30.346Z)
In-scope justification
False positive — in-scope, authorized security work; not out of scope. Filed automatically by claudit.
Block message
API Error: Opus 4.8 has safety measures that flagged this message for a cybersecurity topic. If your work requires this access, you can apply for an exemption: https://claude.com/form/cyber-use-case?token=[SCRUBBED]
Please double press esc to edit your last message or start a new session for Claude Code to assist with a different task.
Send feedback with /feedback or learn more: https://support.claude.com/en/articles/15363606
Request ID: req_011CcCLBiJvdBLHMEJvGZu8n
Environment: Claude Code, Linux. · Work domain: general
---
<sub>🔎 Filed automatically by ClAudit v2.0.21 — a FOSS tool for reporting false-positive Claude Code blocks.</sub>
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗