registry / @socketsecurity/cli-with-sentry / 1.1.173
@socketsecurity/cli-with-sentry@1.1.173
CLI for Socket.dev, includes Sentry error handling, otherwise identical to the regular `socket` package
AI Security Review
scanned 1mo ago · by lpm-firewall-aiStatic inspection found a user-invoked CLI with no npm lifecycle hook. The potentially mutating wrapper path is gated by an explicit argument and confirmation, so no concrete malicious behavior was established.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user invokes one of the declared CLI binaries.
Impact
No unconsented install-time mutation, credential exfiltration, remote payload execution, or persistence was identified.
Mechanism
The launcher forwards user arguments to the bundled CLI. A shell-alias setup path requires an explicit --postinstall argument and user confirmation.
AI rationale
Static inspection found a user-invoked CLI with no npm lifecycle hook. The potentially mutating wrapper path is gated by an explicit argument and confirmation, so no concrete malicious behavior was established.
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes CLI binaries and contains no npm lifecycle hook.
- The primary binary starts the bundled CLI with the caller's arguments.
- The wrapper configuration path is only reached when the caller supplies --postinstall, and alias writes require a confirmation prompt.
- The terminal library's dynamic Function use is for compiled terminal capability formatting.
- The inspected bundled vendor and registry-library paths contain ordinary Node module imports, not package entrypoint hooks.
- The Maven artifact is a JAR with a standard manifest entry.
Evidence against
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
3 Critical9 High8 Medium6 Low
CriticalCredential Exfiltrationexternal/@socketsecurity/registry/external/libnpmpack.js
CriticalTrigger Reachable Dangerous Capabilitydist/vendor.js
CriticalPrevious Version Dangerous Deltadist/cli.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
Affected versions and remediation
This report applies to @socketsecurity/cli-with-sentry@1.1.173.
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.173 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.