Policy helper processes now start from a scrubbed environment, so loader and interpreter tricks can't hijack them.
What's wrong with this entry?
Helpers now start from a locked-down environment: credential variables are stripped as before, and loader and interpreter hijack variables (LD_, DYLD_, NODE_OPTIONS, BASH_ENV, CLASSPATH, OPENSSL_CONF) are dropped too, with PATH, COMSPEC, ZDOTDIR, XDG_CONFIG_HOME and the git config paths pinned at fixed values pointing into an empty directory.
- The credential list (
ANTHROPIC_API_KEY,AWS_SECRET_ACCESS_KEY,GOOGLE_APPLICATION_CREDENTIALSand others) and the TOKEN/SECRET/PASSWORD name pattern moved into a dedicated module next to the new sanitizer. - No flag gates this; it applies whenever a policy helper is spawned.
/var/empty/claude-code-policy-helper
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.228
A policy helper is only honoured from an admin settings source
Both mention policy helper
-
v2.1.239
Policy-helper warnings say which platform they apply to
Both mention policy helper
-
v2.1.228
Managed settings accept per-OS
policyHelpersBoth mention policy helper