@zan_team/zan-router
ZAN AI Router CLI
This report shows the evidence for @zan_team/zan-router@1.0.0. 1 of 6 known versions is blocked or flagged. The newest version, 1.1.2, is allowed. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is concrete credential exfiltration from foreign agent configuration to a package-controlled endpoint before consent, not merely an explicit configuration helper.
Decision evidence
public snapshot- Setup reads credentials from existing agent configs before the user confirms changes.
- Claude extraction accepts any existing ANTHROPIC_AUTH_TOKEN; Hermes also falls back to OPENAI_API_KEY.
- The extracted key is sent as an Authorization/x-api-key header to the ZAN API.
- The default receiver is https://ai.zan.top, and confirmation occurs only after verification.
- package.json has no npm lifecycle hooks.
- Network requests are confined to the advertised ZAN endpoint and setup is user-invoked.
Source & flagged code
4 flagged · loading sourceSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/cli.jsView on unpkg · L99Manifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection.
Findings
Affected versions and remediation
This report applies to @zan_team/zan-router@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @zan_team/zan-router@1.0.0. 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.