registry / @socketsecurity/cli / 1.9.0
@socketsecurity/cli@1.9.0
CLI for Socket.dev
AI Security Review
scanned 16d ago · by lpm-firewall-aiDirect source inspection did not substantiate the scanner’s credential-exfiltration finding: the relevant bundled code belongs to npm registry request handling. The CLI’s telemetry path is organization-scoped and disabled by fallback configuration; no malicious behavior was identified.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Running the CLI invokes its command handler and telemetry event tracking.
Impact
No confirmed attack surface was established by the inspected behavior.
Mechanism
Telemetry uses sanitized command arguments and an organization-scoped SDK; if telemetry configuration is unavailable, the fallback is disabled. Registry authentication is handled in requests to the registry URI.
AI rationale
Direct source inspection did not substantiate the scanner’s credential-exfiltration finding: the relevant bundled code belongs to npm registry request handling. The CLI’s telemetry path is organization-scoped and disabled by fallback configuration; no malicious behavior was identified.
Decision evidence
public snapshotAI called this Clean at 87.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json identifies this as a CLI and its scripts contain build and maintenance commands, with no install lifecycle hook.
- The CLI entrypoint starts telemetry and command handling. Telemetry falls back to disabled when configuration is unavailable, sends only when enabled, and uses the organization-scoped SDK.
- The bundled npm registry code sends requests to its registry URI; the inspected auth handling is part of registry tooling, not a separate credential-export path.
- The listed bundled utilities, dependency manifests, terminal UI sources, and archive analysis did not establish an attack.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
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/utils.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.9.0.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.9.0 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.