registry / @tangle-network/sandbox-cli / 0.20.62
@tangle-network/sandbox-cli@0.20.62
CLI for Tangle Sandbox operations
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe CLI sends credentials to Tangle endpoints for requested API operations, and its solve credential flow restricts destinations to fixed Tangle hosts. The manifest has no install hooks, and the credential-related scanner leads do not establish an unrelated recipient or unauthorized default action.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Network requests occur when a user invokes CLI commands that need the Tangle API.
Impact
No unauthorized collection, credential redirection, or unrelated execution was established.
Mechanism
The CLI uses configured Tangle endpoints, defaults sandbox requests to sandbox.tangle.tools, and sends API credentials as bearer tokens to the selected service.
AI rationale
The CLI sends credentials to Tangle endpoints for requested API operations, and its solve credential flow restricts destinations to fixed Tangle hosts. The manifest has no install hooks, and the credential-related scanner leads do not establish an unrelated recipient or unauthorized default action.
Network endpoints3
sandbox.tangle.toolsid.tangle.toolssolve.tangle.tools
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a CLI and library entrypoint and declares no install lifecycle hooks.
- The CLI defaults sandbox requests to sandbox.tangle.tools; API keys are sent as bearer credentials to the configured sandbox API base URL.
- Platform and solve endpoints are on tangle.tools, and solve credentials are restricted to those fixed endpoints.
- The bundled skill documentation tells users not to print or log credentials.
Evidence against
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
6 flaggeddist/index.mjsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @tangle-network/sandbox-cli@0.20.50
matchedIdentity = npm:[redacted]:0.20.50
similarity = 0.500
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/index.mjsView on unpkg1import{createRequire as e}from"node:module";import"dotenv/config";import{ALL_BACKEND_TYPES as t,AuthError as n,GPU_LEASE_PROVIDER_NAMES as r,NetworkError as i,NotFoundError as a,Pu...
L2: `);return`Hub connection reference is ambiguous: "${e}" matches ${t.length} connections. Use a connection id or provider:account instead.
High
1import{createRequire as e}from"node:module";import"dotenv/config";import{ALL_BACKEND_TYPES as t,AuthError as n,GPU_LEASE_PROVIDER_NAMES as r,NetworkError as i,NotFoundError as a,Pu...
L2: `);return`Hub connection reference is ambiguous: "${e}" matches ${t.length} connections. Use a connection id or provider:account instead.
Findings
1 Critical5 High2 Medium4 Low
CriticalPrevious Version Dangerous Deltadist/index.mjs
HighChild Processdist/index.mjs
HighSame File Env Network Executiondist/index.mjs
HighCredential Redirect Persistencedist/index.mjs
HighCommand Output Exfiltrationdist/index.mjs
HighTrigger Reachable Command Output Exfiltrationdist/index.mjs
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @tangle-network/sandbox-cli@0.20.62.
See all versions of @tangle-network/sandbox-cli for other recorded verdicts.
- Review the evidence and your use of @tangle-network/sandbox-cli@0.20.62 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.