Skip to content

Rule Reference

SEC399lintai-ai-securitygovernancehardeningpreviewclaude_settingswarn

Claude settings: shared npx Bash permissions

Claude settings permissions allow `Bash(npx ...)` in a shared committed config

Public lane
governance
Category
hardening
Provider
lintai-ai-security
Scope
per-file
Surface
claude_settings
Tier
preview
Severity
warn
Confidence
high
Detection
structural
Remediation
message only
How to read this lane

Shared authority and workflow policy review.

How to read this category

Least-privilege, provenance, or operational hygiene signal.

Activation Model

Preset Activation

These presets explain where this rule appears in the product experience.

Lifecycle

Stable Lifecycle Contract

State

stable

Graduation rationale

Checks shared committed Claude settings for exact `Bash(npx ...)` mutable package-runner authority.

Deterministic signal basis

ClaudeSettingsSignals exact permission detection for `Bash(npx ...)` entries inside permissions.allow.

Malicious corpus
claude-settings-npx-permission
Benign corpus
claude-settings-npx-specific-safe
structured evidence required remediation reviewed
Canonical note

Structural preview rule; deterministic today, but the preview contract may still evolve.

Nearby Signals

Related Rules

SEC399 / CLAUDE-NPX-PERMISSION

SEC399 flags shared Claude settings when permissions.allow grants a Bash(npx ...) permission.

Why It Matters

npx executes mutable package resolution by default. Granting it directly in a shared AI policy makes package execution authority part of the default team config, which is harder to review and easier to cargo-cult than a pinned wrapper or a narrower reviewed command.

Trigger Shape

The rule triggers only when all of these are true:

  • the file is a detected Claude settings surface
  • the path is not fixture-like
  • permissions.allow contains a string that starts with Bash(npx

Clean Cases

These stay clean:

  • specific non-npx Bash permissions such as Bash(node server.js)
  • settings files that do not grant Bash execution at all
  • fixture-like examples under test or fixture paths

Example Trigger

json
{
  "permissions": {
    "allow": ["Bash(npx claude-flow:*)", "Read(*)"]
  }
}

Safer Example

json
{
  "permissions": {
    "allow": ["Bash(./scripts/claude-flow-wrapper)", "Read(*)"]
  }
}

How To Fix

Replace shared Bash(npx ...) permissions with a pinned wrapper or a narrower reviewed command permission that does not grant mutable package execution by default.