@zuplo/cli@7.7.9
<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-aiThe package has no automatic lifecycle hook or demonstrated malicious install chain. Its user-invoked telemetry and remote template writes are concrete capabilities with residual privacy and supply-chain risk.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Running a telemetry-enabled CLI command or the dev-portal migration command.
Impact
Usage metadata may leave the machine, and a migration can write downloaded template-derived project files.
Mechanism
Machine-linked analytics and remote template retrieval.
AI rationale
The package has no automatic lifecycle hook or demonstrated malicious install chain. Its user-invoked telemetry and remote template writes are concrete capabilities with residual privacy and supply-chain risk.
Evidence
dist/common/analytics/lib.jsdist/common/machine-id/lib.jsdist/source/migrate/dev-portal/handler.jsnode_modules/@zuplo/core/zeno.jsdocs/package.jsondocs/tsconfig.json
Network endpoints2
app.posthog.comcdn.jsdelivr.net
Decision evidence
public snapshotAI called this Suspicious at 82.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- CLI telemetry derives a stable hashed machine identifier and sends events to PostHog unless the user sets ZUPLO_DO_NOT_TRACK.
- The dev-portal migration command downloads templates from jsDelivr and writes generated project files.
- Bundled runtime code reads process and dotenv environment values when its runtime is launched.
Evidence against
- package.json has no preinstall, install, postinstall, or prepare lifecycle hook.
- The observed network and file operations are tied to invoked CLI commands rather than package installation.
- No source evidence established secret exfiltration, stealth persistence, or destructive automatic behavior.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsTelemetryUrlStrings
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 · L1650export: "legacyDevPortalHandler",
L651: module: "$import(@zuplo/runtime)",
L652: options: {
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/source/migrate/dev-portal/handler.jsView on unpkg · L650dist/lint/handler.jsView file
1import path from "node:path";
L2: import { execa } from "execa";
L3: import { shutdownAnalytics } from "../common/analytics/lib.js";
High
Findings
2 Critical10 High9 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
HighCommand Output Exfiltrationnode_modules/@zuplo/core/customer.cli.minified.js
HighCloud Metadata Accessnode_modules/@zuplo/runtime/out/esm/chunk-KNAYKBEE.js
HighCopied Package Dependency Bridgedist/common/analytics/lib.js
HighCross File Remote Execution Contextnode_modules/@zuplo/core/customer.cli.minified.js
High
Affected versions and remediation
This report applies to @zuplo/cli@7.7.9.
See all versions of @zuplo/cli for other recorded verdicts.
- Review the evidence and your use of @zuplo/cli@7.7.9 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.