[Bug][cyber] AD/M365 audit wrongly blocked: list distribution-group members with active mailboxes (req_011CcHRaJHnvVgAPQoxCp8X8)

Open 💬 1 comment Opened Jun 25, 2026 by sworrl

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

Why this is a false positive

The blocked message was part of a routine systems-administration session — managing an email distribution group on an account the operator owns, then asking how to migrate a local application into an LXC/container and move it between a workstation and a hypervisor. None of this involves offensive security, exploitation, or any cybersecurity topic; the request concerns ordinary containerization and virtualization on the user's own infrastructure. The cybersecurity classifier appears to have misfired on benign infrastructure and account-management language, producing a false positive that halts 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-22T01:24:01.856Z.

Request IDs (lookup-able server-side)

  • req_011CcHRaJHnvVgAPQoxCp8X8 (2026-06-22T01:24:01.856Z)

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_011CcHRaJHnvVgAPQoxCp8X8

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

---
<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 ↗