registry / @socketsecurity/cli / 1.6.0
@socketsecurity/cli@1.6.0
⚠ Under reviewCLI for Socket.dev
AI Security Review
scanned 28d ago · by lpm-firewall-aiSource inspection found no confirmed attack surface in the CLI or flagged JavaScript paths, but the required Maven extension archive was unreadable through the source inspection tool. Because that required artifact could not be assessed, the package needs manual review.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Running a published CLI command activates the packaged entrypoint; no package installation hook was found.
Impact
No concrete credential theft, unrelated network transmission, or install-time mutation was established; the uninspected archive prevents a clean determination.
Mechanism
The inspected launcher forwards arguments to the CLI, and registry code handles credentials in registry requests. The archive contents could not be examined as printable source.
AI rationale
Source inspection found no confirmed attack surface in the CLI or flagged JavaScript paths, but the required Maven extension archive was unreadable through the source inspection tool. Because that required artifact could not be assessed, the package needs manual review.
Evidence
package.jsonbin/cli.jsdist/cli.jsdist/vendor.jsexternal/blessed/lib/tput.jsexternal/@socketsecurity/registry/external/libnpmpack.jsdist/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 manifest exposes command line tools through bin entrypoints and declares no install lifecycle hook.
- The primary launcher starts the packaged CLI and forwards the caller's arguments.
- Registry code sends auth tokens in registry requests and documents credential handling for tarballs hosted elsewhere.
- The terminal library compiles generated terminfo capability code; this alone does not establish malicious execution.
- The Maven extension archive could not be inspected as printable source, so its contents remain unresolved.
Evidence against
- Inspected credential handling is scoped to registry authentication, with separate handling for GitHub Actions OIDC tokens.
- The launcher behavior inspected is user-invoked; no install-time mutation or unrelated credential destination 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')
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.0.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.6.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.