registry / @bakit-org/cli / 1.1.14

@bakit-org/cli@1.1.14

BA-kit CLI — AI-powered Business Analyst toolkit for Claude Code

AI Security Review

scanned 18d ago · by lpm-firewall-ai

No confirmed malware or exfiltration was found. There is a real install-time mutation risk because the lifecycle hook deletes stale BA-kit-named files from ~/.local/bin without a user prompt.

Static reason

One or more suspicious static signals were detected.

Trigger

npm install runs postinstall.js; user-invoked ba-kit install/update downloads and installs BA-kit content

Impact

May remove local BA-kit-named binaries during package install; user-invoked install/update can add Claude Code hooks and files under ~/.claude

Mechanism

install hook cleanup plus explicit CLI framework installer

Attack narrative

The package is not a confirmed malicious payload. Its risky behavior is operational: npm install runs postinstall.js, which removes BA-kit-named files in ~/.local/bin if they are regular files, and the user-invoked installer later downloads product releases with gh and registers Claude Code hooks under ~/.claude/settings.json.

Rationale

Static inspection supports a package-aligned BA-kit/Claude Code installer, not credential theft, covert execution, or exfiltration. The automatic lifecycle deletion outside the package directory is enough to warn, but the behavior is narrowly scoped and explained in source comments.

Evidence

package.jsonpostinstall.jsba-kitREADME.md~/.local/bin/ba-kit~/.local/bin/ba-kit.cmd~/.local/bin/ba-kit.ps1~/.claude/settings.json~/.claude/ba-kit~/.claude/hooks~/.claude/skills~/.claude/agents

@bakit-org/cli@1.1.14

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Source & flagged code