@socketsecurity/cli@1.12.1
CLI for Socket.dev
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe CLI automatically sends command arguments in runtime telemetry, with only limited redaction, when an organization's server-side setting enables it. Because the source does not establish user-facing disclosure or a local opt-out, this is suspicious telemetry; the organization gate and first-party endpoint reduce confidence that it is malicious exfiltration.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Running the CLI starts tracking automatically and records command completion or errors.
Impact
Other command arguments, which may contain private package names or sensitive values, can be sent to Socket. The source does not establish that users are informed or given a local opt-out.
Mechanism
The CLI passes process.argv into telemetry context, redacts only selected token patterns and home-directory paths, and posts events to the configured organization's Socket telemetry endpoint.
AI rationale
The CLI automatically sends command arguments in runtime telemetry, with only limited redaction, when an organization's server-side setting enables it. Because the source does not establish user-facing disclosure or a local opt-out, this is suspicious telemetry; the organization gate and first-party endpoint reduce confidence that it is malicious exfiltration.
Evidence
dist/cli.jsdist/utils.jsdist/vendor.js
Network endpoints1
api.socket.dev/v0/orgs/{orgSlug}/telemetry
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The CLI automatically starts telemetry tracking when the command runs.
- Telemetry context includes sanitized command-line arguments.
- Sanitization redacts selected token patterns and home-directory paths but leaves other arguments intact.
- Telemetry is sent only with a configured default organization and when that organization's server-provided telemetry setting is enabled.
- The telemetry request posts organization events to Socket's API; the SDK defaults to api.socket.dev.
- The fallback telemetry configuration disables telemetry if fetching its configuration fails.
Evidence against
- The manifest does not define an install lifecycle hook.
- The telemetry endpoint is Socket's own API, not an unrelated collector.
- Telemetry requires organization configuration and a server-side enabled setting.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindings
Source & flagged code
19 flaggedbin/cli.jsView file
19L20: const spawnPromise = spawn(
L21: constants.execPath,
High
dist/cli.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @socketsecurity/cli@1.11.0
matchedIdentity = npm:QHNvY2tldHNlY3VyaXR5L2NsaQ:1.11.0
similarity = 0.975
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 unpkg4516if (extension === '.ps1') {
L4517: 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...
L4518: }
High
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
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 @socketsecurity/cli@1.12.1.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.12.1 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.