registry / @socketsecurity/cli / 1.8.3
@socketsecurity/cli@1.8.3
CLI for Socket.dev
AI Security Review
scanned 21d ago · by lpm-firewall-aiSource inspection found no malicious behavior. Scanner signals correspond to bundled npm authentication handling, terminal capability compilation, and packaged CLI/build-tool functionality.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user invokes a CLI command; no automatic install hook was present.
Impact
No confirmed unauthorized credential disclosure, persistence, or consumer-project mutation was found.
Mechanism
The CLI dispatches user arguments, conditionally sends sanitized telemetry, and scans dependencies before forwarding package-manager commands.
AI rationale
Source inspection found no malicious behavior. Scanner signals correspond to bundled npm authentication handling, terminal capability compilation, and packaged CLI/build-tool functionality.
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest maps commands to CLI entrypoints; the launcher starts the bundled CLI when invoked.
- The CLI dispatches supplied arguments. Telemetry sanitizes arguments and sends events only when an organization is configured.
- The bundled npm HTTP client removes authorization and cookie headers when a redirect changes hostname.
- The flagged dynamic function creation is used by the terminal capability formatter and is wrapped in error handling.
- The archive is identified as a Maven extension; the CLI references it through a Maven build-tool helper.
- The pnpm wrapper scans dependency data and then forwards the command to the resolved pnpm executable.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
HighEntropyStrings
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/shadow-pnpm-bin2.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.8.3.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.8.3 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.