@keruyun/agent-cli@1.5.5
客如云 CLI 工具
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is a real install-time remote payload staging and telemetry surface, but the source pins hashes, confines writes to its own package binary, and does not execute the staged payload during installation. Static inspection cannot establish the downloaded executable's behavior.
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
Installing the package with npm lifecycle scripts enabled.
Impact
A remote executable is staged for later use, while host, session-derived, and package-manager metadata leave the machine during installation.
Mechanism
Postinstall remote native-binary staging and telemetry upload.
AI rationale
This is a real install-time remote payload staging and telemetry surface, but the source pins hashes, confines writes to its own package binary, and does not execute the staged payload during installation. Static inspection cannot establish the downloaded executable's behavior.
Evidence
package.jsoninstall.cjsbinaries.jsonbin/kry-cli.exe
Network endpoints2
s.koubei.comtnnm-alsc-saas-merchant-spider-fy21.cn-wulanchabu.log.aliyuncs.com/logstores/kry-cli/track?APIVersion=0.6.0
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The package runs install.cjs automatically through a postinstall hook.
- The hook downloads a platform-specific opaque native executable, verifies hashes, and replaces bin/kry-cli.exe.
- By default, the install hook sends hostname, derived user and session identifiers, and npm-install metadata to a remote logging endpoint.
Evidence against
- The downloaded compressed data and decompressed binary are checked against package-pinned SHA-256 values before writing.
- The installer writes only its own bin/kry-cli.exe and does not launch the downloaded binary during installation.
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
HighSemantic Analysis Limitedbin/sdk.mjs#virtual:string-array:round1
HighKnown Malware Source Similarityinstall.cjs
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.5.5.
See all versions of @keruyun/agent-cli for other recorded verdicts.
- Review the evidence and your use of @keruyun/agent-cli@1.5.5 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.