lintai docs

Appearance

Rule Reference

SEC493lintai-ai-securitypreviewclaude_settingswarn

Claude settings: shared bunx Bash permissions

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

Provider
lintai-ai-security
Surface
claude_settings
Scope
per_file
Tier
preview
Severity
warn
Confidence
high
Detection
structural
Remediation
message_only

Activation Model

Preset Membership

This rule is part of the builtin activation graph through these preset memberships.

previewmembership
claudemembership

Lifecycle

Stable Lifecycle Contract

State

stable_gated

Graduation rationale

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

Deterministic signal basis

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

Malicious corpus
claude-settings-npm-exec-bunx-permissions
Benign corpus
claude-settings-npm-exec-bunx-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

SEC361Claude settings: missing `$schema`Claude settings file is missing a top-level `$schema` referenceclaude_settingspreview
SEC363Claude settings: home-directory hook pathClaude settings hook command uses a home-directory path in a shared committed configclaude_settingspreview
SEC365Claude settings: non-HTTPS allowed HTTP hook URLClaude settings allow non-HTTPS HTTP hook URLs in a shared committed configclaude_settingspreview
SEC366Claude settings: dangerous HTTP hook host literalClaude settings allow dangerous host literals in `allowedHttpHookUrls`claude_settingspreview
SEC368Claude settings: repo-external absolute hook pathClaude settings hook command uses a repo-external absolute path in a shared committed configclaude_settingspreview
SEC381Claude settings: command hook missing `timeout`Claude settings command hook should set `timeout` in a shared committed configclaude_settingspreview

SEC493 / CLAUDE-BUNX-PERMISSION ​

SEC493 flags shared Claude settings when permissions.allow grants Bash(bunx ...).

Why It Matters ​

bunx resolves and executes packages through a mutable runner path. Shared Claude settings should not quietly make that a default team capability.

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(bunx

Clean Cases ​

These stay clean:

  • non-bunx commands such as Bash(bun run lint)
  • settings without Bash(bunx ...)
  • fixture-like examples under test or fixture paths

Example Trigger ​

json
{
  "permissions": {
    "allow": ["Bash(bunx prettier:*)", "Read(*)"]
  }
}

Safer Example ​

json
{
  "permissions": {
    "allow": ["Bash(bun run lint)", "Read(*)"]
  }
}

How To Fix ​

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