@zuplo/cli@7.5.6
<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 install or persistence chain was found, but default machine-linked telemetry and bundled environment-aware runtime code create a real privacy-sensitive surface. The non-text archive and large minified bundle prevent a fully grounded clean verdict.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Running the zup CLI or a Zuplo runtime deployment.
Impact
Pseudonymous device data and selected command context may leave the machine; runtime logging may transmit configured deployment data.
Mechanism
Default telemetry and configured runtime log delivery.
AI rationale
No concrete malicious install or persistence chain was found, but default machine-linked telemetry and bundled environment-aware runtime code create a real privacy-sensitive surface. The non-text archive and large minified bundle prevent a fully grounded clean verdict.
Evidence
dist/common/analytics/lib.jsdist/common/machine-id/lib.jsnode_modules/@zuplo/runtime/out/esm/chunk-CT4N5TO4.jsnode_modules/@zuplo/core/zeno.js
Network endpoints1
app.posthog.com
Decision evidence
public snapshotAI called this Suspicious at 76.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The CLI sends analytics to PostHog by default, including a persistent machine-derived identifier and selected command context.
- The bundled runtime collects its complete Deno environment and can send authenticated runtime logs to a configured remote endpoint.
- The package includes large minified bundled code and a non-text test archive, preventing a fully source-grounded clean determination.
Evidence against
- package.json defines no preinstall, install, or postinstall lifecycle hook.
- The exposed executable is a normal CLI entry point, not import-time execution.
- The inspected migration and lint handlers are invoked commands; no covert persistence or destructive install action was found.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsTelemetryUrlStrings
Source & flagged code
21 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
3 Critical11 High8 Medium7 Low
CriticalHardcoded Runtime Data Exfiltrationnode_modules/@zuplo/runtime/out/esm/chunk-CT4N5TO4.js
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-CT4N5TO4.js
Affected versions and remediation
This report applies to @zuplo/cli@7.5.6.
See all versions of @zuplo/cli for other recorded verdicts.
- Review the evidence and your use of @zuplo/cli@7.5.6 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.