socket@1.11.2
CLI for Socket.dev
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe source matches a Socket security CLI: its entrypoint dispatches user commands, registry credentials are used in npm authorization headers, and shell configuration changes require user action. The scanner’s credential and persistence leads did not reveal unauthorized behavior.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
The user invokes a Socket CLI command; shell-profile changes require an interactive confirmation or an explicit completion-install command.
Impact
No unauthorized credential disclosure, install-time contact, or unrequested persistent change was found.
Mechanism
The CLI runs its bundled command handlers. The reviewed npm registry code uses configured credentials in authorization headers for registry requests.
AI rationale
The source matches a Socket security CLI: its entrypoint dispatches user commands, registry credentials are used in npm authorization headers, and shell configuration changes require user action. The scanner’s credential and persistence leads did not reveal unauthorized behavior.
Evidence
~/.bashrcconfigured bash and zsh profile paths
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes Socket CLI commands that forward into the bundled CLI.
- Shell completion is installed by an explicit `socket install completion` command.
- The npm registry code sends configured credentials in authorization headers as part of registry requests.
Evidence against
- The CLI includes shell-profile setup, but wrapper changes require a confirmation prompt.
- No credential flow to an unrelated host or other attack behavior was identified.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
Source & flagged code
19 flaggedbin/cli.jsView file
19L20: const spawnPromise = spawn(
L21: constants.execPath,
High
dist/cli.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = socket@1.11.0
matchedIdentity = npm:c29ja2V0:1.11.0
similarity = 0.975
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/cli.jsView on unpkg4516if (extension === '.ps1') {
L4517: throw new utils.InputError('This PowerShell Bazel launcher could not be resolved to a Node entry point. Pass a native .exe, a .cmd or .bat wrapper, or a JavaScript entry point with...
L4518: }
High
Shell
Package source references shell execution.
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
HighShelldist/cli.js
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.11.2.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.11.2 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.