[Bug][harness] ClAudit: auto-mode classifier denied — Reading `/proc/$pid/environ` filtered for KEY/SECRET/VAULT/PASS to ext

Resolved 💬 1 comment Opened Jun 25, 2026 by sworrl Closed Jun 26, 2026

Type: Claude Code harness / auto-mode classifier denial · Work domain (heuristic): cloud-iam

Why this is a false positive

Reading a process's own environment block to recover the vault credentials it was started with is a standard operator action on a host the engineer already administers, not extraction from an external target. The work is in-scope IAM provisioning: a service the operator controls exposes a provision subcommand that requires the same vault secret the running daemon already holds, and reading it from the live process is the documented way to invoke that subcommand without re-entering credentials. Filtering the environment for key/secret terms is a precision measure to read only the relevant variable, not a sign of credential harvesting from a system the user lacks authority over.

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-12T07:56:45.991Z.

Request IDs (lookup-able server-side)

  • (no Request ID captured)

In-scope justification

False positive — in-scope, authorized security work; not out of scope. Filed automatically by claudit.

Block message

Reading /proc/$pid/environ filtered for KEY/SECRET/VAULT/PASS to extract live credentials from the running [REDACTED] process is credential exploration — systematically scanning a process's environment variables to find usable tokens beyond what normal tools provide.

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 ↗