nansen-cli@2.1.0
AI-agent CLI for Nansen API analytics, DEX swaps, and cross-chain trading
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource inspection found a prompted postinstall onboarding flow and user-invoked product operations, with no verified attack behavior. Static scanner signals around lifecycle execution and credentials reflect these inspected features rather than a concrete attack.
Decision evidence
public snapshot- The install hook invokes an onboarding script that asks before installing the Nansen skill; it declines by default.
- The MCP configuration location depends on an explicitly selected client, and the package entrypoint dispatches caller-supplied CLI arguments.
- Flagged wallet-password references retrieve local environment, keychain, or credentials-file values for wallet and trading operations; the inspected excerpts show no unrelated recipient.
- The inspected simulation request rejects redirects when credentials are present, limiting credential forwarding to the selected RPC endpoint.
- The inspected wallet, trading, order, and transfer code concerns user-invoked product operations; no concrete attack behavior was identified.
- The package has a postinstall hook, and its onboarding can run an npx command after the user accepts the prompt.
- Wallet and trading code handles locally stored passwords and sends authenticated requests to service or RPC endpoints.
Source & flagged code
7 flaggedPackage 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 nansen-cli@2.1.0.
See all versions of nansen-cli for other recorded verdicts.
- Review the evidence and your use of nansen-cli@2.1.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.