registry / @socketsecurity/cli-with-sentry / 1.1.180
@socketsecurity/cli-with-sentry@1.1.180
CLI for Socket.dev, includes Sentry error handling, otherwise identical to the regular `socket` package
AI Security Review
scanned 1mo ago · by lpm-firewall-aiScripts contain no registry install lifecycle, and the bin only starts the local CLI when invoked. Bundled eval-like terminal compilation, npm pack code, and the Maven jar are package-aligned command helpers rather than a concrete attack chain.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A person runs one of the published bin commands.
Impact
No unconsented install mutation, credential theft, or remote payload execution was established.
Mechanism
The bin spawns the local dist CLI. API tokens and GitHub tokens are taken from the caller environment for Socket and GitHub operations the user requested.
AI rationale
Scripts contain no registry install lifecycle, and the bin only starts the local CLI when invoked. Bundled eval-like terminal compilation, npm pack code, and the Maven jar are package-aligned command helpers rather than a concrete attack chain.
Decision evidence
public snapshotAI called this Clean at 84.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes only user-invoked bin entrypoints and build/test scripts, with no preinstall, install, or postinstall hook.
- bin/cli.js launches the local dist CLI through Node using the package spawn helper and hardening flags when the user runs the binary.
- Bundled blessed tput, libnpmpack, vendor rollup, Socket CLI, and the Maven extension jar are command-time helpers; the jar only shows a META-INF/maven entry and is not an install trigger.
Evidence against
- The Sentry build path can load dist/instrument-with-sentry.js, which reports errors to a Sentry ingest host, only after the user starts the CLI.
- Blessed tput uses Function to compile terminal capability strings, which is library behavior and not an install or network payload.
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.1.180.
See all versions of @socketsecurity/cli-with-sentry for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli-with-sentry@1.1.180 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.