registry / @socketsecurity/cli / 1.1.168
@socketsecurity/cli@1.1.168
CLI for Socket.dev
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo concrete malicious install hook, credential theft, persistence, or destructive action was established. The opaque JAR and broad user-invoked execution and network capabilities warrant a warning rather than a block.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs a Socket CLI command, including a command that delegates to npm.
Impact
The CLI can execute the selected package-manager command and send requested scan data to Socket services; opaque archive contents leave residual uncertainty.
Mechanism
User-invoked process spawning and authenticated API requests.
AI rationale
No concrete malicious install hook, credential theft, persistence, or destructive action was established. The opaque JAR and broad user-invoked execution and network capabilities warrant a warning rather than a block.
Evidence
bin/cli.jsdist/cli.jsdist/vendor.jsdist/manifest-scripts/maven-extension/coana-maven-extension.jar
Network endpoints2
api.socket.devfirewall-api.socket.dev
Decision evidence
public snapshotAI called this Suspicious at 72.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package ships an opaque Java archive, so its complete runtime behavior cannot be verified from readable JavaScript source.
- The executable launcher starts a child Node process with the caller's arguments and environment.
- A user-invoked command forwards arbitrary arguments to npm, including with a shell on Windows.
- Bundled code contains dynamic Function construction in the terminal capability parser.
- The bundled API client constructs authenticated requests to Socket endpoints.
Evidence against
- The manifest has no preinstall, install, or postinstall lifecycle hook.
- The observable process-spawning paths are reached through explicit CLI commands rather than package installation.
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@1.1.168.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.1.168 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.