registry / @socketsecurity/cli / 1.1.175
@socketsecurity/cli@1.1.175
CLI for Socket.dev
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe scanner findings map to bundled dependencies and normal CLI functionality. Source inspection found no lifecycle hook, self-dependency chain, or concrete malicious behavior.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user runs one of the CLI commands.
Impact
No concrete unconsented credential transfer, persistence, destructive action, or remote payload execution was established.
Mechanism
CLI scanning and package-management integration.
AI rationale
The scanner findings map to bundled dependencies and normal CLI functionality. Source inspection found no lifecycle hook, self-dependency chain, or concrete malicious behavior.
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest defines command-line entrypoints and has no preinstall, install, or postinstall hook; it also has no runtime dependency on itself.
- The launcher only starts the package's bundled CLI with the caller's arguments and inherited standard I/O.
- The flagged dynamic Function use is terminal capability-string handling, gated by the library's stringify option, not downloaded or environment-derived code.
- The bundled request implementation removes authorization and cookie headers when a redirect changes hostname.
- The large vendor file references the Socket API, and the JAR is a conventional archive containing a Maven manifest marker.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
HighEntropyStringsPossibleObfuscation
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.175.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.1.175 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.