nansen-cli@1.44.3
AI-agent CLI for Nansen API analytics, DEX swaps, and cross-chain trading
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInspected source supports a warning for explicit forwarding of an existing service credential to an unrestricted custom HTTPS recipient. Prompted skill setup and user-command MCP configuration do not establish malicious install behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running nansen mcp verify with a custom --url and --send-api-key while a saved or environment API key exists.
Impact
The selected endpoint can receive and retain a usable Nansen credential.
Mechanism
The command resolves the existing key and sends it as a NANSEN-API-KEY header after the custom server passes an unauthenticated tools/list check.
AI rationale
Inspected source supports a warning for explicit forwarding of an existing service credential to an unrestricted custom HTTPS recipient. Prompted skill setup and user-command MCP configuration do not establish malicious install behavior.
Evidence
src/doctor.jssrc/commands/mcp.jssrc/mcp-verify.js
Network endpoints1
mcp.nansen.ai/ra/mcp
Decision evidence
public snapshotAI called this Suspicious at 97.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- MCP verification resolves an existing Nansen API key from configuration or NANSEN_API_KEY when no explicit key is supplied.
- The verify command accepts a custom URL and enables saved-key forwarding through --send-api-key.
- Custom HTTPS destinations are not restricted to Nansen; consent bypasses the saved-key withholding guard.
- After an unauthenticated reachability check, verification sends the key in a NANSEN-API-KEY header on an authenticated POST.
- Interactive global installation offers a prompted Nansen skill installation.
- Explicit MCP installation merges a Nansen server entry into the selected agent configuration.
Evidence against
- Saved-key forwarding requires an explicit flag; unsafe public HTTP destinations are rejected and redirects are refused.
- The install hook skips local and noninteractive installations; skill installation has an interactive prompt.
- MCP installation uses a fixed Nansen endpoint, preserves other server entries, and backs up existing configuration.
Behavioral surface
ChildProcess
Source & flagged code
8 flaggedpackage.jsonView file
•scripts.postinstall = node scripts/postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 4
High
Semantic Analysis Limited
A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgsrc/wallet.jsView file
Findings
4 High7 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSandbox Evasion Gated Capabilitysrc/doctor.js
HighSemantic Analysis Limitedpackage.json
HighPrevious Version Dangerous Deltasrc/cli.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumSecret Patternsrc/wallet.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumSecret Patternsrc/wallet.js
MediumSecret Patternsrc/wallet.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Low
Affected versions and remediation
This report applies to nansen-cli@1.44.3.
See all versions of nansen-cli for other recorded verdicts.
- Review the evidence and your use of nansen-cli@1.44.3 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.