registry / @socketsecurity/cli-with-sentry / 1.1.167
@socketsecurity/cli-with-sentry@1.1.167
CLI for Socket.dev, includes Sentry error handling, otherwise identical to the regular `socket` package
AI Security Review
scanned 2mo ago · by lpm-firewall-aiStatic inspection found no lifecycle script, self-dependency, covert payload chain, or confirmed credential exfiltration. The scanner findings correspond to bundled library primitives and explicit CLI functionality.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs one of the package's command-line binaries or explicitly runs its completion command.
Impact
The completion command can update the user's Bash completion configuration; no unconsented lifecycle mutation or exfiltration was confirmed.
Mechanism
User-invoked CLI execution and optional Bash completion setup.
AI rationale
Static inspection found no lifecycle script, self-dependency, covert payload chain, or confirmed credential exfiltration. The scanner findings correspond to bundled library primitives and explicit CLI functionality.
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package includes dynamic function construction in bundled terminal and compatibility code.
- The CLI has an explicit completion command that can modify the user's Bash completion setup when the user invokes it.
- A bundled Maven archive is present.
Evidence against
- The manifest exposes command-line binaries and contains no preinstall, install, postinstall, or prepare lifecycle hook.
- The primary launcher starts the packaged CLI only after the user runs its binary.
- The flagged package-packing code writes an archive only when dryRun is explicitly false; no credential exfiltration path was confirmed.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
Source & flagged code
18 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 Critical10 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
HighCredential Redirect Persistencedist/vendor.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
Affected versions and remediation
This report applies to @socketsecurity/cli-with-sentry@1.1.167.
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.167 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.