registry / @socketsecurity/cli-with-sentry / 1.4.0
@socketsecurity/cli-with-sentry@1.4.0
CLI for Socket.dev, includes Sentry error handling, otherwise identical to the regular `socket` package
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe inspected suspicious primitives are consistent with user-invoked package functionality. Static inspection found no concrete malicious behavior, install-hook abuse, or unrelated credential export.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The user invokes a CLI command; no registry install lifecycle trigger is declared.
Impact
Inspected behavior performs CLI analysis and reporting; no confirmed malicious effect was found.
Mechanism
The launcher starts bundled code, analysis commands invoke build tools, and telemetry sanitizes token arguments. No malicious execution or credential harvesting chain was established.
AI rationale
The inspected suspicious primitives are consistent with user-invoked package functionality. Static inspection found no concrete malicious behavior, install-hook abuse, or unrelated credential export.
Network endpoints2
o555220.ingest.us.sentry.ioregistry.npmjs.org/
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has no registry install hooks or runtime self-dependency.
- bin/cli.js launches the bundled CLI with caller arguments and optional Sentry instrumentation.
- The flagged dynamic functions implement terminal formatting and schema validation.
- The bundled packing library runs directory prepack scripts only when scripts are enabled.
- The CLI loads the bundled Maven records extension during project analysis.
- Telemetry sanitization redacts API token arguments; inspected reporting and update behavior is package-aligned.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
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.4.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.4.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.