alvin-bot@5.127.0
Self-hosted autonomous AI agent on Telegram, Slack, Discord, WhatsApp, Signal, terminal & web. Claude Agent SDK + multi-provider engine with auto-failover, detached sub-agents, zero-config memory. Local-first, telemetry-free.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package does not run automatically on npm installation, so there is no install-hook attack. However, its runtime contains a concrete shell-injection path and deliberately bypasses agent permission checks, creating a serious unresolved security risk.
Decision evidence
public snapshot- The email plugin passes agent-controlled command arguments into shell-based execSync without validation.
- The Claude bridge always launches Claude with permission checks disabled.
- Published runtime files are deliberately obfuscated, which prevents straightforward auditing of substantial runtime behavior.
- package.json has only a prepublishOnly hook; installation does not automatically run package code.
- The risky features are reached through the bot, plugin, or bridge runtime rather than an npm install hook.
- No source evidence showed credential harvesting or transmission to an attacker-controlled endpoint.
Source & flagged code
18 flagged · loading sourcePackage source references child process execution.
claude-bridge/src/claude.jsView on unpkg · L2Source file is highly similar to a previously finalized malicious package; route for source-aware review.
claude-bridge/src/claude.jsView on unpkgPackage source references dynamic require/import behavior.
claude-bridge/src/claude.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to alvin-bot@5.127.0.
See all versions of alvin-bot for other recorded verdicts.
- Review the evidence and your use of alvin-bot@5.127.0 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.