[Bug][cyber] Safety block on M365 account compromise audit during active incident response (req_011CcQG2XvBVrLop241EpzZd)

Open 💬 1 comment Opened Jun 25, 2026 by sworrl

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

Why this is a false positive

The block occurred during an active incident-response engagement: the task was a forensic audit of how a cloud identity account was compromised — reconstructing timeline, attack vector, and excessive OAuth scope grants so the affected user could remediate and change their behavior. This is purely defensive, read-oriented analysis of existing tenant logs and permission assignments, not credential theft, account takeover, or any offensive action. The trigger appears to be keyword co-occurrence (compromised account + broad OAuth scope names) rather than actual intent, which is a false positive on a core cloud-IAM IR workflow.

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-25T16:03:31.747Z.

Request IDs (lookup-able server-side)

  • req_011CcQG2XvBVrLop241EpzZd (2026-06-25T16:03:31.747Z)

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_011CcQG2XvBVrLop241EpzZd

Environment: Claude Code, Linux. · Work domain: cloud-iam

---
<sub>🔎 Filed automatically by ClAudit v2.0.21 — 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 ↗