[Bug][cyber] Safety block halted mid-session Android/ADB kprobe validation on user's own rooted test device (req_011CcmMR7BwnuqKiVs2tCaVR)

Status Open
Maintainer reply None cached
Activity 4 comments · opened Jul 6, 2026

Triage: kind cyber · domain general · flagging model Opus 4.8 · 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): general

Why this is a false positive

The session was validating a kernel probe (kprobe) capture workflow on the user's own rooted Android test device over ADB — arming a probe, dumping a capture file, and tearing it down — standard on-device instrumentation/debugging work with no external target or network access involved. The block fired mid-flow after a benign interruption ("keyboard dropped"), stopping legitimate, already-authorized local device testing and forcing a session restart rather than a resume.

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-07-06T19:26:00.797Z.

Request IDs (lookup-able server-side)

  • req_011CcmMR7BwnuqKiVs2tCaVR (2026-07-06T19:26:00.797Z)

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'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_011CcmMR7BwnuqKiVs2tCaVR

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

Related reports (same work session, linked)

Distinct false-positive blocks from the same work session, each its own report:
#74882, #74887, #74898, #74899, #74909

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

View original on GitHub ↗

4 Comments

sworrl · 1 month ago

🔗 Related false positive from the same work session: #74919

github-actions[bot] · 1 month ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/74919
  2. https://github.com/anthropics/claude-code/issues/74839
  3. https://github.com/anthropics/claude-code/issues/74922

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

sworrl · 1 month ago

Not a duplicate — please do not auto-close. The duplicate-detector matched on similar titles, but it cited #74839, #74919, #74922, and each of those is a separate server-side incident with its own Request ID (listed above), fired on the reporter's own authorized infrastructure. Same class of false positive, different events at different times. Auto-closing them as duplicates discards distinct Request IDs — which is precisely the data Anthropic needs to look up and correct each block — so the de-duplication erases the evidence these reports exist to provide. Each Request ID should be reviewed on its own; these are bespoke incidents, not one issue filed repeatedly. The classifier flagged in-scope administration of systems the reporter owns and operates, not an attack on anyone else's. (Assessed by ClAudit; PII-scrubbed.)

<!-- claudit:defense -->

sworrl · 1 month ago

This should not be auto-closed as a duplicate. The bot matched these issues based on similar topic keywords, but the actual incidents are distinct: #74919, #74839, and #74922 each represent a separate server-side block event, identified by its own unique Request ID that can be independently looked up in infrastructure logs to determine root cause and scope. Auto-closing them as duplicates would discard those unique Request IDs—the precise identifiers Anthropic needs to investigate and fix each block individually. Consolidating distinct Request IDs into a single issue destroys the lookup evidence required for remediation. Please review each with its Request ID independently rather than de-duplicating them.

<!-- claudit:defense -->