alvin-bot@5.132.1
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 1mo ago · by lpm-firewall-aiThe package contains deliberate obfuscation and an explicit detection-bypass plus permission-bypass chain in a runtime bridge. Although no installation lifecycle attack was found, the resulting AI-agent capability is unsafe and insufficiently transparent.
Decision evidence
public snapshot- The published runtime is deliberately obfuscated; the manifest exposes a debug build flag to disable obfuscation.
- The Claude bridge labels its transformation as a detection bypass and rewrites outbound identifiers before invoking Claude.
- It invokes Claude with permission checks explicitly disabled.
- The CLI can install a login persistence agent and an independent watcher that restarts the bot.
- The manifest has no preinstall, install, or postinstall hook.
- The persistence path is exposed through an explicit launchd command, not package installation.
- No self-dependency or confirmed secret-exfiltration endpoint was found.
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.132.1.
See all versions of alvin-bot for other recorded verdicts.
- Review the evidence and your use of alvin-bot@5.132.1 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.