registry / @socketsecurity/cli / 1.6.2
@socketsecurity/cli@1.6.2
⚠ Under reviewCLI for Socket.dev
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe inspected flags resolve to CLI delegation, bundled registry tooling, and terminal capability compilation; they do not establish a malicious chain. The required archive is unreadable as UTF-8 source and clean citation coverage is therefore incomplete, so manual review is appropriate.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Invoking the package CLI or its npm-related shims.
Impact
No confirmed credential theft, install-time mutation, or other attack impact was identified; the remaining required artifact could not be assessed through source citations.
Mechanism
The inspected launcher delegates to the distribution CLI. The flagged token helper requires GitHub Actions OIDC environment values and uses their provided endpoint; the terminal library creates functions while stringifying terminal capability code.
AI rationale
The inspected flags resolve to CLI delegation, bundled registry tooling, and terminal capability compilation; they do not establish a malicious chain. The required archive is unreadable as UTF-8 source and clean citation coverage is therefore incomplete, so manual review is appropriate.
Decision evidence
public snapshotAI called this Manual Review at 76.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The package exposes CLI binaries through bin/cli.js and related npm and package manager shims.
- The CLI launcher loads constants and spawns the distribution CLI.
- The flagged registry bundle's token code requires GitHub Actions OIDC environment values and builds its request URL from the supplied request URL.
- The flagged terminal library's dynamic function creation is in terminal capability stringification code.
- The distribution CLI imports the vendor bundle, but required-path coverage remains unresolved because a required archive is binary and cannot be cited as UTF-8 source.
Evidence against
- Inspected entrypoint code shows command delegation rather than install-time execution.
- The reviewed OIDC code uses a caller-provided GitHub Actions token endpoint, and no independent credential exfiltration behavior was established.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindings
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.2.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.6.2 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.