registry / @socketsecurity/cli-with-sentry / 1.8.3
@socketsecurity/cli-with-sentry@1.8.3
⚠ Under reviewCLI for Socket.dev, includes Sentry error handling, otherwise identical to the regular `socket` package
AI Security Review
scanned 21d ago · by lpm-firewall-aiThe scanner alerts inspected here resolve to ordinary CLI, registry-authentication, terminal-capability, and validator code. The Maven extension is executable and reachable during Maven analysis, but its behavior is not established by the available artifact report, leaving a material unresolved risk.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs the CLI’s Maven manifest analysis.
Impact
The extension’s effects during Maven analysis cannot be determined from the available artifact analysis.
Mechanism
The CLI adds the bundled extension JAR to Maven’s classpath and triggers Maven’s validate phase; the inspected artifact analysis does not expose the classes’ behavior.
AI rationale
The scanner alerts inspected here resolve to ordinary CLI, registry-authentication, terminal-capability, and validator code. The Maven extension is executable and reachable during Maven analysis, but its behavior is not established by the available artifact report, leaving a material unresolved risk.
Evidence
dist/cli.jsdist/manifest-scripts/maven-extension/coana-maven-extension.jar.lpm-inspection-HTWeEF/0-1f7f04b18495.txt
Decision evidence
public snapshotAI called this Manual Review at 81.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest maps the CLI commands to bin launchers, and the launcher starts the bundled CLI when invoked. The inspected manifest scripts begin with build tasks and show no install lifecycle hook.
- The Maven analysis path adds the bundled Coana JAR to Maven’s extension classpath and runs Maven’s validate phase.
- Offline analysis identifies the JAR as a ZIP containing compiled lifecycle participant classes, but says its binary members need further inspection and provides no behavior-level findings.
- The flagged code-generation sites compile terminal capability strings and generated validators; the registry code builds npm authorization headers. These excerpts do not establish unrelated credential collection or delivery.
Evidence against
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-with-sentry@1.8.3.
See all versions of @socketsecurity/cli-with-sentry for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli-with-sentry@1.8.3 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.