socket@1.1.178
CLI for Socket.dev
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe active request path permits credential forwarding to an unrestricted configured URL. The configuration requirement prevents a finding of covert malware, but does not bind the credential to its intended service.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs a CLI operation after setting the API base URL in configuration or the environment.
Impact
A configured untrusted endpoint could receive a valid Socket API token.
Mechanism
The configured URL is used to construct a request, and the default token is placed in its Authorization header.
AI rationale
The active request path permits credential forwarding to an unrestricted configured URL. The configuration requirement prevents a finding of covert malware, but does not bind the credential to its intended service.
Evidence
dist/utils.js
Decision evidence
public snapshotAI called this Suspicious at 89.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The CLI accepts an API base URL from an environment setting or saved configuration without an allowlist.
- SDK setup defaults to the saved Socket API token and can prompt for one.
- A request is sent to the configured base URL with that token in the Authorization header.
Evidence against
- The exposed behavior requires an operator-supplied API endpoint; no hidden package-controlled recipient was identified.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
Source & flagged code
17 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
2 Critical9 High8 Medium6 Low
CriticalCredential Exfiltrationexternal/@socketsecurity/registry/external/libnpmpack.js
CriticalTrigger Reachable Dangerous Capabilitydist/vendor.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
HighSemantic Analysis Limiteddist/vendor.js
Medium
Affected versions and remediation
This report applies to socket@1.1.178.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.1.178 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.