[Bug][cyber] Safety block halted forensic triage of an internal BEC vendor-impersonation invoice-fraud email (req_011CcPHGQUTEyyNZENQ41hkH)

Open 💬 2 comments Opened Jun 25, 2026 by sworrl

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

Why this is a false positive

A defensive email-security investigation—reading message headers in an authorized mailbox to identify a business-email-compromise/vendor-impersonation fraud attempt—was flagged as a prohibited cybersecurity topic. This is standard incident response and fraud triage performed by an authorized account holder on their own inbox, not offensive tooling or attacker tradecraft. The classifier appears to be keying on terms like "compromised account," "spoofing," and "invoice fraud" without distinguishing defensive analysis from malicious activity, producing a false positive that blocks legitimate, in-scope work.

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-25T03:38:33.473Z.

Request IDs (lookup-able server-side)

  • req_011CcPHGQUTEyyNZENQ41hkH (2026-06-25T03:38:33.473Z)

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_011CcPHGQUTEyyNZENQ41hkH

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

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

View original on GitHub ↗

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