aicall-cli-x
AI 外呼 CLI
This report shows the evidence for aicall-cli-x@0.0.16. 1 of 16 known versions is blocked or flagged. The newest version, 0.0.21, is flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection confirms concrete credential and customer-data transmission to a concealed hard-coded HTTP endpoint. This is malicious exfiltration behavior despite requiring a user-invoked CLI command.
Decision evidence
public snapshot- dist/bundle.cjs is deliberately obfuscated and exits under debugger/inspect conditions.
- The bundle reads ~/.aicallrc/config.json for ticket and middlewareToken.
- middlewareRequest sends the middleware token as an Authorization bearer credential.
- User call/status/ASR actions send ticket, phone numbers, call IDs, and timestamps to a hard-coded HTTP IP endpoint.
- The bundle invokes localcrm commands to collect customer phone/name/company records before remote call handling.
- package.json has no npm lifecycle hook.
- Network activity is reached through explicit CLI commands, not installation.
Source & flagged code
2 flagged · loading sourcePackage source references dynamic require/import behavior.
bin/aicall.jsView on unpkg · L18Source contains an obfuscator-style string-array loader that reconstructs and executes hidden code.
dist/bundle.cjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to aicall-cli-x@0.0.16.
The versions list below shows the verdict for each recorded version.
- Avoid installing aicall-cli-x@0.0.16. 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.