registry / @socketsecurity/cli / 1.8.0
@socketsecurity/cli@1.8.0
CLI for Socket.dev
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe flagged primitives are reachable in user-invoked CLI functionality and align with the package's terminal, validation, signing-tooling, and manifest-generation roles. The inspected sources do not establish a malicious attack surface.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs one of the package's command-line binaries; Maven extension use occurs when the CLI processes a Maven manifest command.
Impact
No unconsented credential disclosure, install-time mutation, or other concrete attack effect was established.
Mechanism
The inspected code compiles terminal and schema-formatting code and requests a workflow token using the workflow-provided URL. The Maven command loads its extension to gather dependency records.
AI rationale
The flagged primitives are reachable in user-invoked CLI functionality and align with the package's terminal, validation, signing-tooling, and manifest-generation roles. The inspected sources do not establish a malicious attack surface.
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes command-line binaries, and the main launcher forwards user arguments to the CLI; no install lifecycle hook is defined.
- The terminal library compiles terminfo formatting strings into functions, and the bundled validator compiles schema validation code.
- The flagged npm code retrieves a GitHub Actions token using the request URL supplied by the workflow and sends its bearer token to that URL.
- The Maven extension is loaded by the CLI's Maven manifest command to gather dependency records; its JAR is a ZIP artifact.
Evidence against
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')
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.8.0.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.8.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.