socket@1.1.172
CLI for Socket.dev
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe high-risk findings resolve to bundled dependencies and normal CLI functionality. There is no lifecycle script or source-grounded malicious chain.
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 automatic persistence, broad configuration mutation, or credential exfiltration was confirmed.
Mechanism
CLI execution and package-analysis API requests.
AI rationale
The high-risk findings resolve to bundled dependencies and normal CLI functionality. There is no lifecycle script or source-grounded malicious chain.
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 exposes user-invoked CLI binaries and contains no install lifecycle hook.
- The CLI launcher passes the user’s arguments to the packaged CLI process.
- The flagged dynamic evaluation is terminal capability formatting in the bundled blessed library.
- The registry helper removes authorization and cookie headers when a redirect changes hostname.
- The CLI’s analytics request is an explicit command handler using its SDK.
- The Maven artifact contains a normal Maven manifest marker and is not invoked by a lifecycle script.
Evidence against
- The package includes subprocess, network, and terminal-library capabilities, but inspection found no automatic install-time trigger or credential forwarding to an unrestricted endpoint.
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')
Medium
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 socket@1.1.172.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.1.172 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.