Loading npm security reports…

nur-cli@0.33.0: Malicious npm security report (Block) | LPM Firewall

registry / nur-cli / 0.33.0

nur-cli@0.33.0

NurCLI - fully loaded multi-provider coding agent (TUI, vision, tools, sandbox, skills). One command installs the native binary: npx nur-cli

AI Security Review

scanned 24d ago · by lpm-firewall-ai

Installing the package triggers a download of an unverified, mutable native binary and executes it automatically. The package also writes that binary under the user's home directory.

Static reason

One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review

Trigger

npm postinstall runs node bin.js --ensure when the binary is absent.

Impact

A release-controlled binary obtains arbitrary code execution during dependency installation and can alter the user environment.

Mechanism

Remote native payload download, home-directory write, and automatic execution.

Attack narrative

A package installation invokes its postinstall hook. When no local binary exists, the hook downloads a platform-specific executable from a mutable GitHub release URL, writes it to the user's home bin directory, marks it executable on Unix, and runs its install command. No cryptographic integrity verification binds the executed binary to the reviewed npm package.

AI rationale

This is a concrete automatic remote-code-execution chain during installation, with an opaque native payload fetched from a mutable latest-release endpoint. The source also persists the payload in the user's home bin directory.

Evidence

package.jsonbin.js~/.local/bin/nur

Network endpoints2

github.com/nuroctane/nur-cli/releases/latest/downloadgithub.com/nuroctane/nur-cli/releases/download/v0.31.0

Source & flagged code

7 flagged · loading source

package.jsonView file

•scripts.postinstall = node bin.js --ensure || exit 0

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

30"scripts": { "postinstall": "node bin.js --ensure || exit 0" }

High

Suspicious Lifecycle Evidence

The postinstall hook automatically invokes the downloader.

package.jsonView on unpkg · L30

•scripts.postinstall = node bin.js --ensure || exit 0

Medium

Ambiguous Install Lifecycle Script

Install-time lifecycle script is not statically allowlisted and needs review.

package.jsonView on unpkg

bin.jsView file

•matchType = normalized_sha256 matchedPackage = nur-cli@0.36.4 matchedPath = bin.js matchedIdentity = npm:bnVyLWNsaQ:0.36.4 similarity = 1.000 summary = normalized source hash matched finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

bin.jsView on unpkg

•matchType = malicious_source_fingerprint_signature signature = b921eac94efd58ac signatureType = suspicious_hashes sourceLabel = final_verdict:malicious matchedPackage = nur-cli@0.36.4 matchedPath = bin.js matchedIdentity = npm:bnVyLWNsaQ:0.36.4 similarity = 1.000 shingleOverlap = 1 summary = package final verdict is malicious

High

Known Malware Source Fingerprint Signature

Source fingerprint signature matches a known malicious package signature; route for source-aware review.

bin.jsView on unpkg

98// Try every (asset, version) combination: latest first, then the pinned // fallback version. Covers legacy release layouts too. const versions = ["latest/download", `download/v${FALLBACK_VERSION}`]; const urls = []; for (const v of versions) { for (const name of asset.names) { urls.push(`https://github.com/${REPO}/releases/${v}/${name}`); } }

High

Ai Review Evidence

The shim fetches a latest-release native executable from GitHub without a checksum or signature verification.

bin.jsView on unpkg · L98

127const dest = installedBinaryPath(); fs.writeFileSync(dest, buf); if (asset.execBit) fs.chmodSync(dest, 0o755);

High

Suspicious Lifecycle Evidence

It writes the downloaded executable into the user's home bin directory and executes its install subcommand during postinstall.

bin.jsView on unpkg · L127