@aiyiran/myclaw@1.1.204
为 OpenClaw 教学环境设计的一站式命令行工具。
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThere is no install lifecycle hook, but explicit CLI flows establish persistent third-party workspace uploads and broad modification of a foreign AI-agent UI. The behavior is risky and insufficiently constrained, though static source does not establish automatic install-time malware.
Decision evidence
public snapshot- The server continuously uploads changed OpenClaw workspace files to a third-party CDN.
- The patch command injects several scripts into another package's control UI and weakens its CSP to allow arbitrary connections and frames.
- The persistent upload server is started by a CLI command and scans workspace directories.
- package.json has no preinstall, install, or postinstall hook.
- The risky actions require explicit CLI commands; package import alone does not run them.
- No self-dependency or automatic registry-install lifecycle chain is present.
Source & flagged code
20 flagged · loading sourcePackage source references dynamic require/import behavior.
delete_agents.jsView on unpkg · L19Findings
Affected versions and remediation
This report applies to @aiyiran/myclaw@1.1.204.
See all versions of @aiyiran/myclaw for other recorded verdicts.
- Review the evidence and your use of @aiyiran/myclaw@1.1.204 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.