registry / slashvibe-mcp / 0.8.21
slashvibe-mcp@0.8.21
Presence + messaging for terminal coding agents (Claude Code, Codex, Cursor) — the /vibe kernel
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and the flagged Unicode in protocol/handle.js is deliberately stripped during handle normalization. Credential use and agent configuration are consistent with the package’s sign-in and setup flows; no attack behavior was found.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Package install and import do not trigger the reviewed setup actions; setup and messaging actions are user-invoked.
Impact
No malicious impact identified.
Mechanism
The reviewed credential flow sends the sign-in token to the package’s own API. Setup configures the package for detected agents when launched.
AI rationale
The package has no install lifecycle hook, and the flagged Unicode in protocol/handle.js is deliberately stripped during handle normalization. Credential use and agent configuration are consistent with the package’s sign-in and setup flows; no attack behavior was found.
Network endpoints1
www.slashvibe.dev
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest declares no preinstall, install, or postinstall script.
- Setup is routed through the CLI’s setup command or the dedicated setup binary.
- The sign-in token is sent as a bearer credential to the package’s own slashvibe.dev API.
- The flagged invisible Unicode characters are removed during handle normalization.
- Git context uses argument-based execution with shell disabled.
Evidence against
- Setup writes MCP entries to detected coding-agent configuration files and performs browser OAuth when invoked.
- The package uses network access, credentials, and filesystem writes as part of its presence and messaging purpose.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggedtools/_work-context.jsView file
12L13: const { execFileSync } = require('child_process');
L14: const fs = require('fs');
High
Child Process
Package source references child process execution.
tools/_work-context.jsView on unpkg · L12tools/init.jsView file
11L12: const { exec, execSync } = require('child_process');
L13: const fs = require('fs');
...
L21:
L22: const API_BASE = 'https://www.slashvibe.dev';
L23:
...
L25: // "vibe email …" advertises a command their session does not have.
L26: const EXTRAS_ENABLED = ['1', 'true'].includes(String(process.env.VIBE_EXTRAS || '').toLowerCase());
L27:
High
Same File Env Network Execution
A single source file combines environment access, network access, and code or shell execution; review context before blocking.
tools/init.jsView on unpkg · L11protocol/handle.jsView file
Findings
3 Critical4 High3 Medium4 Low
CriticalTrojan Source Unicodeprotocol/handle.js
CriticalTrigger Reachable Dangerous Capabilityprotocol/handle.js
CriticalPrevious Version Dangerous Deltasetup.js
HighChild Processtools/_work-context.js
HighShell
HighSame File Env Network Executiontools/init.js
HighSemantic Analysis Limitedindex.js#virtual:string-array:round1
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to slashvibe-mcp@0.8.21.
See all versions of slashvibe-mcp for other recorded verdicts.
- Review the evidence and your use of slashvibe-mcp@0.8.21 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.