@socketsecurity/cli@1.1.170
CLI for Socket.dev
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo automatic lifecycle attack was found, but an executable opaque JVM component runs against user projects and source-only inspection cannot establish its safety. The network upload and process execution are user-invoked and appear product-aligned, so this warrants a warning rather than a block.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs Socket reachability scanning or a Maven manifest command.
Impact
Project manifest data is sent to api.socket.dev; the bundled JVM extension runs within Maven's validate phase.
Mechanism
Manifest upload and Maven extension execution.
AI rationale
No automatic lifecycle attack was found, but an executable opaque JVM component runs against user projects and source-only inspection cannot establish its safety. The network upload and process execution are user-invoked and appear product-aligned, so this warrants a warning rather than a block.
Evidence
dist/cli.jsdist/manifest-scripts/maven-extension/coana-maven-extension.jardist/vendor.jsbin/cli.js
Network endpoints1
api.socket.dev
Decision evidence
public snapshotAI called this Suspicious at 72.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- A bundled JVM archive is executed by Maven but its bytecode cannot be fully assessed from source text.
- User-invoked reachability scanning uploads selected manifest paths to Socket's service.
- The CLI spawns child processes with the caller environment, and bundled code handles Socket API token variables.
- Bundled dependencies include dynamic terminal-string compilation and package-hook execution paths.
Evidence against
- package.json defines command binaries but no preinstall, install, or postinstall lifecycle hook.
- The upload and Maven-extension paths are reached from explicit CLI scan and manifest operations.
- The vendored pack code only runs prepack and postpack for an explicitly packed local directory.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
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@1.1.170.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.1.170 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.