@keruyun/agent-cli@1.4.16
客如云 CLI 工具
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is a transparent but automatic remote-binary installer with silent host and session telemetry. No source evidence establishes secret theft, broad persistence, agent-control mutation, or an unverified payload chain, so blocking is not warranted.
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 runs postinstall during package installation.
Impact
A remote artifact selected by package metadata becomes the CLI executable; installation metadata is sent to a third-party logging host.
Mechanism
Remote binary staging with silent installation telemetry.
AI rationale
This is a transparent but automatic remote-binary installer with silent host and session telemetry. No source evidence establishes secret theft, broad persistence, agent-control mutation, or an unverified payload chain, so blocking is not warranted.
Evidence
package.jsonbinaries.jsoninstall.cjsbin/kry-cli.exe
Network endpoints2
s.koubei.comtnnm-alsc-saas-merchant-spider-fy21.cn-wulanchabu.log.aliyuncs.com
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The automatic postinstall hook downloads and replaces the CLI binary.
- The downloaded executable is opaque to this source review and is fetched from a remote CDN.
- Postinstall silently sends host, user-path-derived, session, and npm environment metadata to a logging endpoint.
Evidence against
- The downloader verifies both compressed and decompressed SHA-256 values before writing the binary.
- Writes are limited to the package's bin/kry-cli.exe path; no broad project or agent-configuration mutation was found.
- No self-dependency, secret-file harvesting, shell payload execution, or evaluator-directed text was found.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
8 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node install.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node install.cjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkginstall.cjsView file
28*
L29: * 首装曾是唯一一段完全没有观测的路径：下面那 8 条返回路径以前只写 stderr，而 npm 通常把
L30: * postinstall 的 stderr 折叠掉 —— 于是「有多少人装不上、卡在下载还是校验、哪个平台最惨」
...
L50: const zlib = require('zlib');
L51: const { execFileSync } = require('child_process');
L52:
L53: const BIN_DIR = path.join(__dirname, 'bin');
L54: const TARGET = path.join(BIN_DIR, 'kry-cli.exe');
...
L65: function log(msg) {
L66: process.stdout.write(`${LOG_PREFIX} ${msg}\n`);
L67: }
...
L73: try {
High
Install Named Payload File
Install-named source file stages remote content through filesystem writes and execution.
Findings
5 High6 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
HighInstall Named Payload Fileinstall.cjs
HighKnown Malware Source Similarityinstall.cjs
HighKnown Malware Source Similaritybin/sdk.mjs
HighKnown Malware Source Fingerprint Signatureinstall.cjs
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumShips Native Binarybin/kry-cli.exe
MediumShips Build Helperbin/log.py
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to @keruyun/agent-cli@1.4.16.
See all versions of @keruyun/agent-cli for other recorded verdicts.
- Review the evidence and your use of @keruyun/agent-cli@1.4.16 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.