beast-agent@2.16.0
Ultra-fast local agent shell for Windows.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has concrete, high-risk remote execution paths, including one in postinstall, but the inspected source does not meet the policy threshold for a malicious publish block. It should be warned until its installers use pinned, verified artifacts and avoid shell-piped remote scripts.
Decision evidence
public snapshot- The npm postinstall hook automatically runs the Electron repair script.
- The repair script deletes Electron runtime files and runs Electron's installer, retrying through a third-party mirror.
- The application also contains a user-invoked installer that pipes a remote CUA driver script directly into a shell.
- The manifest has no runtime dependency on beast-agent, so there is no nested self-install lifecycle chain.
- The remote CUA installer is exposed through an explicit application install action rather than the npm lifecycle hook.
- The source includes permission gates for agent command and file-writing tools.
Source & flagged code
19 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.16.0.
See all versions of beast-agent for other recorded verdicts.
- Review the evidence and your use of beast-agent@2.16.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.