registry / @superblocksteam/cli / 2.0.171
@superblocksteam/cli@2.0.171
Official Superblocks CLI
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe inspected credential path remains tied to the Superblocks service, and the preinstall hook's removal action requires confirmation. Agent-related configuration is part of an explicit setup command; the host metadata signal comes from a telemetry-gated Datadog tracer path, with no concrete attack behavior established.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
No malicious trigger identified; the preinstall hook runs during global installation, and MCP setup runs when explicitly invoked.
Impact
No credential diversion or unconsented install-time agent configuration change was established.
Mechanism
The hook asks before attempting removal of conflicting Superblocks CLI installs. Login and gateway configuration use the Superblocks server URL from configuration or user selection.
AI rationale
The inspected credential path remains tied to the Superblocks service, and the preinstall hook's removal action requires confirmation. Agent-related configuration is part of an explicit setup command; the host metadata signal comes from a telemetry-gated Datadog tracer path, with no concrete attack behavior established.
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 runs a preinstall hook; its handler skips ordinary local installs and asks before attempting to remove conflicting Superblocks CLI installations.
- Login uses a supplied or saved Superblocks API key with the Superblocks service, and the gateway session uses its configured server URL; the inspected path shows no unrelated credential recipient.
- MCP configuration changes come from the explicit setup command, target a selected client's configuration, and add the Superblocks server entry. The packaging verifier also rejects Claude plugin artifacts.
- A bundled Datadog tracer builds host metadata for a telemetry path guarded by its instrumentation telemetry setting; this source does not establish an unrelated credential transfer.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
Source & flagged code
16 flaggedpackage.jsonView file
•scripts.preinstall = node scripts/customer/preinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.preinstall = node scripts/customer/preinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/chunk-WWL44AEF.jsView file
25exports.execAsync = void 0;
L26: var child_process = __require("child_process");
L27: var util = __require("util");
High
Child Process
Package source references child process execution.
dist/chunk-WWL44AEF.jsView on unpkg · L25Findings
1 Critical10 High7 Medium5 Low
CriticalPrevious Version Dangerous Deltascripts/verify-ripgrep-package.mjs
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/chunk-WWL44AEF.js
HighShelldist/index.js
HighHost Fingerprint Exfiltrationdist/chunk-LCQX4UHT.js
HighCredential Redirect Persistencedist/index.js
HighCommand Output Exfiltrationdist/chunk-LCQX4UHT.js
HighSandbox Evasion Gated Capabilityscripts/verify-ripgrep-package.mjs
HighCross File Remote Execution Contextdist/chunk-LCQX4UHT.js
HighTrigger Reachable External Post Callbackdist/chunk-LCQX4UHT.js
HighSemantic Analysis Limiteddist/chunk-LCQX4UHT.js
Affected versions and remediation
This report applies to @superblocksteam/cli@2.0.171.
See all versions of @superblocksteam/cli for other recorded verdicts.
- Review the evidence and your use of @superblocksteam/cli@2.0.171 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.