socket@1.6.1
⚠ Under reviewCLI for Socket.dev
AI Security Review
scanned 28d ago · by lpm-firewall-aiThe inspected signals are consistent with ordinary CLI and GitHub Actions OIDC functionality, and do not establish malicious behavior. Manual review is necessary because the required Maven extension JAR is binary and could not be inspected or cited as a source excerpt.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The CLI is launched by a user; the OIDC token helper requires GitHub Actions OIDC environment variables.
Impact
No malicious effect or unintended recipient was confirmed; the uninspectable binary leaves the review incomplete.
Mechanism
The helper requests a token from the environment-provided OIDC URL using its corresponding environment-provided bearer token.
AI rationale
The inspected signals are consistent with ordinary CLI and GitHub Actions OIDC functionality, and do not establish malicious behavior. Manual review is necessary because the required Maven extension JAR is binary and could not be inspected or cited as a source excerpt.
Decision evidence
public snapshotAI called this Manual Review at 77.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The package exposes CLI commands through bin/cli.js, which starts the built CLI when invoked.
- The bundled registry code requests a token using the GitHub Actions OIDC URL and token supplied through environment variables; this is consistent with a service integration, but the complete activation path was not established.
- The required Maven extension JAR is binary and could not be read as a citable source excerpt, preventing the required clean citation coverage.
Evidence against
- No npm lifecycle hooks appear in the inspected manifest excerpt.
- The flagged terminal capability code initializes terminal options and does not itself establish malicious behavior.
- The OIDC code uses an environment-provided URL and token, and no unrelated recipient or exfiltration behavior was established.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetwork
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.1.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.6.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.