registry / @socketsecurity/cli / 1.4.1
@socketsecurity/cli@1.4.1
CLI for Socket.dev
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe inspected behaviors are consistent with dependency scanning and user-invoked package tooling. Static inspection found no concrete malicious installation, credential theft, or agent control mutation.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Users invoke the CLI or its package manager wrappers; no npm install hook activates these behaviors.
Impact
No malicious impact was identified from the inspected source; requested analysis can execute build tools and package scripts.
Mechanism
The CLI launches local tools, uses an authenticated API client, and loads a bundled Maven analysis extension. No concrete malicious chain was established.
AI rationale
The inspected behaviors are consistent with dependency scanning and user-invoked package tooling. Static inspection found no concrete malicious installation, credential theft, or agent control mutation.
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
- The package has no npm install lifecycle hooks or runtime self-dependency.
- The launcher forwards command arguments to the bundled CLI.
- The terminal library compiles terminal formatting functions; the packing library runs directory package scripts when scripts are enabled.
- The API client defaults to Socket's API, and telemetry sanitization redacts API token arguments.
- The CLI loads the bundled Maven extension for dependency analysis; the archive contains Socket dependency-record classes.
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')
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.4.1.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@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.