registry / @socketsecurity/cli / 1.1.160
@socketsecurity/cli@1.1.160
CLI for Socket.dev
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe scanner findings resolve to bundled dependency functionality and explicit CLI features. The manifest has no install lifecycle script, and source inspection found no concrete malicious behavior.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user runs a CLI command that requests package or GitHub operations.
Impact
No automatic install-time execution, credential exfiltration, or persistence was confirmed.
Mechanism
User-invoked CLI subprocess and API client operations.
AI rationale
The scanner findings resolve to bundled dependency functionality and explicit CLI features. The manifest has no install lifecycle script, and source inspection found no concrete malicious behavior.
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes user-invoked CLI binaries and has no install lifecycle hook.
- The CLI wrapper spawns the packaged CLI with the user's arguments and inherited standard I/O.
- The flagged credential-capable registry code removes authorization and cookie headers when a redirect changes hostname.
- The dynamic Function calls are terminal capability compilation in the bundled terminal library.
- GitHub token use is an explicit scan command option with a documented GitHub API base URL.
- The large vendor bundle imports standard Node modules; no independent malicious execution path was found.
- The Maven artifact is a ZIP/JAR payload, but no lifecycle hook invokes it.
Evidence against
- The package contains large vendored bundles, network client code, and a Maven JAR, increasing static-analysis noise.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetwork
Source & flagged code
18 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
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
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
Affected versions and remediation
This report applies to @socketsecurity/cli@1.1.160.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.1.160 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.