encrata-cli@0.12.1
Encrata CLI — intelligence lookups from your terminal
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is a real install-time remote-payload risk because the native archive is unchecked. The source otherwise confines writes to the package and targets the declared project repository, so malicious behavior is not established.
Static reason
One or more suspicious static signals were detected.
Trigger
npm installation runs postinstall; invoking encrata launches the downloaded binary.
Impact
A compromised release asset or redirect target could supply arbitrary native code to the installing user.
Mechanism
Unchecked remote native-binary download and execution.
AI rationale
This is a real install-time remote-payload risk because the native archive is unchecked. The source otherwise confines writes to the package and targets the declared project repository, so malicious behavior is not established.
Evidence
package.jsoninstall.jsbin/encratabin/.extractbin/encrata-binbin/encrata-bin.exe
Network endpoints1
github.com/Encratahq/encrata-cli/releases/download/v0.12.1/
Decision evidence
public snapshotAI called this Suspicious at 89.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The automatic postinstall hook runs the downloader during npm installation.
- The installer downloads a platform-native archive from GitHub, follows redirects, and has no checksum or signature verification.
- The archive is extracted into the package, made executable, and later launched by the CLI shim.
Evidence against
- The download URL is fixed to the package's named GitHub repository and matching version.
- The installer writes only under its own bin directory; no credential harvesting or broad system mutation is present in the inspected source.
- The downloaded executable is launched only when the user invokes the encrata command.
Behavioral surface
ChildProcessFilesystemNetwork
UrlStrings
Source & flagged code
7 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node install.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg2scripts.postinstall = node install.js
Install-time code downloads an unverified remote native archive, stages it locally, activates an executable path, and exposes it to process execution.
L2:
L3: const { existsSync, mkdirSync, createWriteStream, chmodSync, unlinkSync, copyFileSync, rmSync } = require("fs");
L4: const path = require("path");
L5: const https = require("https");
L6: const { execSync } = require("child_process");
...
L30:
L31: const ext = process.platform === "win32" ? ".zip" : ".tar.gz";
L32: // Name of the binary *inside* the GoReleaser archive.
...
L37: const assetName = `encrata_${VERSION}_${platform}_${arch}${ext}`;
L38: const url = `https://github.com/${REPO}/releases/download/v${VERSION}/${assetName}`;
L39:
...
L52: return new Promise((resolve, reject) => {
High
Unverified Remote Native Payload Install
Install-time source downloads a native archive from a fixed external host without transport verification, extracts it, and installs an executable payload.
package.jsonView on unpkg · L2•scripts.postinstall = node install.js
Medium
Findings
2 High6 Medium3 Low
HighInstall Time Lifecycle Scriptspackage.json
HighUnverified Remote Native Payload Installpackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumSuspicious Lifecycle Evidencepackage.json
MediumAi Review Evidenceinstall.js
MediumAi Review Evidenceinstall.js
MediumAi Review Evidencebin/encrata
LowScripts Present
LowFilesystem
LowUrl Strings
Affected versions and remediation
This report applies to encrata-cli@0.12.1.
See all versions of encrata-cli for other recorded verdicts.
- Review the evidence and your use of encrata-cli@0.12.1 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.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.