@vibeapi/api-helper@0.0.162
CLI tool for managing AI coding assistants (Claude Code, Codex, OpenClaw, Hermes, AtomCode, Grok Build) with one unified config
AI Security Review
scanned 16h ago · by lpm-firewall-aiThe package sends runtime command diagnostics to its own gateway by default, with only an environment-variable opt-out and no disclosure found in the inspected README. This meets the suspicious telemetry criterion, but the reviewed flow does not show an unrelated collector or credential exfiltration.
Static reason
One or more suspicious static signals were detected.
Trigger
Running a CLI command that reaches normal command execution.
Impact
The publisher receives command and error diagnostics without an apparent disclosure in the inspected README; no credential exfiltration was identified.
Mechanism
The CLI records command diagnostics and runtime metadata, then posts telemetry to the configured gateway; TELEMETRY=0, false, or off disables collection.
AI rationale
The package sends runtime command diagnostics to its own gateway by default, with only an environment-variable opt-out and no disclosure found in the inspected README. This meets the suspicious telemetry criterion, but the reviewed flow does not show an unrelated collector or credential exfiltration.
Evidence
dist/lib/command.jsdist/lib/telemetry.jsdist/brand.json
Network endpoints6
www.vibeapi.cnwww.vibeapi.sihk.vibeapi.cnus13-www.vibeapi.cncf.vibeapi.cntoken.nfeyre.top
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- Runtime telemetry is enabled by default; it is disabled only when TELEMETRY is set to 0, false, or off.
- Telemetry events include the command, step, status, duration, error text, and event details, alongside install and runtime metadata.
- The CLI flushes telemetry after a command runs.
- Telemetry posts to the configured VibeAPI gateway, whose default host is www.vibeapi.cn.
Evidence against
- The manifest declares no install, preinstall, or postinstall lifecycle hook.
- The reviewed telemetry sends runtime and command diagnostics to the package’s own gateway; no unrelated collector or automatic credential theft was identified.
Behavioral surface
ChildProcessEnvironmentVarsNetworkShell
HighEntropyStringsMinifiedUrlStrings
NoLicense
Source & flagged code
6 flaggeddist/lib/tools/chatgpt-desktop.jsView file
1import{spawnSync as t}from"child_process";import{logger as n}from"../../utils/logger.js";import{brand as e}from"../brand.js";import{powerShellEnv as r}from"../powershell-env.js";im...
High
Child Process
Package source references child process execution.
dist/lib/tools/chatgpt-desktop.jsView on unpkg · L1dist/lib/tools/tool-installs.jsView file
1import{spawnSync as t}from"child_process";import{existsSync as n,realpathSync as r,statSync as e}from"fs";import{delimiter as o,dirname as s,isAbsolute as i,join as a}from"path";im...
High
1import{spawnSync as t}from"child_process";import{existsSync as n,realpathSync as r,statSync as e}from"fs";import{delimiter as o,dirname as s,isAbsolute as i,join as a}from"path";im...
Findings
5 High4 Medium4 Low
HighChild Processdist/lib/tools/chatgpt-desktop.js
HighShelldist/lib/tools/tool-installs.js
HighSame File Env Network Executiondist/lib/tools/claude-desktop-cli.js
HighTrigger Reachable Persistencedist/lib/env-cleanup.js
HighRuntime Package Installdist/lib/tools/tool-installs.js
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencedist/lib/persistent-env.js
MediumStructural Risk Force Deep Review
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @vibeapi/api-helper@0.0.162.
See all versions of @vibeapi/api-helper for other recorded verdicts.
- Review the evidence and your use of @vibeapi/api-helper@0.0.162 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.