registry / @socketsecurity/cli / 1.6.1
@socketsecurity/cli@1.6.1
⚠ Under reviewCLI for Socket.dev
AI Security Review
scanned 28d ago · by lpm-firewall-aiReadable source supports ordinary CLI, terminal capability compilation, and conditional GitHub Actions OIDC behavior. The shipped Maven extension binary could not be inspected as readable source, leaving its behavior unresolved.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Unclear; the JAR is packaged under the Maven extension directory, but its activation could not be established from readable source.
Impact
Unknown; the available evidence does not establish harmful behavior.
Mechanism
The binary contents and behavior remain unverified.
AI rationale
Readable source supports ordinary CLI, terminal capability compilation, and conditional GitHub Actions OIDC behavior. The shipped Maven extension binary could not be inspected as readable source, leaving its behavior unresolved.
Evidence
dist/manifest-scripts/maven-extension/coana-maven-extension.jar
Decision evidence
public snapshotAI called this Manual Review at 78.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The Maven extension JAR is a binary file that the citation tool could not provide as a readable UTF-8 excerpt, so its contents remain unverified.
Evidence against
- The manifest identifies this as Socket.dev’s CLI and defines command-line entry points; it declares no install lifecycle hook.
- The CLI launcher starts the package’s own CLI with inherited standard I/O and environment.
- Bundled registry tooling requests a GitHub Actions OIDC token only when the runner supplies its request URL and token; the match is consistent with that provider’s function.
- The flagged dynamic function construction in the terminal library is in terminfo compilation code.
- The main CLI imports the bundled vendor module as part of its application entry point.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
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')
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 @socketsecurity/cli@1.6.1.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@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.