@superblocksteam/cli@2.0.173
Official Superblocks CLI
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe hook has a real installation-time removal capability, and its confirmation treats an empty answer as consent, so a warning is warranted. The inspected credential flows target the configured service origin or Vercel’s OIDC endpoint; no unrelated credential recipient was established.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A global package install that detects conflicting CLI installations, or an explicitly enabled cleanup-mode run.
Impact
A blank response can authorize removal of an existing CLI installation, potentially including a privileged removal command.
Mechanism
The hook prints removal commands, then treats a blank confirmation as approval and executes the commands.
AI rationale
The hook has a real installation-time removal capability, and its confirmation treats an empty answer as consent, so a warning is warranted. The inspected credential flows target the configured service origin or Vercel’s OIDC endpoint; no unrelated credential recipient was established.
Evidence
package.jsonscripts/customer/preinstall.js
Decision evidence
public snapshotAI called this Suspicious at 82.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- package.json runs scripts/customer/preinstall.js as a preinstall hook.
- The hook can execute removal commands against detected prior CLI installations; one Unix Oclif path uses sudo, and an empty confirmation answer counts as approval.
- Conflict detection runs for global installs or cleanup mode; removal is requested through a confirmation prompt.
- The inspected credential flows use the configured service origin for API requests or send a Vercel token to the Vercel OIDC endpoint; the listed callers resolve credentials for their configured origin.
Evidence against
- The hook displays the proposed removal commands and requests confirmation before executing them.
- The credential resolver matches saved credentials to the requested service origin, and API requests reject a different origin.
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-SGKUWPV7.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-SGKUWPV7.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-SGKUWPV7.js
HighShelldist/index.js
HighHost Fingerprint Exfiltrationdist/chunk-RWMD7E47.js
HighCredential Redirect Persistencedist/index.js
HighCommand Output Exfiltrationdist/chunk-RWMD7E47.js
HighSandbox Evasion Gated Capabilityscripts/verify-ripgrep-package.mjs
HighCross File Remote Execution Contextdist/chunk-RWMD7E47.js
HighTrigger Reachable External Post Callbackdist/chunk-RWMD7E47.js
HighSemantic Analysis Limiteddist/chunk-RWMD7E47.js
Affected versions and remediation
This report applies to @superblocksteam/cli@2.0.173.
See all versions of @superblocksteam/cli for other recorded verdicts.
- Review the evidence and your use of @superblocksteam/cli@2.0.173 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.