registry / @socketsecurity/cli / 1.11.0
@socketsecurity/cli@1.11.0
CLI for Socket.dev
AI Security Review
scanned 9d ago · by lpm-firewall-aiSource inspection did not confirm malicious behavior. The credential-related scanner hit is GitHub Actions OIDC handling in bundled registry tooling, and the Maven extension is invoked through the CLI's manifest workflow.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user invokes one of the declared CLI commands; the Maven extension runs in the Maven manifest workflow.
Impact
No harmful effect or unconsented credential transfer was established.
Mechanism
The reviewed credential handling uses GitHub Actions OIDC inputs, while the flagged utilities serve package, cache, terminal, and manifest functions.
AI rationale
Source inspection did not confirm malicious behavior. The credential-related scanner hit is GitHub Actions OIDC handling in bundled registry tooling, and the Maven extension is invoked through the CLI's manifest workflow.
Decision evidence
public snapshotAI called this Clean at 86.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest declares CLI entrypoints and build scripts; the included dependency manifests show build and test scripts, with no install hook shown.
- The launcher forwards user arguments to the CLI. The Maven extension is invoked from the manifest workflow with the selected project and build tool.
- The flagged credential flow requests an audience-scoped token using GitHub Actions-provided URL and token variables.
- The flagged bundled files contain cache, package, network, browser-data, glob, terminal, and image-processing utilities; the inspected excerpts do not show a package-controlled credential recipient or hidden loader.
- The packaged Maven extension is reached through the Maven manifest workflow; the CLI invokes Maven to trigger it and collect records.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
Source & flagged code
18 flaggedbin/cli.jsView file
19L20: const spawnPromise = spawn(
L21: constants.execPath,
High
external/blessed/lib/tput.jsView file
1152if (this.options.stringify && code.indexOf('return ') === 0) {
L1153: return new Function('', code)();
L1154: }
High
Eval
Package source references dynamic code evaluation.
external/blessed/lib/tput.jsView on unpkg · L1152bin/npm-cli.jsView file
4void (async () => {
L5: const Module = require('node:module')
L6: const path = require('node:path')
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
HighShell
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.0.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.11.0 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.