registry / @socketsecurity/cli / 1.8.4
@socketsecurity/cli@1.8.4
CLI for Socket.dev
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe package manifest and launcher show a CLI entrypoint without an install lifecycle hook. Flagged environment, network, and dynamic-code matches in the inspected vendored files align with npm tooling and ordinary library code, not a demonstrated attack.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user invokes one of the declared CLI commands.
Impact
No unauthorized credential transfer, install-time mutation, or other concrete attack effect was established.
Mechanism
The launcher starts the bundled CLI; inspected flagged code handles registry requests, caching, terminal formatting, and validator generation.
AI rationale
The package manifest and launcher show a CLI entrypoint without an install lifecycle hook. Flagged environment, network, and dynamic-code matches in the inspected vendored files align with npm tooling and ordinary library code, not a demonstrated attack.
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest identifies version 1.8.4 as a Socket CLI and declares command entrypoints; the launcher starts the bundled CLI.
- The bundled CLI loads its vendor code and local registry utilities. The flagged npm tooling contains registry-fetch and authorization-cache logic consistent with package management.
- The dynamic code-generation matches are in terminal capability formatting and validator generation; the inspected excerpts do not show remote payload execution.
- The Maven extension analysis identifies a JAR manifest created by the Maven JAR Plugin; no attack behavior was established from the inspected evidence.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
Source & flagged code
17 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 Critical9 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
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
HighSemantic Analysis Limiteddist/vendor.js
Medium
Affected versions and remediation
This report applies to @socketsecurity/cli@1.8.4.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.8.4 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.