registry / @socketsecurity/cli-with-sentry / 1.1.172
@socketsecurity/cli-with-sentry@1.1.172
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 Socket CLI with explicit login handling and package-aligned Sentry error instrumentation. It has no lifecycle hook or concrete malicious behavior.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Running a package command-line entrypoint.
Impact
No unconsented installation action, persistence, destructive behavior, or credential theft was identified.
Mechanism
The launcher starts the packaged CLI and, in this Sentry build, loads its Sentry instrumentation.
AI rationale
Static inspection found a user-invoked Socket CLI with explicit login handling and package-aligned Sentry error instrumentation. It has no lifecycle hook or concrete malicious behavior.
Network endpoints1
66736701db8e4ffac046bd09fa6aaced@o555220.ingest.us.sentry.io/4508846967619585
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- Package metadata exposes command-line entrypoints and contains no install lifecycle hook.
- The main launcher runs the packaged CLI with the user's arguments and inherited standard I/O.
- The Sentry-specific build initializes error reporting only when its compiled Sentry flag is enabled.
- Login explicitly prompts for a Socket API token before configuring the SDK.
- Reviewed terminal and npm-registry support code performs terminal-info reads and defaults registry access to npmjs.
- The bundled Java archive contains named Socket facts/workspaces classes; no process or network class markers were found.
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.172.
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.172 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.