[Bug][cyber] False-positive safety block prevented analyzing a captured malware sample for incident forensics (req_011CcPfKEWKcTEycj5LWs7DG)

Open 💬 3 comments Opened Jun 25, 2026 by sworrl

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

Why this is a false positive

The block triggered on a malware-forensics task—analyzing malicious code to understand its behavior and build defenses—which is a standard, defensive cybersecurity activity that the model conflated with offensive intent. The request involved no creation or deployment of harmful capability; it was inspection and characterization of an existing sample for protective purposes, work that is explicitly in-scope under acceptable-use policy. Blanket-blocking the cybersecurity topic here prevents legitimate, authorized defensive analysis and forces a model downgrade with no corresponding reduction in actual risk.

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-06-25T08:27:34.683Z.

Request IDs (lookup-able server-side)

  • req_011CcPfKEWKcTEycj5LWs7DG (2026-06-25T08:27:34.683Z)

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]

Try rephrasing the request in a new session or change your model.

Learn more: https://support.claude.com/en/articles/15363606

Request ID: req_011CcPfKEWKcTEycj5LWs7DG

Environment: Claude Code, Linux. · Work domain: malware-forensics

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

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗