@vibelet/cli
Cross-platform CLI for installing and running the Vibelet daemon
This report shows the evidence for @vibelet/cli@1.2.154. 1 of 23 known versions is blocked or flagged. The newest version, 1.2.220, is flagged. See all versions.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-10720 confirms this npm version as malicious.
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
The package is not proven malicious, but its obfuscated daemon, persistence, default remote tunnel, and remote coding-agent control create substantial user-host risk. Flag as a warning rather than block because activation is user-invoked and no concrete malicious chain was found.
Independent scan evidence
public snapshot- `dist/index.cjs` is heavily obfuscated, limiting auditability of the daemon.
- `dist/vibelet.mjs` starts persistent launchd/systemd/detached daemon backends after a user invokes the CLI.
- `dist/vibelet.mjs` enables Cloudflare Tunnel remote access by default for start-like commands.
- `dist/vibelet.mjs` explicitly launches Claude/Codex integrations and creates temporary Claude hook settings.
- `package.json` contains no preinstall, install, postinstall, or prepare lifecycle hook.
- The executable is only the user-invoked `vibelet` bin entrypoint.
- CLI persistence and configuration target `~/.vibelet`; no foreign AI-agent configuration write was confirmed.
- No hardcoded credential-exfiltration endpoint or secret-harvesting path was confirmed in inspected sources.
Source & flagged code
2 flagged · loading sourcePackage source references dynamic require/import behavior.
dist/web/assets/codeql-DsOJ9woJ.jsView on unpkg · L1Source contains bidi control or invisible Unicode characters associated with Trojan Source attacks.
dist/web/assets/mermaid-O7DHMXV3-BA2glr4S.jsView on unpkg · L189Findings
Affected versions and remediation
This report applies to @vibelet/cli@1.2.154.
The versions list below shows the verdict for each recorded version.
- Avoid installing @vibelet/cli@1.2.154. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.