socket@1.3.0
CLI for Socket.dev
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe inspected package has no automatic lifecycle trigger and its observed process and configuration actions are tied to explicit CLI use. No concrete malicious behavior was found.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs one of the package command-line entrypoints.
Impact
No unconsented installation-time mutation, credential export, remote payload execution, or destructive behavior was established.
Mechanism
The launcher forwards user arguments to the bundled CLI. An optional wrapper flow requests confirmation before adding shell aliases.
AI rationale
The inspected package has no automatic lifecycle trigger and its observed process and configuration actions are tied to explicit CLI use. No concrete malicious behavior was found.
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- Package metadata identifies a command-line tool and exposes command entrypoints; it has no install lifecycle hook.
- The launcher starts the bundled CLI with supplied command arguments rather than running at import or install time.
- The only observed shell-profile alias write is behind an interactive confirmation in a CLI wrapper flow.
- The reviewed bundled terminal helper invokes a fixed Windows code-page utility with a short timeout.
- The remaining required bundled Java archive is an ordinary archive containing a manifest marker; no active attack behavior was established.
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')
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.3.0.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.3.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.