registry / @socketsecurity/cli / 1.1.173
@socketsecurity/cli@1.1.173
CLI for Socket.dev
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has no automatic install lifecycle hook, and the reported high-risk primitives are either user-invoked CLI behavior or vendored dependency behavior with credential protection. Static inspection found no concrete malicious chain.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
The user explicitly invokes one of the package's CLI binaries.
Impact
No concrete credential exfiltration, persistence, destructive action, or remote payload execution was established.
Mechanism
User-invoked Socket CLI command dispatch.
AI rationale
The package has no automatic install lifecycle hook, and the reported high-risk primitives are either user-invoked CLI behavior or vendored dependency behavior with credential protection. Static inspection found no concrete malicious chain.
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes command-line binaries and has no preinstall, install, or postinstall lifecycle hook.
- The launcher only starts the packaged CLI with the caller's arguments and inherited environment.
- The flagged dynamic Function use is terminal capability formatting in vendored blessed code.
- The flagged registry helper removes authorization and cookie headers when an HTTP redirect changes host.
- The bundled client identifies its service API as api.socket.dev.
- The runtime entrypoint runs telemetry, update checking, and command dispatch only after the CLI is invoked.
- The Maven artifact contains a standard JAR manifest entry; no source evidence connects it to malicious behavior.
Evidence against
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
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@1.1.173.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.1.173 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.