registry / @socketsecurity/cli / 1.1.174
@socketsecurity/cli@1.1.174
CLI for Socket.dev
AI Security Review
scanned 2mo ago · by lpm-firewall-aiDirect inspection found no lifecycle hook, self-dependency chain, or concrete credential-exfiltration path. Scanner findings map to vendored libraries, a normal archive, and explicit CLI functionality.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user runs a Socket CLI command.
Impact
No concrete credential exfiltration, persistence, or destructive behavior was established.
Mechanism
User-invoked dependency scanning and command execution.
AI rationale
Direct inspection found no lifecycle hook, self-dependency chain, or concrete credential-exfiltration path. Scanner findings map to vendored libraries, a normal archive, and explicit CLI functionality.
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 has no npm install lifecycle hook and declares only two runtime dependencies.
- The executable wrapper launches the packaged CLI only when its bin command is invoked, passing user arguments through.
- The flagged dynamic evaluation is confined to generating terminal capability formatting functions.
- The flagged registry file is a bundled dependency using standard Node modules; inspection found no credential collection-and-send path.
- The CLI defaults its dependency scanner to avoid dependency installation and arbitrary code execution.
- The JAR contains standard Maven archive metadata, not an observed staged payload.
Evidence against
- The CLI performs runtime telemetry and a self-update check when the user runs its command.
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.1.174.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.1.174 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.