registry / @tangle-network/sandbox-cli / 0.21.24
@tangle-network/sandbox-cli@0.21.24
CLI for Tangle Sandbox operations
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged credential flow requires an explicit command, strips Claude credentials from the child environment, and filters captured output for official OAuth authorization URLs before storing the token through the Sandbox API. The fixed Tailnet URL appears in solve sponsor metadata, but the reviewed source does not show it receiving credentials or being contacted automatically.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user invokes `tangle secret create --from-login claude`.
Impact
No unauthorized impact identified; the flow stores a credential at the user’s request.
Mechanism
The CLI starts Claude’s setup-token flow, filters captured output for official authorization URLs, and stores the token through the Sandbox secrets API.
AI rationale
The flagged credential flow requires an explicit command, strips Claude credentials from the child environment, and filters captured output for official OAuth authorization URLs before storing the token through the Sandbox API. The fixed Tailnet URL appears in solve sponsor metadata, but the reviewed source does not show it receiving credentials or being contacted automatically.
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a CLI entry point and lists build and test scripts, with no install lifecycle script.
- Claude credential enrollment requires the explicit `secret create --from-login claude` option.
- The enrollment flow launches `claude setup-token` with Claude credential variables removed from the child environment.
- Captured output is filtered for authorization URLs on Claude’s two official OAuth hosts.
- The resulting token is stored through the Sandbox secrets API, and the CLI says it stays out of terminal output.
Evidence against
- A fixed Tailnet host appears in solve sponsor metadata, but I found no evidence that it receives credentials or is contacted automatically.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsMinifiedPossibleObfuscationTelemetry
Source & flagged code
8 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 Critical6 High3 Medium6 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
HighSemantic Analysis Limiteddist/graph-viewer/record-part-Cx9GDQeo.js#virtual:string-array:round1
MediumNetwork
MediumEnvironment Vars
MediumRemote Tarball Dependencypackage.json
LowScripts Present
LowEval
LowFilesystem
Affected versions and remediation
This report applies to @tangle-network/sandbox-cli@0.21.24.
See all versions of @tangle-network/sandbox-cli for other recorded verdicts.
- Review the evidence and your use of @tangle-network/sandbox-cli@0.21.24 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.