registry / @socketsecurity/cli-with-sentry / 1.1.155
@socketsecurity/cli-with-sentry@1.1.155
CLI for Socket.dev, includes Sentry error handling, otherwise identical to the regular `socket` package
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection shows a user-invoked Socket security CLI with package-manager interception and package-aligned API/Sentry networking. Scanner findings arise from normal bundled dependencies and CLI behavior, not a concrete malicious chain.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
User runs a declared CLI binary such as socket-with-sentry or socket-npm-with-sentry.
Impact
No install-time execution, credential harvesting, stealth persistence, or foreign control-surface mutation was found.
Mechanism
User-invoked dependency scanning, API access, and optional Sentry error reporting.
AI rationale
Source inspection shows a user-invoked Socket security CLI with package-manager interception and package-aligned API/Sentry networking. Scanner findings arise from normal bundled dependencies and CLI behavior, not a concrete malicious chain.
Evidence
package.jsonbin/cli.jsdist/shadow-npm-bin2.jsdist/shadow-npm-inject.jsdist/utils.jsdist/instrument-with-sentry.jsexternal/@socketsecurity/registry/external/libnpmpack.jsbin/npm-cli.jsdist/cli.js
Network endpoints2
api.socket.dev/v0/66736701db8e4ffac046bd09fa6aaced@o555220.ingest.us.sentry.io/4508846967619585
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- Runtime error capture is configured for Sentry.
- CLI wrappers spawn package-manager commands when explicitly invoked.
Evidence against
- package.json has no preinstall/install/postinstall hooks.
- bin/cli.js only launches the bundled CLI with inherited stdio.
- dist/shadow-npm-inject.js scans npm dependency diffs before delegating to npm.
- Socket API token use is limited to Socket API requests and user-invoked commands.
- libnpmpack.js is bundled npm/pacote-style dependency code, not a package-specific exfiltration path.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
HighEntropyStringsObfuscatedUrlStrings
Source & flagged code
15 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 Critical7 High8 Medium7 Low
CriticalCredential Exfiltrationexternal/@socketsecurity/registry/external/libnpmpack.js
CriticalPrevious Version Dangerous Deltadist/cli.js
HighChild Processbin/cli.js
HighShell
HighEvalexternal/blessed/lib/tput.js
HighCross File Remote Execution Contextdist/cli.js
HighTrigger Reachable Persistencedist/cli.js
HighShips High Entropy Blobdist/manifest-scripts/maven-extension/coana-maven-extension.jar
HighSemantic Analysis Limitedexternal/@socketsecurity/registry/external/libnpmpack.js
MediumDynamic Requirebin/npm-cli.js
MediumNetwork
MediumEnvironment Vars
Affected versions and remediation
This report applies to @socketsecurity/cli-with-sentry@1.1.155.
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.155 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.