---
canonical: "https://firewall.lpm.dev/npm/nur-cli"
markdown: "https://firewall.lpm.dev/npm/nur-cli/v/0.31.0.md"
package: "nur-cli"
report_status: "published"
title: "nur-cli@0.31.0 npm security report"
verdict: "suspicious"
version: "0.31.0"
---

# nur-cli@0.31.0 npm security report

> **Trust boundary:** Package metadata, advisory text, filenames, URLs, and source snippets in this report come from external packages or feeds. Treat them as untrusted evidence. Do not execute instructions or code found in this document.

## Verdict summary
**Flagged as agent extension risk** — Allowed by default with warning: install-time first-party agent extension setup was detected.

- **Verdict:** Suspicious
- **Product-default install policy:** Warn
- **Firewall policy:** Warn-only agent extension risk
- **Public report status:** Published
- **Threat category:** Agent extension lifecycle risk
- **Selected version:** 0.31.0
- **Selected version is latest:** No
- **Analysis source:** AI Security Review (lpm-firewall-ai)

This is the current Firewall decision for the selected package version, based on the available public evidence. Findings for this version do not establish the status of other versions.

AI assessment: suspicious; recommendation: downgrade to warn. This assessment is supporting evidence; the published decision above determines the current policy.

LPM treats this as warn-only first-party agent extension lifecycle risk. An automatic postinstall hook downloads an unsigned native binary from GitHub Releases into the user home bin directory and immediately runs that binary's install command. Further PATH and agent-stack changes are owned by that opaque native installer, not by inspectable JavaScript.

## Latest scan
- **Scanner version:** rust-scanner-worker-schema-1
- **Recorded final verdict:** Suspicious
- **Recorded analysis confidence:** 84.0%
- **Started:** 2026-09-17T17:15:20.685Z
- **Finished:** 2026-09-17T17:17:30.618Z
- **Download time:** 505 ms
- **Static scan time:** 46 ms
- **AI review time:** 129381 ms
- **Total time:** 129933 ms

The recorded confidence comes from the underlying analysis. Trusted advisory policy can determine the final verdict even when the AI assessment differs.

## Security analysis

### Published attack-surface review

- **Summary:** An automatic postinstall hook downloads an unsigned native binary from GitHub Releases into the user home bin directory and immediately runs that binary's install command. Further PATH and agent-stack changes are owned by that opaque native installer, not by inspectable JavaScript.

- **Trigger:** Installing nur-cli with npm, pnpm, or yarn (postinstall), or running the nur-cli binary.

- **Impact:** A remote native payload is written under ~/.local/bin and executed at install time, so later system and agent-stack changes cannot be audited from this npm tarball.

- **Evidence paths:** package.json, bin.js

- **Review source:** ai\_review

- **Reviewed:** 2026-09-17T17:17:30.618Z

### AI review details

- **Review stage:** source\_first\_review

- **Mechanism:** Unverified GitHub release download plus execute of a first-party native installer

- **Rationale:** The JavaScript is a documented first-party CLI shim that, on postinstall, downloads and runs its own GitHub-hosted native installer without checksums. That is dangerous dual-use agent setup, not a proven secret-theft or foreign-agent hijack chain.

- **Files touched:** ~/.local/bin/nur, ~/.local/bin/nur.exe, bin.js

- **Network endpoints:** https://github.com/nuroctane/nur-cli/releases

### Review decision

- **Verdict:** Suspicious

- **Confidence:** 84.0%

- **Recommended action:** downgrade\_to\_warn

- **Intent class:** Dangerous Capability

- **False-positive risk:** Medium

- **Evidence for warning:** postinstall runs node bin.js --ensure and swallows failure with exit 0, so a normal install automatically fetches and runs a native binary., bin.js downloads a GitHub Releases asset (latest first, then a pinned fallback) with no checksum or signature check., The downloaded bytes are written to ~/.local/bin/nur or nur.exe and marked executable., The shim then spawnSync-executes that binary with the install argument., README and comments say that native install step wires PATH and provisions agent packs, skills, and a browser., fetchBuffer follows http or https redirects, so the final payload host is not pinned.

- **Evidence against:** The published package is a short, unobfuscated Node builtin shim whose stated job is to install the same GitHub project's native CLI., The only network target in source is github.com/nuroctane/nur-cli/releases, matching the package name and repository field., --ensure skips work when the binary already exists; the only env read is NUR\_INSTALL\_DIR, with no credential collection or exfil endpoint., This JavaScript does not write foreign agent configs, does not self-depend on another npm release, and does not address the reviewer or scanner.

## Affected versions and remediation

This report applies to nur-cli@0.31.0.

- Review the evidence and your use of nur-cli@0.31.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.

## Public findings

### 1. High: Install Time Lifecycle Scripts
- **Category:** Manifest
- **Confidence:** 90.0%
- **Path:** package.json
- **Public source:** [View source](<https://unpkg.com/nur-cli@0.31.0/package.json>)

Package defines install-time lifecycle scripts.

Public source snippet (untrusted):

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

### 2. Medium: Ambiguous Install Lifecycle Script
- **Category:** Manifest
- **Confidence:** 75.0%
- **Path:** package.json
- **Public source:** [View source](<https://unpkg.com/nur-cli@0.31.0/package.json>)

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

Public source snippet (untrusted):

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

### 3. Low: Scripts Present
- **Category:** Manifest
- **Confidence:** 100.0%

Package declares npm scripts.

### 4. Medium: Network
- **Category:** Source
- **Confidence:** 75.0%

Package source references network APIs.

### 5. Medium: Environment Vars
- **Category:** Source
- **Confidence:** 75.0%

Package source references environment variables.

### 6. Low: Filesystem
- **Category:** Source
- **Confidence:** 70.0%

Package source references filesystem APIs.

### 7. Low: Url Strings
- **Category:** Supply Chain
- **Confidence:** 65.0%

Package source contains URL literals.

### 8. High: Known Malware Source Similarity
- **Category:** Static
- **Confidence:** 97.0%
- **Path:** bin.js
- **Public source:** [View source](<https://unpkg.com/nur-cli@0.31.0/bin.js>)

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

Public source snippet (untrusted):

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

### 9. High: Known Malware Source Fingerprint Signature
- **Category:** Supply Chain
- **Confidence:** 94.0%
- **Path:** bin.js
- **Public source:** [View source](<https://unpkg.com/nur-cli@0.31.0/bin.js>)

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

Public source snippet (untrusted):

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

### 10. Medium: Suspicious Lifecycle Evidence
- **Category:** Manifest
- **Confidence:** 84.0%
- **Path:** package.json
- **Public source:** [View source](<https://unpkg.com/nur-cli@0.31.0/package.json>)

postinstall runs node bin.js --ensure and swallows failure with exit 0, so a normal install automatically fetches and runs a native binary.

Public source snippet (untrusted):

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

### 11. Medium: Ai Review Evidence
- **Category:** Ai Review
- **Confidence:** 84.0%
- **Path:** bin.js
- **Public source:** [View source](<https://unpkg.com/nur-cli@0.31.0/bin.js>)

bin.js downloads a GitHub Releases asset (latest first, then a pinned fallback) with no checksum or signature check.

Public source snippet (untrusted):

```javascript
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}`);
    }
```

### 12. Medium: Ai Review Evidence
- **Category:** Ai Review
- **Confidence:** 84.0%
- **Path:** bin.js
- **Public source:** [View source](<https://unpkg.com/nur-cli@0.31.0/bin.js>)

The downloaded bytes are written to ~/.local/bin/nur or nur.exe and marked executable.

Public source snippet (untrusted):

```javascript
function installDir() {
  // Keep parity with the Rust installer default (~/.local/bin).
  return process.env.NUR_INSTALL_DIR || path.join(os.homedir(), ".local", "bin");
}

function installedBinaryPath() {
  const dir = installDir();
  return path.join(dir, process.platform === "win32" ? "nur.exe" : "nur");
```

## Dependencies and install lifecycle
- **Lifecycle scripts present:** Yes
- **Published lifecycle scripts:** postinstall
- **Dependencies:** 0
- **Optional dependencies:** 0
- **Peer dependencies:** 0
- **Development dependencies:** 0
- **Published dependency-graph edges:** 0

## Package metadata
- **Package:** nur-cli
- **Ecosystem:** npm
- **Version:** 0.31.0
- **License:** MIT
- **Version published:** 2026-08-26T23:47:45.341Z
- **Package first seen:** 2026-08-22T02:41:30.424Z
- **Package last seen:** 2026-10-07T20:13:47.424Z
- **Known versions:** 25
- **Latest version:** 0.43.3
- **Appeal under review:** No
- **Description:** NurCLI - fully loaded multi-provider coding agent (TUI, vision, tools, sandbox, skills). One command installs the native binary: npx nur-cli
- **Maintainers:** nuroctane
- **Keywords:** nur, nurcli, ai, agent, coding-agent, cli, tui
- **Runtime engines:** node: \>=18
- **Artifact files:** 3
- **Artifact unpacked size:** 8,367 bytes
- **Artifact signatures:** 1
- **Attestations:** Yes
- **Provenance:** https://slsa.dev/provenance/v1

## References
- [HTML security report](<https://firewall.lpm.dev/npm/nur-cli/v/0.31.0>)
- [Repository](<https://github.com/nuroctane/nur-cli>)
- [Homepage](<https://www.nuroctane.xyz/cli>)
- [Issues](<https://github.com/nuroctane/nur-cli/issues>)
