registry / @socketsecurity/cli-with-sentry / 1.8.0
@socketsecurity/cli-with-sentry@1.8.0
CLI for Socket.dev, includes Sentry error handling, otherwise identical to the regular `socket` package
AI Security Review
scanned 23d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or concrete attack behavior. The flagged credential and dynamic-code primitives are explained by registry redirect protections and generated terminal and schema code; telemetry is gated, and the Maven extension is used for manifest collection.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Running an advertised CLI command; Maven extension behavior occurs when the manifest workflow invokes Maven.
Impact
No confirmed attacker-controlled effect or harmful impact was established.
Mechanism
The launcher forwards arguments to the CLI, which uses npm registry auth handling and invokes build tools for manifest records. Telemetry is gated by configured service enablement.
AI rationale
Source inspection found no install lifecycle hook or concrete attack behavior. The flagged credential and dynamic-code primitives are explained by registry redirect protections and generated terminal and schema code; telemetry is gated, and the Maven extension is used for manifest collection.
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json maps the published bins to CLI launchers and contains no install lifecycle hook; bin/cli.js forwards the selected command to the CLI.
- The bundled registry client uses configured npm credentials for requests and removes authorization and cookies when a redirect changes hostname.
- The flagged dynamic-code sites compile formatter code in the terminal library and generated validation code in the bundled validator.
- The Maven extension is invoked through the manifest workflow to collect records; the inspected artifact descriptor identifies it as a Maven extension.
- CLI telemetry requires an organization and enabled telemetry configuration; its context uses sanitized arguments.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
HighEntropyStrings
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.0.
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.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.