socket@1.11.0
CLI for Socket.dev
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected credential and evaluation matches fit the CLI’s package-management and terminal-library functions. Scanner hints and the executable Maven archive did not establish concrete attack behavior.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user invokes one of the published CLI commands.
Impact
No confirmed malicious impact was identified.
Mechanism
The launcher starts the bundled CLI, which uses npm registry and GitHub request code for package operations. No install-time mutation or unrelated credential transfer was established.
AI rationale
The manifest has no install lifecycle hook, and the inspected credential and evaluation matches fit the CLI’s package-management and terminal-library functions. Scanner hints and the executable Maven archive did not establish concrete attack behavior.
Decision evidence
public snapshotAI called this Clean at 85.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes CLI entrypoints and declares no install lifecycle hook.
- bin/cli.js launches the bundled CLI with the caller’s arguments and inherited environment.
- The flagged npm packer code handles registry authentication; inspection found no unrelated credential recipient.
- The GitHub token use is in a request for a GitHub release download URL.
- The flagged terminal-library evaluation is part of terminal capability handling; no independent attack behavior was identified.
- The bundled dependency and inspected Maven artifact evidence did not establish an attack.
Evidence against
- Static hints flagged credential exfiltration, dynamic evaluation, and an executable archive; those labels alone do not establish malicious behavior.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
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')
Medium
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 socket@1.11.0.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.11.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.