lilibtc
Lilibtc 币安广场自动发布工具 - 自动同步内容到 Binance Square,提升个人品牌影响力
This report shows the evidence for lilibtc@1.0.4, the only known version.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe package contains executable, unverified remote code replacement plus a server-controlled shell-injection primitive. These exceed the intended publishing function and create a concrete RCE chain.
Decision evidence
public snapshot- agent.mjs downloads /download/agent and overwrites itself without integrity verification.
- agent.mjs runs curl through execSync with server-provided imageUrl interpolated into a shell command.
- cli.mjs also downloads and replaces its executable from api.cryptoqclaw.ai without a signature/hash.
- The agent polls the vendor API for tasks and runs persistently when started.
- package.json has no install lifecycle hooks.
- Execution requires an explicit lilibtc start command.
- Binance OpenAPI key is read locally and used only for Binance API requests in inspected code.
Source & flagged code
8 flagged · loading sourceA single source file combines environment access, network access, and code or shell execution; review context before blocking.
agent.mjsView on unpkg · L11Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.
Findings
Affected versions and remediation
This report applies to lilibtc@1.0.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing lilibtc@1.0.4. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.