registry / @zuplo/cli / 7.7.16
@zuplo/cli@7.7.16
<p align="center"> <a href="https://zuplo.com"> <img src="https://portal.zuplo.com/zuplo.svg" height="96"> <h3 align="center">Zuplo</h3> </a> </p> <p align="center">Zuplo's API Gateway helps small and large teams get APIs to production that ar
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo concrete malicious behavior or automatic install-time execution was found. Incomplete coverage of a binary fixture and sensitive environment-handling code warrants a warning rather than a clean verdict.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs the zup CLI or a runtime feature that loads project environment configuration.
Impact
Potential exposure cannot be ruled out because a bundled binary fixture and minified code prevent complete static coverage.
Mechanism
User-invoked project tooling with environment access and bundled native/minified components.
AI rationale
No concrete malicious behavior or automatic install-time execution was found. Incomplete coverage of a binary fixture and sensitive environment-handling code warrants a warning rather than a clean verdict.
Decision evidence
public snapshotAI called this Suspicious at 68.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The bundled runtime enumerates all Deno environment variables and reads project environment files, a sensitive capability.
- The package includes large minified bundled code that limits direct review.
- A non-UTF-8 ZIP fixture remains uninspectable as JSON source text, so coverage is incomplete.
- The CLI can modify project files and invoke git when the user explicitly runs a migration.
- The linter launches a resolved executable only when the user invokes the lint command.
- The manifest exposes an explicit command-line binary.
Evidence against
- The manifest has no preinstall, install, postinstall, or prepare script.
- The entrypoint only imports the CLI after the user runs the zup command.
- No concrete credential-exfiltration endpoint or automatic execution path was established in the inspected source.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
Source & flagged code
20 flaggeddist/source/migrate/dev-portal/handler.jsView file
1import { exec } from "node:child_process";
L2: import { mkdir, readFile, rename, stat, unlink, writeFile, } from "node:fs/promises";
High
Child Process
Package source references child process execution.
dist/source/migrate/dev-portal/handler.jsView on unpkg · L1dist/lint/handler.jsView file
1import path from "node:path";
L2: import { execa } from "execa";
L3: import { shutdownAnalytics } from "../common/analytics/lib.js";
High
node_modules/pino/benchmarks/utils/wrap-log-level.jsView file
Findings
2 Critical11 High8 Medium7 Low
CriticalCredential Exfiltrationnode_modules/@zuplo/core/zeno.js
CriticalTrojan Source Unicodenode_modules/@zuplo/editor/dist/client/static/js/codemirror-6ITIKbGP.js
HighChild Processdist/source/migrate/dev-portal/handler.js
HighShelldist/lint/handler.js
HighSame File Env Network Executionnode_modules/@zuplo/core/customer.cli.minified.js
HighCredential Redirect Persistencenode_modules/@zuplo/core/customer.cli.minified.js
HighCommand Output Exfiltrationnode_modules/@zuplo/core/customer.cli.minified.js
HighCloud Metadata Accessnode_modules/@zuplo/runtime/out/esm/chunk-SIIXGJ76.js
HighCopied Package Dependency Bridgedist/common/analytics/lib.js
High
Affected versions and remediation
This report applies to @zuplo/cli@7.7.16.
See all versions of @zuplo/cli for other recorded verdicts.
- Review the evidence and your use of @zuplo/cli@7.7.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.