@socketsecurity/cli-with-sentry@1.1.171
CLI for Socket.dev, includes Sentry error handling, otherwise identical to the regular `socket` package
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe explicit scan upload is package-aligned, but the opaque bundled Java archive prevents a decisive clean classification. No concrete malicious install-time chain was found.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs a Socket CLI scan or manifest-upload command.
Impact
Project dependency metadata can leave the machine during an explicit scan; opaque archive behavior remains unverified.
Mechanism
Runs analysis tooling and uploads selected manifest files.
AI rationale
The explicit scan upload is package-aligned, but the opaque bundled Java archive prevents a decisive clean classification. No concrete malicious install-time chain was found.
Evidence
dist/cli.jsdist/manifest-scripts/maven-extension/coana-maven-extension.jardist/vendor.js
Network endpoints1
api.socket.dev
Decision evidence
public snapshotAI called this Suspicious at 70.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The user-invoked CLI uploads selected manifest files for reachability analysis.
- The command wrapper launches the bundled CLI and forwards user arguments and environment.
- Vendored npm code can attach registry authentication to registry requests.
- Vendored terminal code dynamically compiles terminfo strings.
- The bundled Maven extension is an opaque Java archive, so its behavior cannot be fully source-verified.
Evidence against
- package.json contains no preinstall, install, or postinstall hook.
- The observed upload is part of an explicit CLI operation, not automatic installation.
- The registry authorization code is conventional npm registry request handling.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
HighEntropyStrings
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.171.
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.171 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.