registry  /  @mflrevan/wipe  /  0.3.6

@mflrevan/wipe@0.3.6

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

AI Security Review

scanned 2d ago · by lpm-firewall-ai

Install-time code fetches a platform-specific executable archive from GitHub Releases, extracts it into the package, and later executes it through the `wipe` CLI. The inspected JavaScript contains no direct malicious action, but the remote binary is unchecked.

Static reason
One or more suspicious static signals were detected.
Trigger
npm install executes the `postinstall` hook; invoking `wipe` executes the installed binary.
Impact
A compromised or substituted release artifact could execute with the installing user's privileges.
Mechanism
Unchecked remote binary download, extraction, and execution.
Rationale
The source is a package-aligned native CLI installer rather than direct malware, but it performs an unverified install-time remote binary fetch and exposes that artifact to execution. This warrants a warning for staged-payload risk, not a publication block.
Evidence
package.jsoninstall.jsbinary.jsbinary-install.jsrun-wipe.jsnode_modules/.bin_realtemporary archive in the OS temp directory
Network endpoints1
github.com/mflRevan/wipe/releases/download/v0.3.6

Decision evidence

public snapshot
AI called this Suspicious at 90.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
  • `package.json` runs `node ./install.js` in `postinstall`.
  • `binary.js` constructs release URLs from the GitHub artifact base.
  • `binary-install.js` downloads a streamed archive and extracts it with `tar`/`unzip`.
  • Downloaded contents are placed in `node_modules/.bin_real` without a checksum or signature check.
  • `run-wipe.js` invokes the downloaded `wipe` executable.
Evidence against
  • No credential, home-directory, SSH, or environment harvesting beyond Windows `SystemRoot` for `tar.exe`.
  • No evidence of exfiltration, hidden persistence, destructive file targeting, eval, or AI-agent configuration writes.
  • Network destination is package-aligned GitHub Releases and the installer behavior matches a native CLI bootstrapper.
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