registry  /  @mflrevan/wipe  /  0.3.1

@mflrevan/wipe@0.3.1

wipe - CLI-first, git-native collaboration for humans and agents.

AI Security Review

scanned 9d ago · by lpm-firewall-ai

The package has an install-time platform binary downloader, but source inspection shows it only installs package-owned CLI artifacts into its own package directory. No confirmed malicious behavior or unconsented foreign agent control-surface mutation is present in the JavaScript package source.

Static reason
One or more suspicious static signals were detected.
Trigger
npm install postinstall; wipe CLI invocation
Impact
Installs and later runs the wipe CLI binary; no confirmed attack impact from inspected source
Mechanism
package-aligned prebuilt binary download and wrapper execution
Rationale
The suspicious primitives are consistent with a documented npm wrapper for a prebuilt CLI binary and are scoped to the package's own install directory. No source evidence shows exfiltration, persistence, destructive behavior, install-time AI-agent hijacking, or other concrete malicious behavior.
Evidence
package.jsoninstall.jsbinary.jsbinary-install.jsrun-wipe.jsREADME.mdnode_modules/.bin_real
Network endpoints3
github.com/mflRevan/wipe/releases/download/v0.3.1wipeboard.devgithub.com/mflRevan/wipe

Decision evidence

public snapshot
AI called this Clean at 83.0% confidence as Benign with low false-positive risk.
Evidence for block
  • package.json runs postinstall: node ./install.js.
  • install.js calls binary.install(false) at install time.
  • binary-install.js downloads a platform tarball with axios and extracts it using tar/unzip.
  • run-wipe.js invokes the downloaded binary from node_modules/.bin_real on CLI use.
Evidence against
  • Download URL is package-aligned GitHub release path from package.json.
  • No credential, env, home directory, or project file harvesting found in JS sources.
  • No AI-agent control-surface writes occur during lifecycle scripts.
  • README documents npm install as prebuilt binary download and agent skill install as explicit CLI command.
  • No remote code execution beyond extracting package-owned CLI binary and running it when wipe is invoked.
Behavioral surface
Source
ChildProcessEnvironmentVarsFilesystemNetwork
Supply chain
UrlStrings
ManifestNo manifest risk signals triggered.
scanned 4 file(s), 9.13 KB of source, external domains: example.com

Source & flagged code

4 flagged · loading source
package.jsonView file
scripts.postinstall = node ./install.js
High
Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg
scripts.postinstall = node ./install.js
Medium
Ambiguous Install Lifecycle Script

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

package.jsonView on unpkg
binary-install.jsView file
2const { join, sep } = require("path"); L3: const { spawnSync } = require("child_process"); L4: const { tmpdir } = require("os");
High
Child Process

Package source references child process execution.

binary-install.jsView on unpkg · L2
92L93: return axios({ ...fetchOptions, url: this.url, responseType: "stream" }) L94: .then((res) => { ... L101: if (/\.tar\.*/.test(this.zipExt)) { L102: const result = spawnSync(process.platform === "win32" ? join(process.env.SystemRoot || "C:\\Windows", "System32", "tar.exe") : "tar", ["xf", tempFile, L103: // The tarballs are stored with a leading directory
High
Same File Env Network Execution

A single source file combines environment access, network access, and code or shell execution; review context before blocking.

binary-install.jsView on unpkg · L92

Findings

3 High3 Medium3 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processbinary-install.js
HighSame File Env Network Executionbinary-install.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowUrl Strings