registry / @socketsecurity/cli / 1.11.1
@socketsecurity/cli@1.11.1
⚠ Under reviewCLI for Socket.dev
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe inspected credential reference is conditional GitHub Actions OIDC support, with no evidence of an unrelated recipient. The large CLI runtime and other flagged files were not sufficiently resolved to establish either a concrete attack or complete clean coverage.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Running a CLI binary activates its packaged command-line entrypoint.
Impact
No specific harmful effect was confirmed. Uninspected runtime behavior prevents a definitive clean assessment.
Mechanism
The inspected launcher starts the CLI with the caller's arguments and environment; the complete behavior of its bundled runtime remains unresolved.
AI rationale
The inspected credential reference is conditional GitHub Actions OIDC support, with no evidence of an unrelated recipient. The large CLI runtime and other flagged files were not sufficiently resolved to establish either a concrete attack or complete clean coverage.
Decision evidence
public snapshotAI called this Manual Review at 62.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json declares CLI binaries and no install lifecycle hook; its scripts are build and development tasks.
- bin/cli.js launches the packaged CLI and forwards arguments and environment variables to it.
- The flagged GitHub Actions token code checks for GitHub Actions token variables and requests an OIDC token using an audience.
- The npm wrapper forwards user arguments and environment to npm tooling.
- The main CLI imports bundled registry and vendor modules; its full runtime behavior was not resolved in this inspection.
Evidence against
- The credential-related code is in registry tooling and shows no evidence here of sending the token to an unrelated recipient.
- The inspected startup files show command dispatch and process handling, not install-time mutation or credential collection.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetwork
Source & flagged code
19 flaggedbin/cli.jsView file
19L20: const spawnPromise = spawn(
L21: constants.execPath,
High
dist/cli.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @socketsecurity/cli@1.11.0
matchedIdentity = npm:QHNvY2tldHNlY3VyaXR5L2NsaQ:1.11.0
similarity = 0.975
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/cli.jsView on unpkg4516if (extension === '.ps1') {
L4517: throw new utils.InputError('This PowerShell Bazel launcher could not be resolved to a Node entry point. Pass a native .exe, a .cmd or .bat wrapper, or a JavaScript entry point with...
L4518: }
High
Findings
3 Critical9 High8 Medium6 Low
CriticalCredential Exfiltrationexternal/@socketsecurity/registry/external/libnpmpack.js
CriticalTrigger Reachable Dangerous Capabilitydist/vendor.js
CriticalPrevious Version Dangerous Deltadist/cli.js
HighChild Processbin/cli.js
HighShelldist/cli.js
HighEvalexternal/blessed/lib/tput.js
HighCommand Output Exfiltrationdist/vendor.js
HighCross File Remote Execution Contextdist/cli.js
HighTrigger Reachable Credential Exfiltrationdist/vendor.js
HighTrigger Reachable Persistencedist/cli.js
HighShips High Entropy Blobdist/manifest-scripts/maven-extension/coana-maven-extension.jar
Affected versions and remediation
This report applies to @socketsecurity/cli@1.11.1.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.11.1 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.