socket@1.4.1
CLI for Socket.dev
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe inspected sensitive operations are consistent with the CLI's command execution and project-analysis functions. Static inspection established no concrete malicious chain.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The user invokes the CLI or its package-manager wrappers; no automatic install hook was found.
Impact
No malicious credential export, destructive action, or agent control hijack was established.
Mechanism
The CLI dispatches commands, queries service APIs, and invokes build tools for project analysis.
AI rationale
The inspected sensitive operations are consistent with the CLI's command execution and project-analysis functions. Static inspection established no concrete malicious chain.
Network endpoints2
api.socket.dev/v0/registry.npmjs.org/
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 has no install lifecycle hooks or runtime self-dependency.
- bin/cli.js launches the packaged CLI with the user's arguments.
- Terminal capability compilation escapes literal text before generating functions.
- The bundled packing library runs packing hooks only within its directory-packing operation.
- The bundled SDK defaults to the Socket API; telemetry sanitizes token arguments.
- The CLI loads the bundled Maven extension for project analysis; the archive contains the corresponding facts-record engine.
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.4.1.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.4.1 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.