socket@1.8.3
CLI for Socket.dev
AI Security Review
scanned 21d ago · by lpm-firewall-aiThe source supports a user-invoked Socket CLI with no detected install-time behavior. The flagged dynamic code, registry authentication, and Maven archive have package-aligned uses, and no concrete attack behavior was found.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs a package CLI command; no install-time trigger was found.
Impact
No confirmed attack impact was identified.
Mechanism
No confirmed malicious mechanism was established. Telemetry requires an organization setting and API-enabled configuration, and its command context is sanitized.
AI rationale
The source supports a user-invoked Socket CLI with no detected install-time behavior. The flagged dynamic code, registry authentication, and Maven archive have package-aligned uses, and no concrete attack behavior was found.
Decision evidence
public snapshotAI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json maps the package binaries to CLI wrappers; bin/cli.js launches the CLI with the caller’s arguments, and the inspected scripts are build and check tasks.
- dist/cli.js starts CLI command handling and telemetry when the CLI is run. Telemetry defaults to disabled, requires an organization configuration, and sends events only when the API-provided setting enables it.
- Telemetry context sanitizes command arguments, including redacting API-token values; the CLI sends enabled events through the organization telemetry API.
- The flagged registry code attaches authorization only when registry request auth is present; it sends the request to its URI and notes that credentials for cross-host tarballs require alwaysAuth.
- The dynamic-code findings are in terminal capability formatting and generated schema validation code.
- The archive contains Maven extension classes; the CLI loads that extension only when its manifest-analysis path invokes Maven.
Evidence against
- No concrete attack behavior was identified in the inspected source; the flagged dynamic compilation, registry authentication, and archive have package-aligned CLI uses.
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.8.3.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.8.3 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.