Loading npm security reports…

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

registry / nur-cli / 0.36.4

nur-cli@0.36.4

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 27d ago · by lpm-firewall-ai

Installing the package triggers a postinstall hook that downloads an opaque native executable and runs it. The executable is persisted in the user's local bin directory and can perform further installation actions outside the inspected source.

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 installation, including a global install, when no existing nur binary is found.

Impact

An unverified mutable remote payload receives code execution during package installation and can alter the user environment.

Mechanism

Postinstall remote binary download, persistence, and execution.

Attack narrative

The package's postinstall hook invokes bin.js automatically. It follows redirects to GitHub release URLs, accepts any payload over one megabyte without integrity verification, saves it as a local executable, then runs that executable with the install argument. This creates automatic remote code execution during installation; the native payload and its subsequent actions are not available for review in this package.

AI rationale

This is an automatic install-time remote payload execution chain with persistence and no cryptographic verification. The opaque executable is immediately authorized to perform further installation actions, so the package should be blocked.

Evidence

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

Network endpoints1

github.com

Decision evidence

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.0 matchedPath = bin.js matchedIdentity = npm:bnVyLWNsaQ:0.36.0 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.0 matchedPath = bin.js matchedIdentity = npm:bnVyLWNsaQ:0.36.0 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

50/** Follow redirects; resolve with the body Buffer, reject on non-200. */ function fetchBuffer(url, redirects) { const maxRedirects = redirects == null ? 6 : redirects; return new Promise((resolve, reject) => { const mod = url.startsWith("http://") ? http : https; const req = mod.get( url, { headers: { "user-agent": "nur-cli-npm-shim" } }, (res) => { const status = res.statusCode || 0; if (status >= 300 && status < 400 && res.headers.location) { res.resume(); if (maxRedirects <= 0) return reject(new Error("too many redirects"));

High

Ai Review Evidence

The hook fetches a release asset through redirects, with no signature or hash verification.

bin.jsView on unpkg · L50

127const dest = installedBinaryPath(); fs.writeFileSync(dest, buf); if (asset.execBit) fs.chmodSync(dest, 0o755); process.stdout.write(`nur-cli: installed ${dest}\n`); return dest; } function runNurInstall(bin) { // Full one-stop install: PATH wiring, prereqs, ecosystem packs, browser. // The binary owns all of it - same as double-clicking a release EXE. const r = spawnSync(bin, ["install"], { stdio: "inherit" });

High

Ai Review Evidence

It writes the downloaded native executable to the user's local bin directory and immediately runs its install command.

bin.jsView on unpkg · L127