socket@1.9.1
CLI for Socket.dev
AI Security Review
scanned 15d ago · by lpm-firewall-aiSource inspection did not substantiate the scanner’s credential-exfiltration or dynamic-evaluation hints as an attack. The identified token use is conditional Sigstore OIDC handling, and the package declares CLI entrypoints without an install hook.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The CLI is launched, or Sigstore identity support requests a token in a GitHub Actions environment.
Impact
No confirmed harmful effect; the inspected code supports a scoped identity-token flow.
Mechanism
The inspected token helper requires the Actions OIDC request URL and bearer token, then requests an audience-scoped token from that environment-provided URL.
AI rationale
Source inspection did not substantiate the scanner’s credential-exfiltration or dynamic-evaluation hints as an attack. The identified token use is conditional Sigstore OIDC handling, and the package declares CLI entrypoints without an install hook.
Decision evidence
public snapshotAI called this Clean at 89.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json identifies this as the Socket.dev CLI and declares command-line entrypoints, with no install lifecycle hook.
- The flagged credential code requests a GitHub Actions OIDC token only when the Actions-provided URL and token are present; it sends that token to the URL from the same environment for Sigstore identity use.
- The flagged files are bundled CLI dependencies and terminal UI code; their inspected excerpts show ordinary module dependencies and terminfo compilation, not an independent attack.
- The offline artifact report describes a Java archive with inspection limits; its findings do not establish malicious behavior.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
HighEntropyStringsPossibleObfuscation
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.9.1.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.9.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.