registry / naabigacode / 0.1.1

naabigacode@0.1.1

NaabigaCode — agentic coding en terminal (TUI style Claude Code + backend Python). Installation one-shot : backend auto-installé dans ~/.naabiga.

AI Security Review

scanned 3d ago · by lpm-firewall-ai

Installation fetches a mutable remote backend and executes its dependency installation without user interaction. This creates install-time remote code execution outside the npm tarball.

Static reason

One or more suspicious static signals were detected.

Trigger

npm install, via postinstall

Impact

A changed remote archive or its Python dependencies can execute code during package installation.

Mechanism

downloads main-branch archive, copies backend, and invokes pip

Attack narrative

During npm installation, postinstall downloads a GitHub archive from the mutable main branch, extracts and copies its backend into the user's home directory, creates a virtual environment, and runs pip against downloaded requirements. The package tarball therefore delegates executable install-time behavior to content not integrity-pinned by npm.

Rationale

The lifecycle hook performs an unconsented, mutable remote payload fetch and executes installation commands derived from it. This is a concrete install-time remote-code-execution supply-chain risk.

Evidence

package.jsonscripts/install-backend.mjscli.mjsREADME.md~/.naabiga/backend~/.naabiga/backend/.venv~/.naabiga/backend/requirements.txt

Network endpoints1

github.com/n8nprobf-hub/NaabigaCode/archive/refs/heads/main.tar.gz

naabigacode@0.1.1

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Source & flagged code