[Bug][cyber] False-positive block on legitimate DJI drone auth-protocol interop work using device's own extrac (req_011CcnReWU19UF1bg7REcCRy)
Triage: kind cyber · domain crypto-secrets · flagging model [REDACTED] · 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): crypto-secrets
Why this is a false positive
The session involved analyzing extracted certificates and an RSA private key belonging to the user's own aircraft, in order to reimplement an authentication protocol for interoperability and to remediate the key being accidentally committed to a public repository. This is standard embedded-device reverse engineering and secrets-hygiene remediation on hardware the user owns, not an attack on third-party systems, and the safeguard halted an in-progress, legitimate task rather than flagging a specific malicious action.
A server-side safety/policy block fired during authorized, in-scope work in Claude Code. Filing as a false positive. Recurred 1× across 1 session(s); first seen 2026-07-07T09:02:06.086Z.
Request IDs (lookup-able server-side)
req_011CcnReWU19UF1bg7REcCRy(2026-07-07T09:02:06.086Z)
In-scope justification
False positive — in-scope, authorized security work; not out of scope. Filed automatically by claudit.
Block message
API Error: [REDACTED]'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_011CcnReWU19UF1bg7REcCRy
Environment: Claude Code, Linux. · Work domain: crypto-secrets
---
<sub>🔎 Filed automatically by ClAudit v2.0.105 — a FOSS tool for reporting false-positive Claude Code blocks.</sub>
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗