socket@1.1.174
CLI for Socket.dev
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has no automatic npm lifecycle trigger, and the flagged primitives are reachable in normal CLI, terminal-formatting, and registry-client paths. The registry code explicitly strips credentials across hostname redirects, so the inspected evidence does not establish credential exfiltration or malicious behavior.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user runs a Socket CLI command.
Impact
No malicious impact was established by static inspection.
Mechanism
User-invoked CLI execution and registry metadata retrieval.
AI rationale
The package has no automatic npm lifecycle trigger, and the flagged primitives are reachable in normal CLI, terminal-formatting, and registry-client paths. The registry code explicitly strips credentials across hostname redirects, so the inspected evidence does not establish credential exfiltration or 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 exposes user-invoked CLI binaries; no automatic npm lifecycle hook is declared.
- The CLI launches the packaged CLI with the caller's arguments and inherited terminal I/O.
- The flagged dynamic function is terminal capability formatting code.
- The registry component fetches the selected package metadata URL with package request headers.
- The registry redirect handler removes authorization and cookies when the hostname changes.
- The main CLI maps its Socket token only into its socket-patch child process environment.
- The Java artifact contains a standard archive manifest marker.
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')
Medium
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 socket@1.1.174.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.1.174 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.