socket@1.13.0
CLI for Socket.dev
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package’s security CLI purpose explains its API and subprocess behavior, and the flagged credential finding is a false positive. However, CLI startup automatically tracks command context and error details for organization-enabled telemetry, with no disclosure or local opt-out found, so this merits a warning rather than a block.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Each CLI invocation starts telemetry tracking; sending requires a configured default organization and that organization’s telemetry setting to be enabled.
Impact
Socket may receive command arguments and diagnostic details without a disclosure or local opt-out found in the reviewed package source.
Mechanism
The CLI records sanitized arguments and runtime metadata, adds path-sanitized error messages and stacks on failures, then submits events through the Socket SDK.
AI rationale
The package’s security CLI purpose explains its API and subprocess behavior, and the flagged credential finding is a false positive. However, CLI startup automatically tracks command context and error details for organization-enabled telemetry, with no disclosure or local opt-out found, so this merits a warning rather than a block.
Evidence
dist/cli.jsdist/utils.jsdist/constants.js
Network endpoints1
api.socket.dev
Decision evidence
public snapshotAI called this Suspicious at 83.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The CLI records a start event with the full process arguments as soon as it starts.
- Telemetry includes sanitized arguments and platform, architecture, Node version, and CLI version; error events also include a path-sanitized message and stack.
- Events are sent when a default organization is configured and that organization’s telemetry setting is enabled, through the Socket SDK’s organization telemetry endpoint.
- The package manifest has no install lifecycle scripts; the reported behavior is runtime telemetry.
Evidence against
- Telemetry is scoped to a configured organization and is skipped when the organization setting disables it.
- The telemetry targets Socket’s own service; the reviewed source shows no automatic credential collection or unrelated collector.
- The package is a Socket security CLI, so API calls, subprocesses, and project scanning fit its stated purpose.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEval
Source & flagged code
20 flaggedbin/cli.jsView file
19L20: const spawnPromise = spawn(
L21: constants.execPath,
High
dist/cli.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = socket@1.11.2
matchedIdentity = npm:c29ja2V0:1.11.2
similarity = 0.992
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/cli.jsView on unpkg5155if (extension === '.ps1') {
L5156: throw new utils.InputError('This PowerShell Bazel launcher could not be resolved to a Node entry point. Pass a native .exe, a .cmd or .bat wrapper, or a JavaScript entry point with...
L5157: }
High
Shell
Package source references shell execution.
Findings
3 Critical9 High9 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
HighShelldist/cli.js
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.13.0.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.13.0 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.