@yhong91/vibetime
vibetime CLI — install AI-agent hooks (Claude Code, Codex, OpenCode, Pi, Cursor) and report activity to vibetime.
This report shows the evidence for @yhong91/vibetime@0.1.76. 7 of 48 known versions are blocked or flagged. The newest version, 0.1.82, is flagged. See all versions.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiSource establishes an explicit-command persistence chain from broad AI-agent hooks to authenticated uploads at a hard-coded HTTP IP endpoint. The lack of an install lifecycle hook reduces automatic-install risk but does not remove the concrete exfiltration capability.
Decision evidence
public snapshot- The default service is a hard-coded HTTP endpoint at an unrelated IP address.
- The explicit install command adds hooks for prompt, permission, and tool events to the user's Codex configuration.
- Hook activation starts a background import that collects local agent history and uploads rollups.
- Uploads include the saved bearer token and machine identity headers.
- The package has no npm install lifecycle hook; its integration is activated by its CLI install command.
- The manifest exposes only a CLI and has no preinstall, install, or postinstall script.
- The hook installation path is an explicit user command rather than automatic package-install execution.
Source & flagged code
6 flagged · loading sourceManifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection.
bin/vibetime.mjsView on unpkgPackage source invokes a package manager install command at runtime.
bin/vibetime.mjsView on unpkg · L16745Source file is highly similar to a previously finalized malicious package; route for source-aware review.
bin/vibetime.mjsView on unpkgSource fingerprint signature matches a known malicious package signature; route for source-aware review.
bin/vibetime.mjsView on unpkgFindings
Affected versions and remediation
This report applies to @yhong91/vibetime@0.1.76.
The versions list below shows the verdict for each recorded version.
- Avoid installing @yhong91/vibetime@0.1.76. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.