@zuplo/cli@7.6.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 source supports a warning for default telemetry and remote content incorporated into project files. It does not support a malicious-install-hook or credential-theft conclusion.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs a CLI command that captures analytics or invokes the dev-portal migration.
Impact
Tracking metadata leaves the host; a compromised remote template source could affect generated project files.
Mechanism
Default telemetry collection and remote template retrieval.
AI rationale
The source supports a warning for default telemetry and remote content incorporated into project files. It does not support a malicious-install-hook or credential-theft conclusion.
Evidence
dist/common/analytics/lib.jsdist/common/machine-id/lib.jsdist/source/migrate/dev-portal/handler.jsdist/common/constants.jsdocs/package.jsondocs/tsconfig.json
Network endpoints2
app.posthog.comcdn.jsdelivr.net
Decision evidence
public snapshotAI called this Suspicious at 82.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- CLI telemetry is enabled unless the user sets the opt-out environment variable, and initializes a PostHog client.
- Telemetry uses a stable hash of the host machine identifier and can include supplied account, project, user, and CI values.
- The explicit dev-portal migration downloads template data from jsDelivr and writes it into the selected project.
Evidence against
- package.json defines a bin entry but no preinstall, install, or postinstall lifecycle hook.
- The observed network and file changes occur in user-invoked CLI features, not on package installation.
- No source evidence established secret harvesting, stealth persistence, destructive behavior, or runtime self-dependency.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
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 · 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
3 Critical10 High9 Medium7 Low
CriticalHardcoded Runtime Data Exfiltrationnode_modules/@zuplo/runtime/out/esm/chunk-Z3IKCP3N.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
HighCommand Output Exfiltrationnode_modules/@zuplo/core/customer.cli.minified.js
HighCloud Metadata Accessnode_modules/@zuplo/runtime/out/esm/chunk-Z3IKCP3N.js
HighCopied Package Dependency Bridgedist/common/analytics/lib.js
High
Affected versions and remediation
This report applies to @zuplo/cli@7.6.9.
See all versions of @zuplo/cli for other recorded verdicts.
- Review the evidence and your use of @zuplo/cli@7.6.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.