socket@1.1.160
CLI for Socket.dev
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe active CLI contains a concrete token-to-unrestricted-endpoint request path. It lacks install hooks or evidence of automatic execution, so this is a non-blocking dangerous capability.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
The user runs a CLI operation after setting an API base URL and supplying or storing an API token.
Impact
An operator-controlled endpoint can receive the Socket API credential; this is a conditional credential-forwarding capability rather than confirmed covert theft.
Mechanism
The CLI accepts the base URL from configuration or environment, validates only URL syntax, then builds authenticated requests using the token.
AI rationale
The active CLI contains a concrete token-to-unrestricted-endpoint request path. It lacks install hooks or evidence of automatic execution, so this is a non-blocking dangerous capability.
Evidence
dist/utils.jsexternal/@socketsecurity/registry/lib/url.js
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The package exposes its functionality through user-invoked CLI binaries.
- The API token is obtained from an environment variable or persisted configuration.
- The API base URL is also obtained from environment or configuration and is accepted if it is merely a valid URL, without a host allowlist.
- A request helper attaches that token as Basic authorization to the configured base URL.
Evidence against
- No npm preinstall, install, or postinstall lifecycle hook is declared.
- The flagged terminal evaluator is part of terminal-capability formatting, and the vendored npm-pack bundle was not found to be called by the CLI entrypoint.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
HighEntropyStringsPossibleObfuscation
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.160.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.1.160 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.