slashvibe-mcp@0.8.26
Presence + messaging for terminal coding agents (Claude Code, Codex, Cursor) — the /vibe kernel
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package has no install-time attack behavior, and the flagged Unicode is used to strip invisible handle characters. However, sign-in completion silently sends repository metadata to the service, which warrants a warning because the init tool does not disclose that collection.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Completing the vibe_init sign-in flow.
Impact
The service receives project-identifying context without the init tool disclosing that collection.
Mechanism
Reads the repository name and technology stack, then includes them in a POST to the package’s onboarding API.
AI rationale
The package has no install-time attack behavior, and the flagged Unicode is used to strip invisible handle characters. However, sign-in completion silently sends repository metadata to the service, which warrants a warning because the init tool does not disclose that collection.
Evidence
tools/init.js
Network endpoints1
www.slashvibe.dev/api/onboarding/personalized-welcome
Decision evidence
public snapshotAI called this Suspicious at 86.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The init flow automatically detects the current repository name and technology stack.
- It posts the handle, optional one-liner, repository name, and stack to the personalized-welcome endpoint on slashvibe.dev.
- The metadata post is triggered during sign-in completion; the tool description does not disclose automatic sharing of repository metadata.
Evidence against
- The package declares no install, preinstall, or postinstall lifecycle script.
- The bidi controls are used in a regex that removes invisible characters from handles.
- The data is sent to the package’s own onboarding endpoint, and this request does not send repository files or credentials.
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.26.
See all versions of slashvibe-mcp for other recorded verdicts.
- Review the evidence and your use of slashvibe-mcp@0.8.26 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.