[Bug][cyber] Safety block fired on routine model switch, halting work reviewing a local key file for a legitim (req_011CcmpAHRpVKhbp5QRqXmke)

Open 💬 1 comment Opened Jul 7, 2026 by sworrl

Triage: kind cyber · domain general · flagging model Opus 4.8 · severity session-halted (blocked authorized work) · reproducible: yes — server-side via the Request ID(s) below

Type: Cybersecurity safety-filter false positive · Work domain (heuristic): general

Why this is a false positive

The triggering message asked the assistant to inspect a locally-held key file to understand how it works in order to launch a P2P file-sharing client ([REDACTED]), a benign local development/config task with no exploit, credential-theft, or attack intent. The cybersecurity safeguard appears to have over-matched on the generic terms "sha key," producing a false positive that halted the entire session rather than just declining the specific request.

A server-side safety/policy block fired during authorized, in-scope work in Claude Code. Filing as a false positive. Recurred across 1 session(s); first seen 2026-07-07T01:16:41.898Z.

Request IDs (lookup-able server-side)

  • req_011CcmpAHRpVKhbp5QRqXmke (2026-07-07T01:16:41.898Z)

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's safeguards 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/8106465

Request ID: req_011CcmpAHRpVKhbp5QRqXmke

Environment: Claude Code, Linux. · Work domain: general

---
<sub>🔎 Filed automatically by ClAudit v2.0.104 — a FOSS tool for reporting false-positive Claude Code blocks.</sub>

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗