socket@1.2.0
CLI for Socket.dev
AI Security Review
scanned 1mo ago · by lpm-firewall-aiStatic inspection found a user-invoked Socket CLI without npm lifecycle execution or concrete malicious behavior. Network configuration is package-aligned.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs a Socket CLI command.
Impact
No unconsented installation-time execution, persistence, credential theft, or destructive action was identified.
Mechanism
The launcher forwards command-line arguments to the bundled CLI; the client can use the Socket API.
AI rationale
Static inspection found a user-invoked Socket CLI without npm lifecycle execution or concrete malicious behavior. Network configuration is package-aligned.
Network endpoints1
api.socket.dev/v0/
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- Package metadata exposes CLI binaries and lists build scripts; no npm install lifecycle hook is present.
- The CLI launcher starts the bundled CLI with user-supplied command-line arguments.
- The blessed file is a terminal capability parser.
- The bundled registry code contains package-manager lifecycle handling, but this package does not invoke it at npm installation.
- The vendor bundle configures a Socket API base URL for the CLI client.
- The Maven artifact contains a standard manifest entry.
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.2.0.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.2.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.