registry / @socketsecurity/cli / 1.1.180
@socketsecurity/cli@1.1.180
CLI for Socket.dev
AI Security Review
scanned 1mo ago · by lpm-firewall-aiRuntime dependencies are @socketsecurity/socket-patch and form-data, and scripts contain no registry install lifecycle. Spawn, terminfo compilation, npm pack, and Socket API constants are consistent with an invoked security CLI rather than a hidden attack.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs the socket or related bin command.
Impact
No unconsented credential export, persistence, or foreign agent-control write was established.
Mechanism
The bin wrapper starts the bundled CLI, which talks to the Socket service and uses local packaging and terminal helpers only as part of that command.
AI rationale
Runtime dependencies are @socketsecurity/socket-patch and form-data, and scripts contain no registry install lifecycle. Spawn, terminfo compilation, npm pack, and Socket API constants are consistent with an invoked security CLI rather than a hidden attack.
Decision evidence
public snapshotAI called this Clean at 84.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json names the Socket.dev CLI, publishes bin entrypoints, and has no preinstall, install, or postinstall hook.
- bin/cli.js only runs when invoked and respawns the packaged dist CLI with inherited stdio.
- external/blessed/lib/tput.js compiles local terminfo strings with Function for terminal display.
- libnpmpack.js exposes a user-driven npm pack helper, not an install-time payload.
- dist/cli.js loads the bundled vendor and Socket registry helpers as the CLI runtime.
- dist/vendor.js points the Socket client at https://api.socket.dev/v0.
- The Maven extension archive is a standard jar identified by META-INF/MANIFEST.MF.
Evidence against
- Blessed terminfo compilation uses Function on generated terminal capability code.
- A public Socket API key constant is bundled for calls to the Socket API.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindings
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')
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 @socketsecurity/cli@1.1.180.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.1.180 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.