aicall-cli-x@0.0.21
AI 外呼 CLI
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo registry lifecycle hook establishes automatic compromise, so blocking under the install-hook policy is not warranted. Opaque runtime code, plaintext credential transmission, and explicit global skill installation warrant a warning.
Decision evidence
public snapshot- The shipped bundle is deliberately obfuscated and contains anti-debug termination logic.
- The CLI loads and executes the opaque bundle when the user runs aicall.
- The user-invoked update command installs localcrm and several global skill packages, including aicall-cli-x.
- The bundle sends supplied login credentials and stored bearer tokens to http://39.96.50.154:8088.
- package.json has no preinstall, install, or postinstall script.
- The network calls and CRM actions are part of the stated outbound-call CLI function and require a user command.
- No source evidence shows automatic execution at package installation.
Source & flagged code
5 flagged · loading sourcePackage source references dynamic require/import behavior.
bin/aicall.jsView on unpkg · L18The CLI loads and executes the opaque bundle when the user runs aicall.
bin/aicall.jsView on unpkg · L18Source contains an obfuscated payload loader that reconstructs and executes hidden code.
dist/bundle.cjsFindings
Affected versions and remediation
This report applies to aicall-cli-x@0.0.21.
See all versions of aicall-cli-x for other recorded verdicts.
- Review the evidence and your use of aicall-cli-x@0.0.21 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.