socket@1.6.0
⚠ Under reviewCLI for Socket.dev
AI Security Review
scanned 28d ago · by lpm-firewall-aiInspected source supports ordinary CLI and dependency behavior, with no confirmed attack surface. The required Maven archive citation could not be obtained, so required clean citation coverage is incomplete and the remaining uncertainty warrants manual review.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Running the socket CLI activates the inspected entrypoint; no install hook was listed in package.json.
Impact
No harmful effect was confirmed in the inspected source; the uninspected archive prevents a complete clean determination.
Mechanism
The CLI launches its bundled entrypoint, and the inspected credential-related code conditionally requests a GitHub Actions identity token.
AI rationale
Inspected source supports ordinary CLI and dependency behavior, with no confirmed attack surface. The required Maven archive citation could not be obtained, so required clean citation coverage is incomplete and the remaining uncertainty warrants manual review.
Decision evidence
public snapshotAI called this Manual Review at 68.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json defines CLI binaries and no install lifecycle hook.
- bin/cli.js starts the package CLI by spawning its bundled dist entrypoint.
- blessed uses dynamic functions to compile terminal capability code.
- Bundled Sigstore code requests an identity token only when GitHub Actions token variables are present.
- The Maven extension archive could not be inspected as source, leaving required clean citation coverage incomplete.
Evidence against
- The inspected entrypoint and bundled code fit a Socket CLI and its dependencies; no concrete attack behavior was established.
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.6.0.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.6.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.