beast-agent@2.63.2
Ultra-fast local agent shell for Windows.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe code contains risky lifecycle repair, persistence, foreign-token migration, and downloaded-code execution, but static inspection did not establish direct malicious exfiltration or the policy's complete malicious lifecycle chain.
Decision evidence
public snapshot- Its automatic postinstall can delete Electron runtime files and rerun Electron's installer, including through a mirror.
- On first global-package launch, it registers itself to start with Windows and creates shortcuts.
- It searches OpenCode authentication files, reads a key, and saves that key into Beast's own environment file.
- Its app installer downloads packages or GitHub repositories and immediately loads their JavaScript with require.
- No runtime dependency on beast-agent itself was found.
- The postinstall targets the package's Electron dependency rather than an AI-agent control surface.
- No source path inspected sends harvested keys to an unrelated endpoint.
Source & flagged code
27 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to beast-agent@2.63.2.
See all versions of beast-agent for other recorded verdicts.
- Review the evidence and your use of beast-agent@2.63.2 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.