@vibiz/cli@0.2.4
The Vibiz Stack CLI and MCP server: website, database, sign-in, email and AI for a new business, from your terminal or your AI agent.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe login flow sends the machine hostname to Vibiz's own service without an evident disclosure in the reviewed path. This is identifying runtime telemetry, so downgrade to a warning; the scanner's credential-exfiltration claim was not supported by the inspected source.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user runs `vibiz login` or `vibiz signup` without supplying `--key`.
Impact
The service receives the machine hostname during login. The reviewed source did not show credential forwarding to an unrelated host.
Mechanism
The CLI posts the machine hostname, OS and CLI version to the configured API's `/v1/cli/login` endpoint, which defaults to Vibiz's own service.
AI rationale
The login flow sends the machine hostname to Vibiz's own service without an evident disclosure in the reviewed path. This is identifying runtime telemetry, so downgrade to a warning; the scanner's credential-exfiltration claim was not supported by the inspected source.
Evidence
dist/vibiz.jspackage.jsonCLI config file (`config.json` under the CLI config directory)CLI pending login file (`pending-login.json` under the CLI config directory)CLI update cache (`update-check.json` under the CLI config directory)
Network endpoints2
app.vibiz.app/v1/cli/loginregistry.npmjs.org/@vibiz/cli/latest
Decision evidence
public snapshotAI called this Suspicious at 85.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The `vibiz` binary runs the CLI entry point; no lifecycle scripts are declared.
- The explicit `login`/`signup` command starts browser login using the configured API URL, defaulting to the Vibiz service.
- Browser login sends the machine hostname, OS and CLI version to `/v1/cli/login`; the hostname is identifying telemetry sent to the package's own service.
- At normal CLI startup, the update check fetches only the package's latest version from the npm registry.
Evidence against
- The manifest declares no install lifecycle scripts.
- No source evidence showed credentials being sent to an unrelated host or a hidden account action.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsPossibleObfuscationUrlStrings
NoLicense
Source & flagged code
6 flaggeddist/vibiz.jsView file
15// packages/cli/src/main.ts
L16: import { spawn } from "node:child_process";
L17: import { chmod, mkdir as mkdir2, readFile as readFile3, writeFile as writeFile3 } from "node:fs/promises";
...
L27: var runtimeEnv = () => globalThis.process?.env ?? {};
L28: var DEFAULT_URL = "https://app.vibiz.app";
L29: var VibizAppError = class extends Error {
...
L166: let diff = 0;
L167: for (let i = 0; i < a.length; i++) diff |= a.charCodeAt(i) ^ b.charCodeAt(i);
L168: return diff === 0;
...
L205: var query = (q) => {
L206: const p = new URLSearchParams();
L207: for (const [k, v] of Object.entries(q)) if (v !== void 0 && v !== "") p.set(k, String(v));
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
dist/vibiz.jsView on unpkg · L1515Trigger-reachable chain: manifest.bin -> dist/vibiz.js
L15: // packages/cli/src/main.ts
L16: import { spawn } from "node:child_process";
L17: import { chmod, mkdir as mkdir2, readFile as readFile3, writeFile as writeFile3 } from "node:fs/promises";
...
L27: var runtimeEnv = () => globalThis.process?.env ?? {};
L28: var DEFAULT_URL = "https://app.vibiz.app";
L29: var VibizAppError = class extends Error {
...
L166: let diff = 0;
L167: for (let i = 0; i < a.length; i++) diff |= a.charCodeAt(i) ^ b.charCodeAt(i);
L168: return diff === 0;
...
L205: var query = (q) => {
L206: const p = new URLSearchParams();
L207: for (const [k, v] of Object.entries(q)) if (v !== void 0 && v !== "") p.set(k, String(v));
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
Findings
3 Critical3 High3 Medium4 Low
CriticalCredential Exfiltrationdist/vibiz.js
CriticalTrigger Reachable Dangerous Capabilitydist/vibiz.js
CriticalPrevious Version Dangerous Deltadist/vibiz.js
HighCredential Redirect Persistencedist/vibiz.js
HighTrigger Reachable Credential Exfiltrationdist/vibiz.js
HighSemantic Analysis Limiteddist/vibiz.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @vibiz/cli@0.2.4.
See all versions of @vibiz/cli for other recorded verdicts.
- Review the evidence and your use of @vibiz/cli@0.2.4 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.