registry / @socketsecurity/cli / 1.8.1
@socketsecurity/cli@1.8.1
⚠ Under reviewCLI for Socket.dev
AI Security Review
scanned 23d ago · by lpm-firewall-aiThe inspected CLI invokes a bundled executable Maven extension during a user-requested manifest operation. Its class behavior remains unresolved in the available offline analysis, so manual review is warranted without treating the scanner hints as proof of an attack.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user invokes the CLI's Maven manifest operation, which runs Maven validation with the bundled extension.
Impact
The extension's effects remain unresolved, so the package cannot be cleared or classified as malicious from the available source inspection.
Mechanism
The CLI supplies the archive as Maven's extension class path; the archive analysis identifies class files but does not establish their runtime behavior.
AI rationale
The inspected CLI invokes a bundled executable Maven extension during a user-requested manifest operation. Its class behavior remains unresolved in the available offline analysis, so manual review is warranted without treating the scanner hints as proof of an attack.
Evidence
dist/cli.js.lpm-inspection-L27p4Y/0-86f1dc8ff05b.txtdist/manifest-scripts/maven-extension/coana-maven-extension.jar
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 bin entrypoints, including the CLI launcher.
- The launcher starts the packaged CLI as a child process when invoked.
- The Maven manifest path loads the bundled archive as a Maven extension during validation.
- Offline archive analysis identifies executable class files but leaves their behavior unresolved.
- The terminal library generates functions from terminal capability strings when formatting is enabled.
- The bundled registry helper requests a GitHub Actions token using the URL supplied by the Actions environment.
Evidence against
- The inspected JavaScript connects the Maven archive to an explicit Maven manifest operation; no malicious action or unrelated network recipient was established from the inspected source.
- The reported dynamic code generation is in terminal capability formatting, and the token helper targets the environment-provided GitHub Actions token endpoint.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVars
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.1.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.8.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.